CVE-2026-73812

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

A fix is available — apply it.

httpd function check_header/3 rejects duplicate Content-Length (per CVE-2026-23941) but never checks for the TE+CL co-presence that RFC 9112 §6.3 identifies as a probable smuggling attempt. handle_body/3 frames by chunked and silently discards Content-Length. A CL-preferring front-end paired with chunked-preferring inets creates a classic CL.TE front-end/back-end desync.

This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2. Whether OTP before OTP 17.0, corresponding to inets before 5.10, is affected is unknown.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Sep 1, 2026
Patch available. Sources: github_commit, github.
github_commit

commit 591dc00dc99d (erlang/otp)

Fix landed in erlang/otp commit 591dc00dc99d — awaiting tagged release

https://github.com/erlang/otp/commit/591dc00dc99dc2a426167a3b5257c0c94bd45e91
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-73812
generic

CVE-2026-73812

https://cna.erlef.org/cves/CVE-2026-73812.html
github Patch Available

HTTP Request Smuggling via Transfer-Encoding and Content-Length in httpd · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-7j6m-4ffg-hg46

Vendor Advisories for CVE-2026-73812(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhaterlang27-main-27.3.4.17-0.1.hum12026-09-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (79 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (40 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (37 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 71× 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-19 16:01 UTCEG score recompute
  2. 2026-09-19 16:01 UTCVendor advisory
  3. 2026-09-19 05:11 UTCEG score recompute
  4. 2026-09-19 05:11 UTCVendor advisory
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 18:22 UTCVendor advisory
  7. 2026-09-18 07:33 UTCVendor advisory
  8. 2026-09-17 20:44 UTCEG score recompute
  9. 2026-09-17 20:44 UTCVendor advisory
  10. 2026-09-17 06:50 UTCVendor advisory
  11. 2026-09-16 20:00 UTCEG score recompute
  12. 2026-09-16 20:00 UTCVendor advisory
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 09:06 UTCEG score recompute
  15. 2026-09-16 09:06 UTCVendor advisory
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 20:54 UTCVendor advisory
  18. 2026-09-15 09:43 UTCEG score recompute
  19. 2026-09-15 09:43 UTCVendor advisory
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 22:54 UTCVendor advisory
  22. 2026-09-14 12:05 UTCVendor advisory
  23. 2026-09-14 01:16 UTCEG score recompute
  24. 2026-09-14 01:16 UTCVendor advisory
  25. 2026-09-13 14:27 UTCVendor advisory
Show 46 more
  1. 2026-09-13 03:38 UTCVendor advisory
  2. 2026-09-12 16:49 UTCEG score recompute
  3. 2026-09-12 16:49 UTCVendor advisory
  4. 2026-09-12 15:02 UTCEPSS rescore
  5. 2026-09-12 06:00 UTCVendor advisory
  6. 2026-09-11 19:10 UTCEG score recompute
  7. 2026-09-11 19:10 UTCVendor advisory
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 08:04 UTCVendor advisory
  10. 2026-09-10 21:15 UTCVendor advisory
  11. 2026-09-10 10:26 UTCEG score recompute
  12. 2026-09-10 10:26 UTCVendor advisory
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 23:37 UTCVendor advisory
  15. 2026-09-09 10:12 UTCVendor advisory
  16. 2026-09-08 23:23 UTCEG score recompute
  17. 2026-09-08 23:23 UTCVendor advisory
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 12:21 UTCVendor advisory
  20. 2026-09-08 01:28 UTCEG score recompute
  21. 2026-09-08 01:28 UTCVendor advisory
  22. 2026-09-08 01:15 UTCEG score recompute
  23. 2026-09-08 01:15 UTCVendor advisory
  24. 2026-09-07 19:08 UTCEG score recompute
  25. 2026-09-07 19:08 UTCVendor advisory
  26. 2026-09-07 08:17 UTCVendor advisory
  27. 2026-09-06 21:28 UTCEG score recompute
  28. 2026-09-06 21:28 UTCVendor advisory
  29. 2026-09-06 13:48 UTCEPSS rescore
  30. 2026-09-06 10:38 UTCVendor advisory
  31. 2026-09-05 23:49 UTCEG score recompute
  32. 2026-09-05 23:49 UTCVendor advisory
  33. 2026-09-05 13:00 UTCVendor advisory
  34. 2026-09-05 02:10 UTCVendor advisory
  35. 2026-09-04 15:21 UTCEG score recompute
  36. 2026-09-04 15:21 UTCVendor advisory
  37. 2026-09-04 05:07 UTCEPSS rescore
  38. 2026-09-04 04:31 UTCVendor advisory
  39. 2026-09-03 17:40 UTCVendor advisory
  40. 2026-09-02 20:00 UTCEG score recompute
  41. 2026-09-02 14:12 UTCEPSS rescore
  42. 2026-09-01 16:25 UTCEG score recompute
  43. 2026-09-01 16:09 UTCEG score recompute
  44. 2026-09-01 15:39 UTCEG score recompute
  45. 2026-09-01 14:43 UTCEG score recompute
  46. 2026-09-01 14:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73812?
CVE-2026-73812 is a high vulnerability published on September 1, 2026. httpd function checkheader/3 rejects duplicate Content-Length (per CVE-2026-23941) but never checks for the TE+CL co-presence that RFC 9112 §6.3 identifies as a probable smuggling attempt. handlebody/3 frames by chunked and silently discards Content-Length. A CL-preferring front-end paired with…
When was CVE-2026-73812 disclosed?
CVE-2026-73812 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73812 actively exploited?
CVE-2026-73812 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 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73812?
CVE-2026-73812 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-73812?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73812, 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-73812

Explore →

Is Your Infrastructure Affected by CVE-2026-73812?

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

Start Free Scan →Browse All CVEs