{"id":"CVE-2026-107928","aliases":["ALPINE-CVE-2026-107928","AZL-109905","AZL-109983","AZL-110052","AZL-110193","AZL-110268","AZL-110298","BELL-CVE-2026-107928","CURL-CVE-2026-107928","DEBIAN-CVE-2026-107928","EUVD-2026-105357","GHSA-4c9f-c4pg-phw4","OESA-2026-4849","OESA-2026-4851","OESA-2026-4852","RHSA-2026:82895","ROOT-OS-ALPINE-321-CVE-2026-107928","ROOT-OS-DEBIAN-12-CVE-2026-107928","ROOT-OS-DEBIAN-13-CVE-2026-107928","UBUNTU-CVE-2026-107928","USN-8927-1","USN-8927-2","openSUSE-SU-2026:12150-1"],"status":"published","title":"info leak uploading over WebSockets with GnuTLS","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-12","score":0.00705,"percentile":0.53842,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-126"],"published":"2026-10-14T06:00:00Z","modified":"2026-11-11T12:45:12Z","fixes":[{"ecosystem":"Alpine:v3.23","package":"curl","fixed_in":["8.23.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"curl","fixed_in":["8.23.0-r0"],"sources":["osv"]},{"ecosystem":"Root:Alpine:3.21","package":"curl","fixed_in":["8.14.1-r300710","8.14.1-r300711","8.14.1-r300712"],"sources":["osv"]},{"ecosystem":"Root:Alpine:3.21","package":"rootio-curl","fixed_in":["8.14.1-r300710","8.14.1-r300711","8.14.1-r300712"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"curl","fixed_in":["7.88.1-10+deb12u15.aikido.19","7.88.1-10+deb12u15.aikido.20"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-curl","fixed_in":["7.88.1-10+deb12u15.aikido.19","7.88.1-10+deb12u15.aikido.20"],"sources":["osv"]},{"ecosystem":"Root:Debian:13","package":"curl","fixed_in":["8.14.1-2+deb13u7.aikido.25"],"sources":["osv"]},{"ecosystem":"Root:Debian:13","package":"rootio-curl","fixed_in":["8.14.1-2+deb13u7.aikido.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.10","package":"curl","fixed_in":["8.20.0-2ubuntu11.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"curl","fixed_in":["8.18.0-1ubuntu2.8"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.23","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.23.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.23.0-r0"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"cmake","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.30.3-15"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"8.11.1-11"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"8.0.46-2"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.75.0-31"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.85.0"},{"last_affected":"1.96.1-2"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"tensorflow","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.16.1-11"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.88.1-10","7.88.1-10+deb12u1","7.88.1-10+deb12u11","7.88.1-10+deb12u12","7.88.1-10+deb12u13","7.88.1-10+deb12u14","7.88.1-10+deb12u15","7.88.1-10+deb12u1~bpo11+1","7.88.1-10+deb12u2","7.88.1-10+deb12u3","7.88.1-10+deb12u3~bpo11+1","7.88.1-10+deb12u4","7.88.1-10+deb12u5","7.88.1-10+deb12u5~bpo11+1","7.88.1-10+deb12u6","7.88.1-10+deb12u6~bpo11+1","7.88.1-10+deb12u7","7.88.1-10+deb12u8","7.88.1-10+deb12u9","7.88.1-11","8.0.1-1~exp1","8.10.0-1","8.10.0-2","8.10.1-1","8.10.1-1~bpo12+1","8.10.1-2","8.11.0-1","8.11.1-1","8.11.1-1~bpo12+1","8.12.0+git20250209.89ed161+ds-1","8.12.0+git20250209.89ed161+ds-1~bpo12+1","8.12.1-1","8.12.1-2","8.12.1-2~bpo12+1","8.12.1-3","8.12.1-3~bpo12+1","8.13.0-1","8.13.0-1+exp1","8.13.0-2","8.13.0-2+exp1","8.13.0-3","8.13.0-4","8.13.0-4+exp1","8.13.0-5","8.13.0-5+exp1","8.13.0-5~bpo12+1","8.13.0~rc-1~exp1","8.13.0~rc-1~exp2","8.13.0~rc2-1","8.13.0~rc2-2","8.13.0~rc3-1","8.13.0~rc3-1+exp1","8.14.0-1","8.14.0-1+exp1","8.14.0~rc1-1+exp1","8.14.0~rc2-1+exp1","8.14.0~rc3-1+exp1","8.14.1-1","8.14.1-1~bpo12+1","8.14.1-2","8.14.1-2+exp1","8.14.1-2~bpo12+1","8.15.0-1","8.15.0-1~bpo13+1","8.15.0-1~exp1","8.15.0~rc1-1exp1","8.15.0~rc2-1~exp1","8.15.0~rc3-1~exp1","8.16.0-1","8.16.0-1+exp1","8.16.0-1~bpo13+1","8.16.0-2","8.16.0-3","8.16.0-4","8.16.0-4~bpo13+1","8.16.0~rc1-1~exp1","8.16.0~rc2-1","8.16.0~rc2-2","8.16.0~rc3-1","8.17.0-1","8.17.0-2","8.17.0-3","8.17.0~rc1-1~exp1","8.17.0~rc2-1","8.17.0~rc3-1","8.18.0-1","8.18.0-1~bpo13+1","8.18.0-2","8.18.0~rc1-1+exp1","8.18.0~rc2-1","8.18.0~rc3-1","8.19.0-1","8.19.0-1+exp1","8.19.0-1~bpo13+1","8.19.0-2","8.19.0-3","8.19.0-3+exp1","8.19.0-3+exp2","8.19.0~rc1-1~exp1","8.19.0~rc2-1","8.19.0~rc2-2","8.19.0~rc3-1","8.2.1-1","8.2.1-2","8.2.1-2~bpo12+1","8.20.0-1","8.20.0-1+exp","8.20.0-2","8.20.0-2+exp1","8.20.0-2~bpo13+1","8.20.0-3","8.20.0-4","8.20.0-5","8.20.0-5~bpo13+1","8.20.0~rc1-1+exp1","8.20.0~rc1-1+exp2","8.20.0~rc1-1+exp3","8.20.0~rc2-1","8.20.0~rc2-1+exp1","8.20.0~rc3-1","8.20.0~rc3-1+exp1","8.21.0-1","8.21.0-1+exp1","8.21.0-2","8.21.0-2+exp1","8.21.0-2~bpo13+1","8.21.0~rc1-1+exp1","8.21.0~rc2-1","8.21.0~rc2-1+exp1","8.21.0~rc3-1","8.21.0~rc3-1+exp1","8.22.0-1","8.22.0-1+exp1","8.22.0~rc2-1","8.22.0~rc2-2","8.22.0~rc3-1","8.22.0~rc3-1+exp1","8.23.0-1","8.23.0~rc1-1","8.23.0~rc1-2","8.23.0~rc2-1","8.23.0~rc2-1+exp1","8.23.0~rc3-1","8.23.0~rc3-1+exp1","8.3.0-1","8.3.0-2","8.3.0-2~bpo12+1","8.3.0-2~exp1","8.3.0-3","8.4.0-1","8.4.0-2","8.4.0-2~bpo12+1","8.5.0-1","8.5.0-1+exp1","8.5.0-2","8.5.0-2+exp1","8.5.0-2~bpo12+1","8.6.0-1","8.6.0-1.1","8.6.0-2","8.6.0-3","8.6.0-3.1","8.6.0-3.1~exp1","8.6.0-3.1~exp2","8.6.0-3.2","8.6.0-4","8.7.1-1","8.7.1-1+exp1","8.7.1-2","8.7.1-3","8.7.1-4","8.7.1-5","8.7.1-5+exp1","8.7.1-5~bpo12+1","8.8.0-1","8.8.0-1+exp1","8.8.0-1+exp2","8.8.0-1~bpo12+1","8.8.0-2","8.8.0-3","8.8.0-4","8.9.0-1","8.9.0-2","8.9.0-3","8.9.1-1","8.9.1-2","8.9.1-2~bpo12+1"]},{"source":"osv","ecosystem":"Debian:13","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.14.1-2","8.14.1-2+deb13u1","8.14.1-2+deb13u2","8.14.1-2+deb13u2~bpo13+1","8.14.1-2+deb13u3","8.14.1-2+deb13u4","8.14.1-2+deb13u5","8.14.1-2+deb13u7","8.14.1-2+exp1","8.15.0-1","8.15.0-1~bpo13+1","8.15.0-1~exp1","8.15.0~rc1-1exp1","8.15.0~rc2-1~exp1","8.15.0~rc3-1~exp1","8.16.0-1","8.16.0-1+exp1","8.16.0-1~bpo13+1","8.16.0-2","8.16.0-3","8.16.0-4","8.16.0-4~bpo13+1","8.16.0~rc1-1~exp1","8.16.0~rc2-1","8.16.0~rc2-2","8.16.0~rc3-1","8.17.0-1","8.17.0-2","8.17.0-3","8.17.0~rc1-1~exp1","8.17.0~rc2-1","8.17.0~rc3-1","8.18.0-1","8.18.0-1~bpo13+1","8.18.0-2","8.18.0~rc1-1+exp1","8.18.0~rc2-1","8.18.0~rc3-1","8.19.0-1","8.19.0-1+exp1","8.19.0-1~bpo13+1","8.19.0-2","8.19.0-3","8.19.0-3+exp1","8.19.0-3+exp2","8.19.0~rc1-1~exp1","8.19.0~rc2-1","8.19.0~rc2-2","8.19.0~rc3-1","8.20.0-1","8.20.0-1+exp","8.20.0-2","8.20.0-2+exp1","8.20.0-2~bpo13+1","8.20.0-3","8.20.0-4","8.20.0-5","8.20.0-5~bpo13+1","8.20.0~rc1-1+exp1","8.20.0~rc1-1+exp2","8.20.0~rc1-1+exp3","8.20.0~rc2-1","8.20.0~rc2-1+exp1","8.20.0~rc3-1","8.20.0~rc3-1+exp1","8.21.0-1","8.21.0-1+exp1","8.21.0-2","8.21.0-2+exp1","8.21.0-2~bpo13+1","8.21.0~rc1-1+exp1","8.21.0~rc2-1","8.21.0~rc2-1+exp1","8.21.0~rc3-1","8.21.0~rc3-1+exp1","8.22.0-1","8.22.0-1+exp1","8.22.0~rc2-1","8.22.0~rc2-2","8.22.0~rc3-1","8.22.0~rc3-1+exp1","8.23.0-1","8.23.0~rc1-1","8.23.0~rc1-2","8.23.0~rc2-1","8.23.0~rc2-1+exp1","8.23.0~rc3-1","8.23.0~rc3-1+exp1"]},{"source":"osv","ecosystem":"Debian:14","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["8.14.1-2","8.14.1-2+exp1","8.15.0-1","8.15.0-1~bpo13+1","8.15.0-1~exp1","8.15.0~rc1-1exp1","8.15.0~rc2-1~exp1","8.15.0~rc3-1~exp1","8.16.0-1","8.16.0-1+exp1","8.16.0-1~bpo13+1","8.16.0-2","8.16.0-3","8.16.0-4","8.16.0-4~bpo13+1","8.16.0~rc1-1~exp1","8.16.0~rc2-1","8.16.0~rc2-2","8.16.0~rc3-1","8.17.0-1","8.17.0-2","8.17.0-3","8.17.0~rc1-1~exp1","8.17.0~rc2-1","8.17.0~rc3-1","8.18.0-1","8.18.0-1~bpo13+1","8.18.0-2","8.18.0~rc1-1+exp1","8.18.0~rc2-1","8.18.0~rc3-1","8.19.0-1","8.19.0-1+exp1","8.19.0-1~bpo13+1","8.19.0-2","8.19.0-3","8.19.0-3+exp1","8.19.0-3+exp2","8.19.0~rc1-1~exp1","8.19.0~rc2-1","8.19.0~rc2-2","8.19.0~rc3-1","8.20.0-1","8.20.0-1+exp","8.20.0-2","8.20.0-2+exp1","8.20.0-2~bpo13+1","8.20.0-3","8.20.0-4","8.20.0-5","8.20.0-5~bpo13+1","8.20.0~rc1-1+exp1","8.20.0~rc1-1+exp2","8.20.0~rc1-1+exp3","8.20.0~rc2-1","8.20.0~rc2-1+exp1","8.20.0~rc3-1","8.20.0~rc3-1+exp1","8.21.0-1","8.21.0-1+exp1","8.21.0-2","8.21.0-2+exp1","8.21.0-2~bpo13+1","8.21.0~rc1-1+exp1","8.21.0~rc2-1","8.21.0~rc2-1+exp1","8.21.0~rc3-1","8.21.0~rc3-1+exp1","8.22.0-1","8.22.0-1+exp1","8.22.0~rc2-1","8.22.0~rc2-2","8.22.0~rc3-1","8.22.0~rc3-1+exp1","8.23.0-1","8.23.0~rc1-1","8.23.0~rc1-2","8.23.0~rc2-1","8.23.0~rc2-1+exp1","8.23.0~rc3-1","8.23.0~rc3-1+exp1"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.0-38.oe2403sp4"}]}],"bundled":15},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.0-38.oe2403sp1"}]}],"bundled":15},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.0-38.oe2403sp3"}]}],"bundled":15},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.23.0-0.1.hum1"}]}],"bundled":26},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"libcurl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.23.0-0.1.hum1"}]}],"bundled":26},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"libcurl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.23.0-0.1.hum1"}]}],"bundled":26},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"libcurl-minimal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.23.0-0.1.hum1"}]}],"bundled":26},{"source":"osv","ecosystem":"Root:Alpine:3.21","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.14.1-r300710"},{"fixed":"8.14.1-r300711"},{"fixed":"8.14.1-r300712"}]}]},{"source":"osv","ecosystem":"Root:Alpine:3.21","package":"rootio-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.14.1-r300710"},{"fixed":"8.14.1-r300711"},{"fixed":"8.14.1-r300712"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.88.1-10+deb12u15.aikido.19"},{"fixed":"7.88.1-10+deb12u15.aikido.20"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.88.1-10+deb12u15.aikido.19"},{"fixed":"7.88.1-10+deb12u15.aikido.20"}]}]},{"source":"osv","ecosystem":"Root:Debian:13","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.14.1-2+deb13u7.aikido.25"}]}]},{"source":"osv","ecosystem":"Root:Debian:13","package":"rootio-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.14.1-2+deb13u7.aikido.25"}]}]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.20.0-2ubuntu11.1"}]}],"versions":["8.18.0-1ubuntu2","8.20.0-2ubuntu1","8.20.0-2ubuntu3","8.20.0-2ubuntu10","8.20.0-2ubuntu11"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.18.0-1ubuntu2.8"}]}],"versions":["8.14.1-2ubuntu1","8.17.0-1ubuntu1","8.18.0-1ubuntu1","8.18.0-1ubuntu2","8.18.0-1ubuntu2.1","8.18.0-1ubuntu2.2","8.18.0-1ubuntu2.3","8.18.0-1ubuntu2.4","8.18.0-1ubuntu2.5","8.18.0-1ubuntu2.7"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.18.0-1ubuntu2.8"}]}],"versions":["8.14.1-2ubuntu1","8.17.0-1ubuntu1","8.18.0-1ubuntu1","8.18.0-1ubuntu2","8.18.0-1ubuntu2.1","8.18.0-1ubuntu2.2","8.18.0-1ubuntu2.3","8.18.0-1ubuntu2.4","8.18.0-1ubuntu2.5","8.18.0-1ubuntu2.7"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.20.0-2ubuntu11.1"}]}],"versions":["8.18.0-1ubuntu2","8.20.0-2ubuntu1","8.20.0-2ubuntu3","8.20.0-2ubuntu10","8.20.0-2ubuntu11"],"bundled":18},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.23.0-1.1"}]}],"bundled":23}],"products":[{"vendor":"curl","product":"curl"}],"references":[{"url":"https://curl.se/docs/CVE-2026-107928.json"},{"url":"https://curl.se/docs/CVE-2026-107928.html","tags":["report"]},{"url":"https://hackerone.com/reports/4099194","tags":["exploit"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107928","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-4c9f-c4pg-phw4"},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-107928","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-107928","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-107928","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4849","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94266","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4851","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4852","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:82895","tags":["advisory"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92392","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92388","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86414","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-14017","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-9086","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-14819","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86410","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92389","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-94265","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-107928","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87866","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-94266","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-107929","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92386","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92391","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92390","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86413","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-92387","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87865","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87863","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87864","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87862","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-87861","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86409","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86411","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-86412","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_82895.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2394750","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-9086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-9086","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2025-9086.html","tags":["article"]},{"url":"https://curl.se/docs/CVE-2025-9086.json","tags":["article"]},{"url":"https://github.com/curl/curl/commit/c6ae07c6a541e0e96d0040afb6","tags":["article"]},{"url":"https://hackerone.com/reports/3294999","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2427870","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-14017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-14017","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2025-14017.html","tags":["article"]},{"url":"https://curl.se/docs/CVE-2025-14017.json","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426408","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-14819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-14819","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2025-14819.html","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550378","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86409","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550356","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86410","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550364","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86411","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550374","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86412","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550594","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86413","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550343","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-86414","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87861","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550638","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87862","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550645","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87863","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87864","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550675","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87865","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550677","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-87866","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550682","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92386","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550691","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92387","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92387","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550692","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92388","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92389","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550702","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92390","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550708","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92391","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2548642","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92392","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550712","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-94265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94265","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550717","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-94266","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550720","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-107928","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2550721","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-107929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107929","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-107928","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8927-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8927-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-86409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-86410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-86412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-86414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-87862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-87863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-87864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-87865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-94266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-107929","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-107928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-107929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-87866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-94265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-94266","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-107928","title":"info leak uploading over WebSockets with GnuTLS","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T20:28:17.712Z","modified":"2026-10-30T16:26:32.201Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"adp"}],"cwes":["CWE-126"],"updated_at":"2026-11-02T13:45:25.313702Z"}],"euvd":[{"id":"EUVD-2026-105357","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T20:28:17Z","modified":"2026-10-30T16:26:32Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:59:05.913237Z"}],"ghsa":[{"id":"GHSA-4c9f-c4pg-phw4","title":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its...","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:31:07Z","modified":"2026-10-30T18:33:24Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-126"],"updated_at":"2026-11-02T15:14:52.01816Z"}],"nvd":[{"id":"CVE-2026-107928","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15.47Z","modified":"2026-10-30T17:17:12.533Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-126"],"updated_at":"2026-11-02T14:13:01.161484Z"}],"osv":[{"id":"ALPINE-CVE-2026-107928","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15.47Z","modified":"2026-10-31T09:30:02.537707943Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:27:50.269992Z"},{"id":"BELL-CVE-2026-107928","title":"CVE-2026-107928 does not affect BellSoft software","status":"withdrawn","published":"2026-10-17T06:05:38.742363Z","modified":"2026-11-02T07:15:02.480829602Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"DEBIAN-CVE-2026-107928","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when `gnutls_record_send()` returns a number of bytes sent **greater than the number of bytes it was given to send**. GnuTLS does that after a blocked send.","status":"published","published":"2026-10-20T21:17:15.47Z","modified":"2026-10-31T10:00:43.569094073Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:49.381767Z"},{"id":"OESA-2026-4849","title":"curl security update","description":"cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.\r\n\r\nSecurity Fix(es):\n\nWhen curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.(CVE-2026-107928)\n\nSetting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication,\ncontrary to expectations and documentation. A subsequent transfer on the same\nhandle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL\nisset next, leaking state information.(CVE-2026-86409)\n\nA flaw in the curl command line tool\u0026apos;s logic makes it only set SSH host\nverification options when interacting directly using SFTP or SCP, and not as a\nresult of following a redirect.(CVE-2026-86410)\n\nAn HTTP proxy can trick libcurl into sending the origin\u0026apos;s credentials (Basic\npassword, or a Negotiate/Kerberos ticket) to the proxy itself, by answering\nthe `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the\nexpected 407 `Proxy-Authenticate:`.(CVE-2026-86414)\n\nImporting a `includeSubDomains` parent HSTS entry before a longer-lived child\nentry, silently drops the child. Consequently, when the parent expires, the\nchild\u0026apos;s valid HSTS policy is lost, causing curl to issue unencrypted HTTP\nrequests rather than upgrading to HTTPS.(CVE-2026-87862)\n\nAn authenticated HTTPS origin can supply an HSTS `max-age` value that the\nparser accepts, but time serialization later fails to process. On 64-bit\nsystems, extreme max-age values compute an absolute expiry within standard\ntime integer limits that exceeds calendar time structure bounds. During cache\nsaves, the original HSTS file is truncated before writing a temporary\nreplacement; when serialization fails, the temporary file is deleted, leaving\nan empty or partial cache. Because the save error is silently ignored during\ncleanup, curl exits successfully despite the data loss.(CVE-2026-87863)\n\nEnabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in\nthe `IMAP APPEND {N}` literal while transmitting line-ending expanded data.\nThe server reads only $N$ bytes for the payload, causing the remaining\noverflow bytes to be interpreted and executed as pipelined IMAP commands\nwithin the authenticated session.(CVE-2026-87864)\n\nWhen libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated\ninitial entry can cause host key validation to report a key *mismatch* as a\n*missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.(CVE-2026-87865)\n\nWhen built with wolfSSL, curl can successfully validate a pinned public key\nhash against a key the TLS peer does not possess. During the TLS handshake,\nwolfSSL validates the connection, but curl\u0026apos;s subsequent re-parsing of the same\ncertificate - tricked by a manipulated validity length field - extracts and\nmatches a different embedded key, incorrectly authorizing the pinned public\nkey.(CVE-2026-87866)\n\nWhen writing a long cookie name and value to a Netscape cookie jar, a remote\nHTTP server can make `curl` write a record that exceeds its line-length\nparsing limit. Consequently, any subsequent `curl` invocation reading from\nthat same cookie jar using `--cookie` silently aborts parsing prematurely upon\nencountering the too long line, ignoring all subsequent valid cookies in the\nfile.(CVE-2026-92386)\n\nWhen an FTP wildcard `LIST` operation fails, libcurl omits the restoration\npath meant for successful listings, leaving the write callback set to the\ninternal listing parser and the write callback data pointing directly to the\neasy handle. Subsequent reuse of this handle triggers an immediate crash, and\ncloning it via `curl_easy_duphandle()` copies this corrupted state into the\nduplicate. If the original handle is subsequently freed, executing a transfer\non the cloned handle causes a heap use-after-free read against the dangling\nhandle reference; alternatively, reusing the original or cloned handle while\nchanging only  `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`)\nresults in type confusion, forcing the internal parser to interpret incoming\nserver response bytes into memory at the application-supplied write data\npointer.(CVE-2026-92388)\n\nlibcurl\u0026apos;s TFTP state machine fails to validate state transitions against the\nrequested transfer direction, accepting opening server responses for both\nreads and writes interchangeably. A malicious TFTP server can respond to a\ndownload request in a way that forces the client into transmit mode, prompting\nlibcurl to consume and transmit data from the handle\u0026apos;s persistent\n`CURLOPT_READDATA` pointer - including data remaining from unrelated prior\noperations, such as an HTTP POST request executed on a reused handle.(CVE-2026-92389)\n\nWhen invoked with `--remote-header-name` (`-J`), curl fails to preserve its\ndocumented anti-clobbering protection if an intermediate 103 Early Hints\nresponse precedes the final HTTP response, or if an `ETag` header is processed\nbefore `Content-Disposition` under `--etag-save`. This flaw allows an HTTP(S)\nserver to overwrite an existing local file specified in the\n`Content-Disposition` header despite the presence of the `-J` non-overwrite\nconstraint.(CVE-2026-92390)\n\nA deeply nested multipart MIME structure constructed via the public API causes\na stack overflow in libcurl during normal cleanup operations. An excessive\nrecursion depth within `curl_mime_free` leads to unbounded stack frame\nallocation during structure traversal, ultimately crashing the host process.(CVE-2026-92391)\n\nlibcurl could accidentally return a URL for `curl_easy_getinfo()`\u0026apos;s\n`CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither\nthe URL provided to libcurl nor the redirected URL did.(CVE-2026-94266)","status":"published","published":"2026-11-11T12:26:48Z","modified":"2026-11-11T12:45:09.653939298Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-11T13:08:46.301371Z"},{"id":"OESA-2026-4851","title":"curl security update","description":"cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.\r\n\r\nSecurity Fix(es):\n\nWhen curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.(CVE-2026-107928)\n\nSetting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication,\ncontrary to expectations and documentation. A subsequent transfer on the same\nhandle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL\nisset next, leaking state information.(CVE-2026-86409)\n\nA flaw in the curl command line tool\u0026apos;s logic makes it only set SSH host\nverification options when interacting directly using SFTP or SCP, and not as a\nresult of following a redirect.(CVE-2026-86410)\n\nAn HTTP proxy can trick libcurl into sending the origin\u0026apos;s credentials (Basic\npassword, or a Negotiate/Kerberos ticket) to the proxy itself, by answering\nthe `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the\nexpected 407 `Proxy-Authenticate:`.(CVE-2026-86414)\n\nImporting a `includeSubDomains` parent HSTS entry before a longer-lived child\nentry, silently drops the child. Consequently, when the parent expires, the\nchild\u0026apos;s valid HSTS policy is lost, causing curl to issue unencrypted HTTP\nrequests rather than upgrading to HTTPS.(CVE-2026-87862)\n\nAn authenticated HTTPS origin can supply an HSTS `max-age` value that the\nparser accepts, but time serialization later fails to process. On 64-bit\nsystems, extreme max-age values compute an absolute expiry within standard\ntime integer limits that exceeds calendar time structure bounds. During cache\nsaves, the original HSTS file is truncated before writing a temporary\nreplacement; when serialization fails, the temporary file is deleted, leaving\nan empty or partial cache. Because the save error is silently ignored during\ncleanup, curl exits successfully despite the data loss.(CVE-2026-87863)\n\nEnabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in\nthe `IMAP APPEND {N}` literal while transmitting line-ending expanded data.\nThe server reads only $N$ bytes for the payload, causing the remaining\noverflow bytes to be interpreted and executed as pipelined IMAP commands\nwithin the authenticated session.(CVE-2026-87864)\n\nWhen libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated\ninitial entry can cause host key validation to report a key *mismatch* as a\n*missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.(CVE-2026-87865)\n\nWhen built with wolfSSL, curl can successfully validate a pinned public key\nhash against a key the TLS peer does not possess. During the TLS handshake,\nwolfSSL validates the connection, but curl\u0026apos;s subsequent re-parsing of the same\ncertificate - tricked by a manipulated validity length field - extracts and\nmatches a different embedded key, incorrectly authorizing the pinned public\nkey.(CVE-2026-87866)\n\nWhen writing a long cookie name and value to a Netscape cookie jar, a remote\nHTTP server can make `curl` write a record that exceeds its line-length\nparsing limit. Consequently, any subsequent `curl` invocation reading from\nthat same cookie jar using `--cookie` silently aborts parsing prematurely upon\nencountering the too long line, ignoring all subsequent valid cookies in the\nfile.(CVE-2026-92386)\n\nWhen an FTP wildcard `LIST` operation fails, libcurl omits the restoration\npath meant for successful listings, leaving the write callback set to the\ninternal listing parser and the write callback data pointing directly to the\neasy handle. Subsequent reuse of this handle triggers an immediate crash, and\ncloning it via `curl_easy_duphandle()` copies this corrupted state into the\nduplicate. If the original handle is subsequently freed, executing a transfer\non the cloned handle causes a heap use-after-free read against the dangling\nhandle reference; alternatively, reusing the original or cloned handle while\nchanging only  `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`)\nresults in type confusion, forcing the internal parser to interpret incoming\nserver response bytes into memory at the application-supplied write data\npointer.(CVE-2026-92388)\n\nlibcurl\u0026apos;s TFTP state machine fails to validate state transitions against the\nrequested transfer direction, accepting opening server responses for both\nreads and writes interchangeably. A malicious TFTP server can respond to a\ndownload request in a way that forces the client into transmit mode, prompting\nlibcurl to consume and transmit data from the handle\u0026apos;s persistent\n`CURLOPT_READDATA` pointer - including data remaining from unrelated prior\noperations, such as an HTTP POST request executed on a reused handle.(CVE-2026-92389)\n\nWhen invoked with `--remote-header-name` (`-J`), curl fails to preserve its\ndocumented anti-clobbering protection if an intermediate 103 Early Hints\nresponse precedes the final HTTP response, or if an `ETag` header is processed\nbefore `Content-Disposition` under `--etag-save`. This flaw allows an HTTP(S)\nserver to overwrite an existing local file specified in the\n`Content-Disposition` header despite the presence of the `-J` non-overwrite\nconstraint.(CVE-2026-92390)\n\nA deeply nested multipart MIME structure constructed via the public API causes\na stack overflow in libcurl during normal cleanup operations. An excessive\nrecursion depth within `curl_mime_free` leads to unbounded stack frame\nallocation during structure traversal, ultimately crashing the host process.(CVE-2026-92391)\n\nlibcurl could accidentally return a URL for `curl_easy_getinfo()`\u0026apos;s\n`CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither\nthe URL provided to libcurl nor the redirected URL did.(CVE-2026-94266)","status":"published","published":"2026-11-11T12:26:50Z","modified":"2026-11-11T12:45:12.569121574Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-11T13:08:46.301371Z"},{"id":"OESA-2026-4852","title":"curl security update","description":"cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.\r\n\r\nSecurity Fix(es):\n\nWhen curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.(CVE-2026-107928)\n\nSetting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication,\ncontrary to expectations and documentation. A subsequent transfer on the same\nhandle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL\nisset next, leaking state information.(CVE-2026-86409)\n\nA flaw in the curl command line tool\u0026apos;s logic makes it only set SSH host\nverification options when interacting directly using SFTP or SCP, and not as a\nresult of following a redirect.(CVE-2026-86410)\n\nAn HTTP proxy can trick libcurl into sending the origin\u0026apos;s credentials (Basic\npassword, or a Negotiate/Kerberos ticket) to the proxy itself, by answering\nthe `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the\nexpected 407 `Proxy-Authenticate:`.(CVE-2026-86414)\n\nImporting a `includeSubDomains` parent HSTS entry before a longer-lived child\nentry, silently drops the child. Consequently, when the parent expires, the\nchild\u0026apos;s valid HSTS policy is lost, causing curl to issue unencrypted HTTP\nrequests rather than upgrading to HTTPS.(CVE-2026-87862)\n\nAn authenticated HTTPS origin can supply an HSTS `max-age` value that the\nparser accepts, but time serialization later fails to process. On 64-bit\nsystems, extreme max-age values compute an absolute expiry within standard\ntime integer limits that exceeds calendar time structure bounds. During cache\nsaves, the original HSTS file is truncated before writing a temporary\nreplacement; when serialization fails, the temporary file is deleted, leaving\nan empty or partial cache. Because the save error is silently ignored during\ncleanup, curl exits successfully despite the data loss.(CVE-2026-87863)\n\nEnabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in\nthe `IMAP APPEND {N}` literal while transmitting line-ending expanded data.\nThe server reads only $N$ bytes for the payload, causing the remaining\noverflow bytes to be interpreted and executed as pipelined IMAP commands\nwithin the authenticated session.(CVE-2026-87864)\n\nWhen libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated\ninitial entry can cause host key validation to report a key *mismatch* as a\n*missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.(CVE-2026-87865)\n\nWhen built with wolfSSL, curl can successfully validate a pinned public key\nhash against a key the TLS peer does not possess. During the TLS handshake,\nwolfSSL validates the connection, but curl\u0026apos;s subsequent re-parsing of the same\ncertificate - tricked by a manipulated validity length field - extracts and\nmatches a different embedded key, incorrectly authorizing the pinned public\nkey.(CVE-2026-87866)\n\nWhen writing a long cookie name and value to a Netscape cookie jar, a remote\nHTTP server can make `curl` write a record that exceeds its line-length\nparsing limit. Consequently, any subsequent `curl` invocation reading from\nthat same cookie jar using `--cookie` silently aborts parsing prematurely upon\nencountering the too long line, ignoring all subsequent valid cookies in the\nfile.(CVE-2026-92386)\n\nWhen an FTP wildcard `LIST` operation fails, libcurl omits the restoration\npath meant for successful listings, leaving the write callback set to the\ninternal listing parser and the write callback data pointing directly to the\neasy handle. Subsequent reuse of this handle triggers an immediate crash, and\ncloning it via `curl_easy_duphandle()` copies this corrupted state into the\nduplicate. If the original handle is subsequently freed, executing a transfer\non the cloned handle causes a heap use-after-free read against the dangling\nhandle reference; alternatively, reusing the original or cloned handle while\nchanging only  `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`)\nresults in type confusion, forcing the internal parser to interpret incoming\nserver response bytes into memory at the application-supplied write data\npointer.(CVE-2026-92388)\n\nlibcurl\u0026apos;s TFTP state machine fails to validate state transitions against the\nrequested transfer direction, accepting opening server responses for both\nreads and writes interchangeably. A malicious TFTP server can respond to a\ndownload request in a way that forces the client into transmit mode, prompting\nlibcurl to consume and transmit data from the handle\u0026apos;s persistent\n`CURLOPT_READDATA` pointer - including data remaining from unrelated prior\noperations, such as an HTTP POST request executed on a reused handle.(CVE-2026-92389)\n\nWhen invoked with `--remote-header-name` (`-J`), curl fails to preserve its\ndocumented anti-clobbering protection if an intermediate 103 Early Hints\nresponse precedes the final HTTP response, or if an `ETag` header is processed\nbefore `Content-Disposition` under `--etag-save`. This flaw allows an HTTP(S)\nserver to overwrite an existing local file specified in the\n`Content-Disposition` header despite the presence of the `-J` non-overwrite\nconstraint.(CVE-2026-92390)\n\nA deeply nested multipart MIME structure constructed via the public API causes\na stack overflow in libcurl during normal cleanup operations. An excessive\nrecursion depth within `curl_mime_free` leads to unbounded stack frame\nallocation during structure traversal, ultimately crashing the host process.(CVE-2026-92391)\n\nlibcurl could accidentally return a URL for `curl_easy_getinfo()`\u0026apos;s\n`CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither\nthe URL provided to libcurl nor the redirected URL did.(CVE-2026-94266)","status":"published","published":"2026-11-11T12:26:51Z","modified":"2026-11-11T12:45:11.721391538Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-11T13:08:46.301371Z"},{"id":"RHSA-2026:82895","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-10-15T10:28:47Z","modified":"2026-10-18T10:05:11Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:23.547034Z"},{"id":"UBUNTU-CVE-2026-107928","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when `gnutls_record_send()` returns a number of bytes sent **greater than the number of bytes it was given to send**. GnuTLS does that after a blocked send.","status":"published","published":"2026-10-14T06:00:00Z","modified":"2026-11-03T21:19:13.232867495Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"AZL-109905","title":"CVE-2026-107928 affecting package cmake 3.30.3-15","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"AZL-109983","title":"CVE-2026-107928 affecting package curl 8.11.1-11","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"AZL-110052","title":"CVE-2026-107928 affecting package mysql 8.0.46-2","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"AZL-110193","title":"CVE-2026-107928 affecting package rust 1.75.0-31","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"AZL-110268","title":"CVE-2026-107928 affecting package rust 1.96.1-2","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"AZL-110298","title":"CVE-2026-107928 affecting package tensorflow 2.16.1-11","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-20T21:17:15Z","modified":"2026-10-27T05:36:16Z","updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"CURL-CVE-2026-107928","title":"info leak uploading over WebSockets with GnuTLS","description":"When curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.","status":"published","published":"2026-10-14T08:00:00Z","modified":"2026-10-25T01:05:09.809818175Z","updated_at":"2026-11-02T15:43:55.998148Z"},{"id":"openSUSE-SU-2026:12150-1","title":"curl-8.23.0-1.1 on GA media","description":"These are all security issues fixed in the curl-8.23.0-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-10-16T00:00:00Z","modified":"2026-10-17T10:00:05.085098051Z","updated_at":"2026-11-02T16:58:40.245664Z"},{"id":"ROOT-OS-ALPINE-321-CVE-2026-107928","title":"CVE-2026-107928 in curl - Patched by Root","description":"Root has patched CVE-2026-107928 in the curl package for Root:Alpine:3.21. Multiple fixed versions available.","status":"published","published":"2026-11-03T11:37:01Z","modified":"2026-11-03T12:15:05.711376885Z","updated_at":"2026-11-03T12:31:35.467775Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-107928","title":"CVE-2026-107928 in curl - Patched by Root","description":"Root has patched CVE-2026-107928 in the curl package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-11-04T06:00:50Z","modified":"2026-11-04T07:15:09.176170648Z","updated_at":"2026-11-04T07:32:10.855619Z"},{"id":"ROOT-OS-DEBIAN-13-CVE-2026-107928","title":"CVE-2026-107928 in curl - Patched by Root","description":"Root has patched CVE-2026-107928 in the curl package for Root:Debian:13. Multiple fixed versions available.","status":"published","published":"2026-11-03T10:50:30Z","modified":"2026-11-03T11:15:05.765588315Z","updated_at":"2026-11-03T11:30:16.221977Z"},{"id":"USN-8927-1","title":"curl vulnerabilities","description":"It was discovered that curl, when built with GnuTLS support, had an\nout-of-bounds read in the WebSocket send path. An attacker could\npossibly use this issue to obtain sensitive information.\n(CVE-2026-107928)\n\nMaksim discovered that curl did not correctly include the interface\nbinding in connection reuse decisions when CURLOPT_INTERFACE was used.\nAn attacker could possibly use this issue to cause connections to go\nout from an unintended source address. (CVE-2026-107929)\n\nStanislav Fort discovered that curl did not properly clear AWS SigV4\nauthentication state when CURLOPT_AWS_SIGV4 was set to NULL. An\nattacker could possibly use this issue to obtain sensitive information.\n(CVE-2026-86409)\n\nStanislav Fort discovered that the curl command line tool did not set\nSSH host verification options when following redirects to SFTP or SCP\nURLs. An attacker could possibly use this issue to perform\nmachine-in-the-middle attacks. (CVE-2026-86410)\n\nStanislav Fort discovered that curl did not properly handle cookie jar\nentries that could not be reloaded. An attacker could possibly use this\nissue to cause a denial of service. (CVE-2026-86412)\n\nStanislav Fort discovered that an HTTP proxy could trick libcurl into\nsending credentials to the proxy itself by responding to a CONNECT\nrequest with an unexpected authentication challenge. An attacker could\npossibly use this issue to obtain sensitive information.\n(CVE-2026-86414)\n\nStanislav Fort discovered that curl did not correctly handle HSTS\nentries when an includeSubDomains parent entry was imported before a\nlonger-lived child entry. An attacker could possibly use this issue to\ncause curl to use unencrypted HTTP connections. (CVE-2026-87862)\n\nStanislav Fort discovered that curl did not properly handle HSTS\nmax-age values that exceeded calendar time structure bounds. An\nattacker could possibly use this issue to cause a denial of service or\ndata loss. (CVE-2026-87863)\n\nStanislav Fort discovered that curl did not properly handle IMAP APPEND\ncommands when CURLOPT_CRLF was enabled, allowing overflow bytes to be\ninterpreted as pipelined commands. An authenticated attacker could\npossibly use this issue to inject arbitrary IMAP commands.\n(CVE-2026-87864)\n\nBobbeh Rhino discovered that libcurl, when used with libssh2 and a\nhashed known_hosts file, could misreport a host key mismatch as a\nmissing key. An attacker could possibly use this issue to perform\nmachine-in-the-middle attacks. (CVE-2026-87865)\n\nJoshua Rogers discovered that curl did not properly handle long cookie\nentries written to a Netscape cookie jar. An attacker could possibly\nuse this issue to cause a denial of service. (CVE-2026-92386)\n\nJoshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP\nserver could cause libcurl to block indefinitely by omitting the final\ncontrol-response line. An attacker could possibly use this issue to\ncause a denial of service. (CVE-2026-92387)\n\nJoshua Rogers discovered that libcurl had a use-after-free\nvulnerability in the FTP wildcard matching code. An attacker could\npossibly use this issue to cause curl to crash, resulting in a denial\nof service, or execute arbitrary code. (CVE-2026-92388)\n\nJoshua Rogers discovered that libcurl's TFTP state machine did not\nproperly validate transfer directions, allowing a malicious server to\nforce the client into transmit mode. An attacker could possibly use\nthis issue to obtain sensitive information. (CVE-2026-92389)\n\nJoshua Rogers discovered that curl did not properly enforce its file\noverwrite protection when using --remote-header-name in certain\ncircumstances. An attacker could possibly use this issue to overwrite\nlocal files. (CVE-2026-92390)\n\nJoshua Rogers discovered that curl had a stack overflow vulnerability\nwhen processing deeply nested MIME structures. An attacker could\npossibly use this issue to cause curl to crash, resulting in a denial\nof service. (CVE-2026-92391)\n\nJoshua Rogers discovered that libcurl could expose credentials in the\nURL returned by CURLINFO_EFFECTIVE_URL when credentials were retrieved\nfrom a .netrc file. An attacker could possibly use this issue to obtain\nsensitive information. (CVE-2026-94266)\n\nJoshua Rogers discovered that libcurl had a use-after-free\nvulnerability during HTTP/2 uploads when handling RST_STREAM responses\nfrom the server. An attacker could possibly use this issue to cause\ncurl to crash, resulting in a denial of service, or execute arbitrary\ncode. (CVE-2026-92392)","status":"published","published":"2026-10-14T11:58:06Z","modified":"2026-11-03T21:19:25.73264429Z","updated_at":"2026-11-03T21:43:32.336286Z"},{"id":"USN-8927-2","title":"curl vulnerabilities","description":"USN-8927-1 fixed vulnerabilities in curl. This update provides the\ncorresponding fixes for Ubuntu 26.10.\n\nOriginal advisory details:\n\n It was discovered that curl, when built with GnuTLS support, had an\n out-of-bounds read in the WebSocket send path. An attacker could\n possibly use this issue to obtain sensitive information.\n (CVE-2026-107928)\n\n Maksim discovered that curl did not correctly include the interface\n binding in connection reuse decisions when CURLOPT_INTERFACE was used.\n An attacker could possibly use this issue to cause connections to go\n out from an unintended source address. (CVE-2026-107929)\n\n Stanislav Fort discovered that curl did not properly clear AWS SigV4\n authentication state when CURLOPT_AWS_SIGV4 was set to NULL. An\n attacker could possibly use this issue to obtain sensitive information.\n (CVE-2026-86409)\n\n Stanislav Fort discovered that the curl command line tool did not set\n SSH host verification options when following redirects to SFTP or SCP\n URLs. An attacker could possibly use this issue to perform\n machine-in-the-middle attacks. (CVE-2026-86410)\n\n Stanislav Fort discovered that curl did not properly handle cookie jar\n entries that could not be reloaded. An attacker could possibly use this\n issue to cause a denial of service. (CVE-2026-86412)\n\n Stanislav Fort discovered that an HTTP proxy could trick libcurl into\n sending credentials to the proxy itself by responding to a CONNECT\n request with an unexpected authentication challenge. An attacker could\n possibly use this issue to obtain sensitive information.\n (CVE-2026-86414)\n\n Stanislav Fort discovered that curl did not correctly handle HSTS\n entries when an includeSubDomains parent entry was imported before a\n longer-lived child entry. An attacker could possibly use this issue to\n cause curl to use unencrypted HTTP connections. (CVE-2026-87862)\n\n Stanislav Fort discovered that curl did not properly handle HSTS\n max-age values that exceeded calendar time structure bounds. An\n attacker could possibly use this issue to cause a denial of service or\n data loss. (CVE-2026-87863)\n\n Stanislav Fort discovered that curl did not properly handle IMAP APPEND\n commands when CURLOPT_CRLF was enabled, allowing overflow bytes to be\n interpreted as pipelined commands. An authenticated attacker could\n possibly use this issue to inject arbitrary IMAP commands.\n (CVE-2026-87864)\n\n Bobbeh Rhino discovered that libcurl, when used with libssh2 and a\n hashed known_hosts file, could misreport a host key mismatch as a\n missing key. An attacker could possibly use this issue to perform\n machine-in-the-middle attacks. (CVE-2026-87865)\n\n Joshua Rogers discovered that curl did not properly handle long cookie\n entries written to a Netscape cookie jar. An attacker could possibly\n use this issue to cause a denial of service. (CVE-2026-92386)\n\n Joshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP\n server could cause libcurl to block indefinitely by omitting the final\n control-response line. An attacker could possibly use this issue to\n cause a denial of service. (CVE-2026-92387)\n\n Joshua Rogers discovered that libcurl had a use-after-free\n vulnerability in the FTP wildcard matching code. An attacker could\n possibly use this issue to cause curl to crash, resulting in a denial\n of service, or execute arbitrary code. (CVE-2026-92388)\n\n Joshua Rogers discovered that libcurl's TFTP state machine did not\n properly validate transfer directions, allowing a malicious server to\n force the client into transmit mode. An attacker could possibly use\n this issue to obtain sensitive information. (CVE-2026-92389)\n\n Joshua Rogers discovered that curl did not properly enforce its file\n overwrite protection when using --remote-header-name in certain\n circumstances. An attacker could possibly use this issue to overwrite\n local files. (CVE-2026-92390)\n\n Joshua Rogers discovered that curl had a stack overflow vulnerability\n when processing deeply nested MIME structures. An attacker could\n possibly use this issue to cause curl to crash, resulting in a denial\n of service. (CVE-2026-92391)\n\n Joshua Rogers discovered that libcurl could expose credentials in the\n URL returned by CURLINFO_EFFECTIVE_URL when credentials were retrieved\n from a .netrc file. An attacker could possibly use this issue to obtain\n sensitive information. (CVE-2026-94266)\n\n Joshua Rogers discovered that libcurl had a use-after-free\n vulnerability during HTTP/2 uploads when handling RST_STREAM responses\n from the server. An attacker could possibly use this issue to cause\n curl to crash, resulting in a denial of service, or execute arbitrary\n code. (CVE-2026-92392)","status":"published","published":"2026-10-19T15:51:17Z","modified":"2026-11-03T21:19:25.726716316Z","updated_at":"2026-11-03T21:43:32.336286Z"}]}}