CVE-2026-73276

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 74% 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

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

Gracefulness code ignored cases that should be rejected, resulting in possible HTTP Request Smuggling opportunities.

This issue affects OTP from OTP 22.2 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 7.1.2 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

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
26%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (6)

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

commit c285240c6e4b (erlang/otp)

Fix landed in erlang/otp commit c285240c6e4b — awaiting tagged release

https://github.com/erlang/otp/commit/c285240c6e4b93960c5dc4f17ba04e6fdfb27a0f
github_commit

commit 6cd995e34d3b (erlang/otp)

Fix landed in erlang/otp commit 6cd995e34d3b — awaiting tagged release

https://github.com/erlang/otp/commit/6cd995e34d3bb3d36dd278dded2d62c25e71820c
github_commit

commit 60add5a19e21 (erlang/otp)

Fix landed in erlang/otp commit 60add5a19e21 — awaiting tagged release

https://github.com/erlang/otp/commit/60add5a19e2154560fdff3fe92dba14a68bbd683
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-73276
github Patch Available

HTTP Request Smuggling via Whitespace-Before-Colon Header Dropping in httpd · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-6v7q-jwgh-cx8p

Vendor Advisories for CVE-2026-73276(1)

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

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

Frequently asked(5)

What is CVE-2026-73276?
CVE-2026-73276 is a high vulnerability published on September 1, 2026. Gracefulness code ignored cases that should be rejected, resulting in possible HTTP Request Smuggling opportunities. This issue affects OTP from OTP 22.2 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 7.1.2 before 9.3.2.7,…
When was CVE-2026-73276 disclosed?
CVE-2026-73276 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-73276 actively exploited?
CVE-2026-73276 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 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-73276?
CVE-2026-73276 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-73276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73276, 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-73276

Explore →

Is Your Infrastructure Affected by CVE-2026-73276?

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