{"api_version":"1","generated_at":"2026-09-03T22:54:31+00:00","cve":"CVE-2026-84380","urls":{"html":"https://cve.report/CVE-2026-84380","api":"https://cve.report/api/cve/CVE-2026-84380.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-84380","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-84380"},"summary":{"title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated","description":"HTTPX2 is a next generation HTTP client for Python. Prior to 2.11.0, Request._prepare() in src/httpx2/httpx2/_models.py can add a body-derived Content-Length header to a request that already contains a caller-supplied Transfer-Encoding header because its setdefault() processing checks each default header independently rather than treating the two framing headers as mutually exclusive. Fixed-size byte, JSON, form, and known-length multipart bodies can therefore be serialized over HTTP/1.1 with both headers, allowing request smuggling or connection desynchronization when downstream intermediaries disagree about which framing header takes precedence. This issue is fixed in version 2.11.0.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-09-02 18:21:29","updated_at":"2026-09-02 19:18:08"},"problem_types":["CWE-444","CWE-444 CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"5.6","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","baseScore":5.6,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"LOW"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"5.6","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","data":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":5.6,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"}}],"references":[{"url":"https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab","name":"https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/pydantic/httpx2/releases/tag/v2.11.0","name":"https://github.com/pydantic/httpx2/releases/tag/v2.11.0","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/pydantic/httpx2/pull/1137","name":"https://github.com/pydantic/httpx2/pull/1137","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566","name":"https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-84380","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84380","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"pydantic","product":"httpx2","version":"affected < 2.11.0","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-84380","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-09-02T18:07:09.850518Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-09-02T18:07:36.980Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"product":"httpx2","vendor":"pydantic","versions":[{"status":"affected","version":"< 2.11.0"}]}],"descriptions":[{"lang":"en","value":"HTTPX2 is a next generation HTTP client for Python. Prior to 2.11.0, Request._prepare() in src/httpx2/httpx2/_models.py can add a body-derived Content-Length header to a request that already contains a caller-supplied Transfer-Encoding header because its setdefault() processing checks each default header independently rather than treating the two framing headers as mutually exclusive. Fixed-size byte, JSON, form, and known-length multipart bodies can therefore be serialized over HTTP/1.1 with both headers, allowing request smuggling or connection desynchronization when downstream intermediaries disagree about which framing header takes precedence. This issue is fixed in version 2.11.0."}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":5.6,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-444","description":"CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-02T17:58:55.520Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566","tags":["x_refsource_CONFIRM"],"url":"https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566"},{"name":"https://github.com/pydantic/httpx2/pull/1137","tags":["x_refsource_MISC"],"url":"https://github.com/pydantic/httpx2/pull/1137"},{"name":"https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab","tags":["x_refsource_MISC"],"url":"https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab"},{"name":"https://github.com/pydantic/httpx2/releases/tag/v2.11.0","tags":["x_refsource_MISC"],"url":"https://github.com/pydantic/httpx2/releases/tag/v2.11.0"}],"source":{"advisory":"GHSA-pf96-p4fj-6566","discovery":"UNKNOWN"},"title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-84380","datePublished":"2026-09-02T17:58:55.520Z","dateReserved":"2026-09-01T16:27:58.130Z","dateUpdated":"2026-09-02T18:07:36.980Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-02 18:21:29","lastModifiedDate":"2026-09-02 19:18:08","problem_types":["CWE-444","CWE-444 CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","baseScore":5.6,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"LOW"},"exploitabilityScore":2.2,"impactScore":3.4}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-09-02T18:07:09.850518Z","id":"CVE-2026-84380","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"84380","Ordinal":"1","Title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers","CVE":"CVE-2026-84380","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"84380","Ordinal":"1","NoteData":"HTTPX2 is a next generation HTTP client for Python. Prior to 2.11.0, Request._prepare() in src/httpx2/httpx2/_models.py can add a body-derived Content-Length header to a request that already contains a caller-supplied Transfer-Encoding header because its setdefault() processing checks each default header independently rather than treating the two framing headers as mutually exclusive. Fixed-size byte, JSON, form, and known-length multipart bodies can therefore be serialized over HTTP/1.1 with both headers, allowing request smuggling or connection desynchronization when downstream intermediaries disagree about which framing header takes precedence. This issue is fixed in version 2.11.0.","Type":"Description","Title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers"}]}}}