CVE-2026-73276

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-69233 (ENISA EUVD)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 7.1.2 before 9.3.2.7, 9.6.2.3, and 9.7.2.

CVSS
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 1, 2026

Last Modified

November 11, 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
Web page

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-73276
GitHub advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuerlang-xmerl (1:18.3-dfsg-1ubuntu3.1+esm3) @ xenial2026-10-27ubuntu

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 rangeFix by version rangeDependents
erlang1:25.2.3+dfsg-1 ... 1:29.1.1+dfsg-1 (80 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u2, 1:27.3.4.1+dfsg-1+deb13u3
  • every version up to 1:27.3.4.1+dfsg-1+deb13u4: fixed in 1:27.3.4.1+dfsg-1+deb13u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (36 versions)
  • every version up to 1:29.0.6+dfsg-1: fixed in 1:29.0.6+dfsg-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 188 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-11-11 14:27 UTCEchelonGraph re-scored
  4. 2026-11-11 14:27 UTCVendor advisory
  5. 2026-11-11 13:49 UTCEchelonGraph re-scored
  6. 2026-11-11 13:49 UTCVendor advisory
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-11-10 11:17 UTCEchelonGraph re-scored
  9. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-11-03 15:58 UTCEchelonGraph re-scored
  17. 2026-11-03 15:58 UTCVendor advisory
  18. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-27 19:25 UTCEchelonGraph re-scored
  25. 2026-10-27 19:25 UTCVendor advisory
Show 75 more
  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-25 14:06 UTCEchelonGraph re-scored
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-20 08:32 UTCEchelonGraph re-scored
  11. 2026-10-20 08:32 UTCVendor advisory
  12. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-18 03:15 UTCEchelonGraph re-scored
  15. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-13 07:56 UTCEchelonGraph re-scored
  21. 2026-10-13 07:56 UTCVendor advisory
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-12 15:41 UTCEchelonGraph re-scored
  24. 2026-10-11 19:26 UTCEchelonGraph re-scored
  25. 2026-10-11 16:42 UTCEchelonGraph re-scored
  26. 2026-10-11 14:02 UTCEchelonGraph re-scored
  27. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  29. 2026-10-10 12:40 UTCVendor advisory
  30. 2026-10-10 00:14 UTCEchelonGraph re-scored
  31. 2026-10-10 00:14 UTCVendor advisory
  32. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  33. 2026-10-09 02:06 UTCEchelonGraph re-scored
  34. 2026-10-09 02:06 UTCVendor advisory
  35. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  36. 2026-10-08 00:12 UTCEchelonGraph re-scored
  37. 2026-10-08 00:12 UTCVendor advisory
  38. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  39. 2026-10-07 08:10 UTCVendor advisory
  40. 2026-10-06 19:45 UTCEchelonGraph re-scored
  41. 2026-10-06 19:45 UTCVendor advisory
  42. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  43. 2026-10-06 07:21 UTCEchelonGraph re-scored
  44. 2026-10-06 07:21 UTCVendor advisory
  45. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  46. 2026-10-05 16:45 UTCVendor advisory
  47. 2026-10-05 03:29 UTCEchelonGraph re-scored
  48. 2026-10-05 03:29 UTCVendor advisory
  49. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  50. 2026-10-04 14:34 UTCVendor advisory
  51. 2026-10-04 01:51 UTCEchelonGraph re-scored
  52. 2026-10-04 01:51 UTCVendor advisory
  53. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-10-03 13:15 UTCVendor advisory
  55. 2026-10-02 21:31 UTCEchelonGraph re-scored
  56. 2026-10-02 21:31 UTCVendor advisory
  57. 2026-10-02 09:06 UTCVendor advisory
  58. 2026-10-01 20:36 UTCEchelonGraph re-scored
  59. 2026-10-01 20:36 UTCVendor advisory
  60. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-10-01 07:58 UTCVendor advisory
  62. 2026-09-30 19:34 UTCEchelonGraph re-scored
  63. 2026-09-30 19:34 UTCVendor advisory
  64. 2026-09-30 03:21 UTCEchelonGraph re-scored
  65. 2026-09-30 03:21 UTCVendor advisory
  66. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  67. 2026-09-29 09:28 UTCEchelonGraph re-scored
  68. 2026-09-29 09:28 UTCVendor advisory
  69. 2026-09-28 21:02 UTCEchelonGraph re-scored
  70. 2026-09-28 21:02 UTCVendor advisory
  71. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  72. 2026-09-28 08:37 UTCVendor advisory
  73. 2026-09-27 20:13 UTCEchelonGraph re-scored
  74. 2026-09-27 20:13 UTCVendor advisory
  75. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Frequently asked(5)

What is CVE-2026-73276?
CVE-2026-73276 is a high-severity vulnerability; its CVE record was 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, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 7.1.2 before 9.3.2.7, 9.6.2.3, and 9.7.2.
When was the CVE record for CVE-2026-73276 published?
The CVE record for CVE-2026-73276 was published on September 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-73276 actively exploited?
CVE-2026-73276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73276?
CVE-2026-73276 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73276?
A fix for CVE-2026-73276 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73276 are linked in the Vendor Advisories panel on this page.

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.