CVE-2026-84380

MEDIUMPre-NVD 5.65.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.6
EG Score
5.6(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 2, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v2.11.0

Patch available: pydantic/httpx2 v2.11.0

https://github.com/pydantic/httpx2/releases/tag/v2.11.0
github_commit Patch Available

commit 829b93a23932 (pydantic/httpx2)

Patch available: pydantic/httpx2 v2.11.0 (contains commit 829b93a23932)

https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab
github_pr Patch Available

Respect explicit Transfer-Encoding headers

Patch available: pydantic/httpx2 v2.11.0 (PR #1137 merged 2026-08-13)

https://github.com/pydantic/httpx2/pull/1137
github Patch Available

Conflicting Content-Length and Transfer-Encoding headers can be auto-generated · Advisory · pydantic/httpx2 · GitHub

https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566

Vendor Advisories for CVE-2026-84380(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-httpx22.4.0-1, 2.5.0-12.12.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
httpx20.0.0 ... 2.9.1 (14 versions)2.11.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 12:42 UTCEG score recompute
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-17 10:53 UTCEG score recompute
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 09:04 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 06:15 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 04:26 UTCEG score recompute
  12. 2026-09-13 02:37 UTCEG score recompute
  13. 2026-09-12 00:48 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 22:59 UTCEG score recompute
  17. 2026-09-09 06:42 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 04:54 UTCEG score recompute
  20. 2026-09-07 03:05 UTCEG score recompute
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-06 01:15 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 23:26 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 4 more
  1. 2026-09-02 19:31 UTCEG score recompute
  2. 2026-09-02 18:30 UTCEG score recompute
  3. 2026-09-02 18:03 UTCEG score recompute
  4. 2026-09-02 18:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84380?
CVE-2026-84380 is a medium vulnerability published on September 2, 2026. 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…
When was CVE-2026-84380 disclosed?
CVE-2026-84380 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84380 actively exploited?
CVE-2026-84380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-84380?
CVE-2026-84380 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2026-84380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84380, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84380

Explore →

Is Your Infrastructure Affected by CVE-2026-84380?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs