{"id":"CVE-2025-43859","aliases":["CLSA-2026-1767571924","CLSA-2026-1790929139","DEBIAN-CVE-2025-43859","EUVD-2025-11981","GHSA-vqfr-h8mv-ghfj","OESA-2025-1496","OESA-2025-1497","PYSEC-2026-348","RHSA-2025:7535","RHSA-2025:7536","ROOT-APP-PYPI-CVE-2025-43859","SUSE-SU-2025:1430-1","SUSE-SU-2025:20330-1","SUSE-SU-2025:20331-1","UBUNTU-CVE-2025-43859","USN-7503-1","openSUSE-SU-2025:15032-1"],"status":"published","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","severity":{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00594,"percentile":0.48684,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-444"],"published":"2025-04-24T16:07:56Z","modified":"2026-10-28T02:31:04Z","fixes":[{"ecosystem":"PyPI","package":"h11","fixed_in":["0.16.0"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:PyPI","package":"h11","fixed_in":["0.9.0.post1+tuxcare","0.12.0.post1+tuxcare"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"python-h11","fixed_in":["0.14.0-1.1~deb12u1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"python-h11","fixed_in":["0.14.0-1.1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"python-h11","fixed_in":["0.14.0-1.1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP1","package":"python-h11","fixed_in":["0.14.0-2.oe2403sp1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS","package":"python-h11","fixed_in":["0.14.0-2.oe2403"],"sources":["osv"]},{"ecosystem":"Red Hat:openstack:18.0::el9","package":"python-h11","fixed_in":["0:0.12.0-4.el9ost"],"sources":["osv"]},{"ecosystem":"Red Hat:openstack:18.0::el9","package":"python3-h11","fixed_in":["0:0.12.0-4.el9ost"],"sources":["osv"]},{"ecosystem":"Red Hat:openstack:17.1::el9","package":"python-h11","fixed_in":["0:0.12.0-2.1.el9ost"],"sources":["osv"]},{"ecosystem":"Red Hat:openstack:17.1::el9","package":"python3-h11","fixed_in":["0:0.12.0-2.1.el9ost"],"sources":["osv"]},{"ecosystem":"Root:PyPI","package":"rootio-h11","fixed_in":["0.14.0+root.io.1","0.12.0+root.io.1","0.12.0+root.io.2","0.14.0+root.io.2"],"sources":["osv"]},{"ecosystem":"Root:PyPI","package":"h11","fixed_in":["0.12.0+aikido.2","0.14.0+aikido.2"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Python 3 15 SP6","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"python-h11","fixed_in":["0.14.0-150400.9.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.1","package":"python-h11","fixed_in":["0.16.0-slfo.1.1_1.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.1","package":"python-httpcore","fixed_in":["0.16.3-slfo.1.1_2.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.0","package":"python-h11","fixed_in":["0.16.0-1.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.0","package":"python-httpcore","fixed_in":["0.16.3-7.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"python-h11","fixed_in":["0.14.0-1ubuntu0.24.04.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"python-h11","fixed_in":["0.16.0-1.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0"}]}]},{"source":"osv","ecosystem":"TuxCare:PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.9.0"},{"fixed":"0.9.0.post1+tuxcare"}]}],"versions":["0.9.0"]},{"source":"osv","ecosystem":"TuxCare:PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.12.0"},{"fixed":"0.12.0.post1+tuxcare"}]}],"versions":["0.12.0"]},{"source":"osv","ecosystem":"Debian:12","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-1.1~deb12u1"}]}],"versions":["0.14.0-1"]},{"source":"osv","ecosystem":"Debian:13","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-1.1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-1.1"}]}]},{"source":"osv","ecosystem":"PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0"}]}],"versions":["0.0.1","0.10.0","0.11.0","0.12.0","0.13.0","0.14.0","0.15.0","0.5.0","0.6.0","0.7.0","0.8.0","0.8.1","0.9.0"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-2.oe2403sp1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-2.oe2403"}]}]},{"source":"osv","ecosystem":"PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0"}]}],"versions":["0.0.1","0.10.0","0.11.0","0.12.0","0.13.0","0.14.0","0.15.0","0.5.0","0.6.0","0.7.0","0.8.0","0.8.1","0.9.0"]},{"source":"osv","ecosystem":"Red Hat:openstack:18.0::el9","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.12.0-4.el9ost"}]}]},{"source":"osv","ecosystem":"Red Hat:openstack:18.0::el9","package":"python3-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.12.0-4.el9ost"}]}]},{"source":"osv","ecosystem":"Red Hat:openstack:17.1::el9","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.12.0-2.1.el9ost"}]}]},{"source":"osv","ecosystem":"Red Hat:openstack:17.1::el9","package":"python3-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.12.0-2.1.el9ost"}]}]},{"source":"osv","ecosystem":"Root:PyPI","package":"rootio-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0+root.io.1"},{"fixed":"0.12.0+root.io.1"},{"fixed":"0.12.0+root.io.2"},{"fixed":"0.14.0+root.io.2"}]}]},{"source":"osv","ecosystem":"Root:PyPI","package":"h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.12.0+aikido.2"},{"fixed":"0.14.0+aikido.2"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Python 3 15 SP6","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-150400.9.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0-slfo.1.1_1.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"python-httpcore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.3-slfo.1.1_2.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0-1.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"python-httpcore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.3-7.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-1ubuntu0.24.04.1"}]}],"versions":["0.14.0-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.0-1ubuntu0.24.04.1"}]}],"versions":["0.14.0-1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-h11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0-1.1"}]}]}],"products":[{"vendor":"python-hyper","product":"h11"}],"references":[{"url":"https://github.com/python-hyper/h11/security/advisories/GHSA-vqfr-h8mv-ghfj","tags":["x_refsource_CONFIRM","advisory","web","article","report"]},{"url":"https://github.com/python-hyper/h11/commit/114803a29ce50116dc47951c690ad4892b1a36ed","tags":["x_refsource_MISC","fix","web","article","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-43859","tags":["advisory"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/h11/PYSEC-2026-348.yaml","tags":["web"]},{"url":"https://pypi.org/project/h11","tags":["web","package"]},{"url":"https://github.com/advisories/GHSA-vqfr-h8mv-ghfj","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/43xxx/CVE-2025-43859.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-43859","tags":["advisory"]},{"url":"https://github.com/python-hyper/h11","tags":["package"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1496","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1497","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7535","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2362162","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7535.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-43859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-43859","tags":["advisory","report"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7536","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7536.json","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251430-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1241872","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-43859","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520330-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520331-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-43859","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7503-1","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-43859","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T18:15:53.328Z","modified":"2025-04-24T19:02:45.13Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical","assessor":"cna"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:32:27.28543Z"}],"euvd":[{"id":"EUVD-2025-11981","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T18:15:53Z","modified":"2025-04-24T19:02:45Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T20:52:03.523577Z"}],"ghsa":[{"id":"GHSA-vqfr-h8mv-ghfj","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"### Impact\n\nA leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions.\n\n### Details\n\nHTTP/1.1 Chunked-Encoding bodies are formatted as a sequence of \"chunks\", each of which consists of:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- `\\r\\n`\n\nIn versions of h11 up to 0.14.0, h11 instead parsed them as:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- any two bytes\n\ni.e. it did not validate that the trailing `\\r\\n` bytes were correct, and if you put 2 bytes of garbage there it would be accepted, instead of correctly rejecting the body as malformed.\n\nBy itself this is harmless. However, suppose you have a proxy or reverse-proxy that tries to analyze HTTP requests, and your proxy has a _different_ bug in parsing Chunked-Encoding, acting as if the format is:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- more bytes of content, as many as it takes until you find a `\\r\\n`\n\nFor example, [pound](https://github.com/graygnuorg/pound/pull/43) had this bug -- it can happen if an implementer uses a generic \"read until end of line\" helper to consumes the trailing `\\r\\n`.\n\nIn this case, h11 and your proxy may both accept the same stream of bytes, but interpret them differently. For example, consider the following HTTP request(s) (assume all line breaks are `\\r\\n`):\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n5\nAAAAAXX2\n45\n0\n\nGET /two HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n0\n```\n\nHere h11 will interpret it as two requests, one with body `AAAAA45` and one with an empty body, while our hypothetical buggy proxy will interpret it as a single request, with body `AAAAXX20\\r\\n\\r\\nGET /two ...`. And any time two HTTP processors both accept the same string of bytes but interpret them differently, you have the conditions for a \"request smuggling\" attack. For example, if `/two` is a dangerous endpoint and the job of the reverse proxy is to stop requests from getting there, then an attacker could use a bytestream like the above to circumvent this protection.\n\nEven worse, if our buggy reverse proxy receives two requests from different users:\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n5\nAAAAAXX999\n0\n```\n\n```\nGET /two HTTP/1.1\nHost: localhost\nCookie: SESSION_KEY=abcdef...\n```\n\n...it will consider the first request to be complete and valid, and send both on to the h11-based web server over the same socket. The server will then see the two concatenated requests, and interpret them as _one_ request to `/one` whose body includes `/two`'s session key, potentially allowing one user to steal another's credentials.\n\n### Patches\n\nFixed in h11 0.15.0.\n\n### Workarounds\n\nSince exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.\n\n### Credits\n\nReported by Jeppe Bonde Weikop on 2025-01-09.","status":"published","published":"2025-04-24T16:07:56Z","modified":"2026-10-27T16:31:16Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:41:38.969831Z"}],"nvd":[{"id":"CVE-2025-43859","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T19:15:47.06Z","modified":"2026-06-17T09:24:39.58Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical","assessor":"secondary"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T14:11:02.570368Z"}],"osv":[{"id":"CVE-2025-43859","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T18:15:53.328Z","modified":"2026-10-28T02:31:04.405279129Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T15:44:49.707645Z"},{"id":"DEBIAN-CVE-2025-43859","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T19:15:47.06Z","modified":"2026-09-01T20:05:53.122988517Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:45:47.378563Z"},{"id":"GHSA-vqfr-h8mv-ghfj","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"### Impact\n\nA leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions.\n\n### Details\n\nHTTP/1.1 Chunked-Encoding bodies are formatted as a sequence of \"chunks\", each of which consists of:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- `\\r\\n`\n\nIn versions of h11 up to 0.14.0, h11 instead parsed them as:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- any two bytes\n\ni.e. it did not validate that the trailing `\\r\\n` bytes were correct, and if you put 2 bytes of garbage there it would be accepted, instead of correctly rejecting the body as malformed.\n\nBy itself this is harmless. However, suppose you have a proxy or reverse-proxy that tries to analyze HTTP requests, and your proxy has a _different_ bug in parsing Chunked-Encoding, acting as if the format is:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- more bytes of content, as many as it takes until you find a `\\r\\n`\n\nFor example, [pound](https://github.com/graygnuorg/pound/pull/43) had this bug -- it can happen if an implementer uses a generic \"read until end of line\" helper to consumes the trailing `\\r\\n`.\n\nIn this case, h11 and your proxy may both accept the same stream of bytes, but interpret them differently. For example, consider the following HTTP request(s) (assume all line breaks are `\\r\\n`):\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n5\nAAAAAXX2\n45\n0\n\nGET /two HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n0\n```\n\nHere h11 will interpret it as two requests, one with body `AAAAA45` and one with an empty body, while our hypothetical buggy proxy will interpret it as a single request, with body `AAAAXX20\\r\\n\\r\\nGET /two ...`. And any time two HTTP processors both accept the same string of bytes but interpret them differently, you have the conditions for a \"request smuggling\" attack. For example, if `/two` is a dangerous endpoint and the job of the reverse proxy is to stop requests from getting there, then an attacker could use a bytestream like the above to circumvent this protection.\n\nEven worse, if our buggy reverse proxy receives two requests from different users:\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n5\nAAAAAXX999\n0\n```\n\n```\nGET /two HTTP/1.1\nHost: localhost\nCookie: SESSION_KEY=abcdef...\n```\n\n...it will consider the first request to be complete and valid, and send both on to the h11-based web server over the same socket. The server will then see the two concatenated requests, and interpret them as _one_ request to `/one` whose body includes `/two`'s session key, potentially allowing one user to steal another's credentials.\n\n### Patches\n\nFixed in h11 0.15.0.\n\n### Workarounds\n\nSince exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.\n\n### Credits\n\nReported by Jeppe Bonde Weikop on 2025-01-09.","status":"published","published":"2025-04-24T16:07:56Z","modified":"2026-10-27T16:45:03.53558404Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"cwes":["CWE-444"],"updated_at":"2026-11-02T15:46:57.694388Z"},{"id":"OESA-2025-1496","title":"python-h11 security update","description":"h11 is suitable for implementing both servers and clients, and has a pleasantly symmetric API: the events you send as a client are exactly the ones that you receive as a server and vice-versa.\r\n\r\nSecurity Fix(es):\n\nh11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11\u0026apos;s parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.(CVE-2025-43859)","status":"published","published":"2025-05-09T11:08:35Z","modified":"2026-08-18T01:17:52.476731755Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"OESA-2025-1497","title":"python-h11 security update","description":"h11 is suitable for implementing both servers and clients, and has a pleasantly symmetric API: the events you send as a client are exactly the ones that you receive as a server and vice-versa.\r\n\r\nSecurity Fix(es):\n\nh11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11\u0026apos;s parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.(CVE-2025-43859)","status":"published","published":"2025-05-09T11:08:35Z","modified":"2026-08-18T01:17:52.425310112Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"PYSEC-2026-348","title":"h11 accepts some malformed Chunked-Encoding bodies","description":"### Impact\n\nA leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions.\n \n### Details\n\nHTTP/1.1 Chunked-Encoding bodies are formatted as a sequence of \"chunks\", each of which consists of:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- `\\r\\n`\n\nIn versions of h11 up to 0.14.0, h11 instead parsed them as:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- any two bytes\n \ni.e. it did not validate that the trailing `\\r\\n` bytes were correct, and if you put 2 bytes of garbage there it would be accepted, instead of correctly rejecting the body as malformed.\n\nBy itself this is harmless. However, suppose you have a proxy or reverse-proxy that tries to analyze HTTP requests, and your proxy has a _different_ bug in parsing Chunked-Encoding, acting as if the format is:\n\n- chunk length\n- `\\r\\n`\n- `length` bytes of content\n- more bytes of content, as many as it takes until you find a `\\r\\n`\n\nFor example, [pound](https://github.com/graygnuorg/pound/pull/43) had this bug -- it can happen if an implementer uses a generic \"read until end of line\" helper to consumes the trailing `\\r\\n`.\n\nIn this case, h11 and your proxy may both accept the same stream of bytes, but interpret them differently. For example, consider the following HTTP request(s) (assume all line breaks are `\\r\\n`):\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n \n5\nAAAAAXX2\n45\n0\n\nGET /two HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n \n0\n```\n\nHere h11 will interpret it as two requests, one with body `AAAAA45` and one with an empty body, while our hypothetical buggy proxy will interpret it as a single request, with body `AAAAXX20\\r\\n\\r\\nGET /two ...`. And any time two HTTP processors both accept the same string of bytes but interpret them differently, you have the conditions for a \"request smuggling\" attack. For example, if `/two` is a dangerous endpoint and the job of the reverse proxy is to stop requests from getting there, then an attacker could use a bytestream like the above to circumvent this protection.\n\nEven worse, if our buggy reverse proxy receives two requests from different users:\n\n```\nGET /one HTTP/1.1\nHost: localhost\nTransfer-Encoding: chunked\n\n5\nAAAAAXX999\n0\n```\n\n```\nGET /two HTTP/1.1\nHost: localhost\nCookie: SESSION_KEY=abcdef...\n```\n\n...it will consider the first request to be complete and valid, and send both on to the h11-based web server over the same socket. The server will then see the two concatenated requests, and interpret them as _one_ request to `/one` whose body includes `/two`'s session key, potentially allowing one user to steal another's credentials.\n\n### Patches\n\nFixed in h11 0.15.0.\n \n### Workarounds\n\nSince exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.\n\n### Credits\n\nReported by Jeppe Bonde Weikop on 2025-01-09.","status":"published","published":"2026-06-29T11:50:35.684909Z","modified":"2026-07-01T20:22:54.082067Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:56.847083Z"},{"id":"RHSA-2025:7535","title":"Red Hat Security Advisory: Red Hat OpenStack Platform 18.0 (python-h11) security update","status":"published","published":"2025-05-14T10:06:53Z","modified":"2026-10-16T10:09:18Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7536","title":"Red Hat Security Advisory: Red Hat OpenStack Platform 17.1 (python-h11) security update","status":"published","published":"2025-05-14T10:06:54Z","modified":"2026-10-16T10:09:18Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"ROOT-APP-PYPI-CVE-2025-43859","title":"CVE-2025-43859 in rootio-h11 - Patched by Root","description":"Root has patched CVE-2025-43859 in the rootio-h11 package for Root:PyPI. Multiple fixed versions available.","status":"published","published":"2026-06-03T14:52:07Z","modified":"2026-06-03T19:30:16.781203824Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:53:27.940619Z"},{"id":"UBUNTU-CVE-2025-43859","description":"h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.","status":"published","published":"2025-04-24T19:15:00Z","modified":"2026-02-04T03:16:51.852527Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T16:55:50.31802Z"},{"id":"CLSA-2026-1767571924","title":"TuxCare security update for h11 (1 CVE)","description":"TuxCare rebuilt h11 to address 1 CVE. Fixed in 0.9.0.post1+tuxcare.","status":"published","published":"2026-08-04T14:52:09Z","modified":"2026-10-15T09:47:41.928904126Z","updated_at":"2026-11-02T15:43:42.847264Z"},{"id":"CLSA-2026-1790929139","title":"TuxCare security update for h11 (1 CVE)","description":"TuxCare rebuilt h11 to address 1 CVE. Fixed in 0.12.0.post1+tuxcare.","status":"published","published":"2026-10-02T08:18:59Z","modified":"2026-10-15T09:47:42.005937921Z","updated_at":"2026-11-02T15:43:49.016976Z"},{"id":"openSUSE-SU-2025:15032-1","title":"python311-h11-0.16.0-1.1 on GA media","description":"These are all security issues fixed in the python311-h11-0.16.0-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-04-25T00:00:00Z","modified":"2026-02-04T02:15:09.892349Z","updated_at":"2026-11-02T16:58:37.399567Z"},{"id":"SUSE-SU-2025:1430-1","title":"Security update for python-h11","description":"This update for python-h11 fixes the following issues:\n\n- CVE-2025-43859: leniency when parsing of line terminators in chunked-coding message bodies can lead to request\n  smuggling. (bsc#1241872)\n","status":"published","published":"2025-05-02T08:10:35Z","modified":"2026-03-23T04:48:06.915999Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20330-1","title":"Security update for python-h11, python-httpcore","description":"This update for python-h11, python-httpcore fixes the following issues:\n\npython-h11:\n  - Update 0.16.0:\n    * CVE-2025-43859: Fixed accepting of malformed Chunked-Encoding bodies (bsc#1241872)\n  - 0.15.0:\n    * Reject Content-Lengths \u003e= 1 zettabyte (1 billion terabytes) early,\n      without attempting to parse the integer (#181)\n\npython-httpcore:\n  - CVE-2025-43859: Fixed accepting of malformed Chunked-Encoding bodies (bsc#1241872) \n","status":"published","published":"2025-05-20T08:39:06Z","modified":"2026-03-23T04:50:46.414751Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20331-1","title":"Security update for python-httpcore, python-h11","description":"This update for python-httpcore, python-h11 fixes the following issues:\n\npython-h11:\n  - Update 0.16.0:\n    * CVE-2025-43859: Fixed accepting of malformed Chunked-Encoding bodies (bsc#1241872)\n  - 0.15.0:\n    * Reject Content-Lengths \u003e= 1 zettabyte (1 billion terabytes) early,\n      without attempting to parse the integer (#181)\n\npython-httpcore:\n  - CVE-2025-43859: Fixed accepting of malformed Chunked-Encoding bodies (bsc#1241872)\n","status":"published","published":"2025-05-20T08:49:02Z","modified":"2026-03-23T04:48:13.961484Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-7503-1","title":"python-h11 vulnerability","description":"Jeppe Bonde Weikop discovered that h11 incorrectly handled crafted HTTP\nrequests. A remote attacker could possibly use this issue to smuggle\nmalicious HTTP requests, which could potentially lead to security\ncontrol bypass and information leakage.","status":"published","published":"2025-05-08T10:53:58Z","modified":"2026-02-10T04:48:36Z","updated_at":"2026-11-02T16:58:19.988474Z"}]}}