CVE-2026-55953

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

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

7.4EG
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.2%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Erlang/OTP ssl TLS 1.2 (and earlier) and DTLS client does not verify that the cipher suite selected by the server in ServerHello was among the suites offered by the client in ClientHello. The client-side tls_handshake:hello/5 handler validates the negotiated protocol version and the downgrade sentinel but hands the server-chosen suite directly to ssl_handshake:handle_server_hello_extensions/9, which installs it without a membership check. The TLS 1.3 client path performs this check (per RFC 8446), so it is not affected.

An on-path attacker between the client and the intended server can respond with a ServerHello selecting an anonymous key exchange suite such as TLS_DH_anon_* or TLS_ECDH_anon_* that the client never offered. Anonymous suites do not require the server to present a certificate, so the entire verify_peer and cacerts configuration is bypassed: the attacker completes the handshake with its own ephemeral parameters, no certificate is validated, no hostname is checked, and ssl:connect returns {ok, Socket}. All subsequent application traffic is readable and modifiable by the attacker.

This issue affects OTP from OTP 17.0 before OTP 27.3.4.15, from OTP 28.0 before OTP 28.5.0.4, and from OTP 29.0 before OTP 29.0.4, corresponding to ssl from 5.3.4 before 11.2.12.11, from 11.3 before 11.6.0.4, and from 11.7 before 11.7.4. Whether OTP before OTP 17.0, corresponding to ssl before 5.3.4, is affected is unknown.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
14th
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

July 27, 2026

Last Modified

October 24, 2026

Advisory Details (7)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit, github.
Web page

Versions — Erlang System Documentation v29.0.4

https://www.erlang.org/doc/system/versions.html#order-of-versions
Web page

OSV - Open Source Vulnerabilities

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

(D)TLS-1.2 Server Cert Verification Bypass via Unoffered Anonymous Cipher Suite · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-c6cw-pr89-w882
GitHub commit

commit e6ff938116b2 (erlang/otp)

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

https://github.com/erlang/otp/commit/e6ff938116b2872bccc478af7fefb56627285b77
GitHub commit

commit 0a82596d425a (erlang/otp)

Fix landed in erlang/otp commit 0a82596d425a — awaiting tagged release

https://github.com/erlang/otp/commit/0a82596d425abe43dc2e0b3d74aa1557ef74051c
GitHub commit

commit 064e23641461 (erlang/otp)

Fix landed in erlang/otp commit 064e23641461 — awaiting tagged release

https://github.com/erlang/otp/commit/064e236414614f9085cbbbd6eacf0e43c02d1b4b
Web page

TLS 1.2 and DTLS client accepts unoffered anonymous cipher suite, bypassing server authentication | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-55953.html

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuerlang-xmerl (1:24.2.1+dfsg-1ubuntu0.7) @ jammy2026-10-27ubuntu
redhaterlang27-main-27.3.4.15-0.1.hum12026-07-28redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
  • every version on: no fix on record
—
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
  • every version up to 1:27.3.4.1+dfsg-1+deb13u3: fixed in 1:27.3.4.1+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (35 versions)
  • every version up to 1:29.0.4+dfsg-1: fixed in 1:29.0.4+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 / 46× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 306 refreshes 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 206 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-55953?
CVE-2026-55953 is a high-severity vulnerability; its CVE record was published on July 27, 2026. The Erlang/OTP ssl TLS 1.2 (and earlier) and DTLS client does not verify that the cipher suite selected by the server in ServerHello was among the suites offered by the client in ClientHello. The client-side tls_handshake:hello/5 handler validates the negotiated protocol version and the downgrade…
When was the CVE record for CVE-2026-55953 published?
The CVE record for CVE-2026-55953 was published on July 27, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-55953 actively exploited?
CVE-2026-55953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55953?
CVE-2026-55953 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-55953?
A fix for CVE-2026-55953 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55953 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-55953

Explore →

Is Your Infrastructure Affected by CVE-2026-55953?

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