CVE-2026-54874

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.

Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service.

CWE: CWE-405: Asymmetric Resource Consumption (Amplification)

Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up.

Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network.

An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity.

FIPS impact: no

No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.

Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr

This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell.

-- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (6)

Auto-updated Aug 25, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit a0c8ec557d9c (openssl/openssl)

Fix landed in openssl/openssl commit a0c8ec557d9c — awaiting tagged release

https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
github_commit

commit 7110cb2f7580 (openssl/openssl)

Fix landed in openssl/openssl commit 7110cb2f7580 — awaiting tagged release

https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40
github_commit

commit 4808b5d64176 (openssl/openssl)

Fix landed in openssl/openssl commit 4808b5d64176 — awaiting tagged release

https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23
github_commit

commit f52ffc11b907 (openssl/openssl)

Fix landed in openssl/openssl commit f52ffc11b907 — awaiting tagged release

https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c
github_commit

commit cc0c6710917c (openssl/openssl)

Fix landed in openssl/openssl commit cc0c6710917c — awaiting tagged release

https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107
generic
https://openssl-library.org/news/secadv/20260825.txt

Vendor Advisories for CVE-2026-54874(5)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-09-19ubuntu
ubuntuopenssl1.0 (1.0.2n-1ubuntu5.13+esm6) @ bionic2026-09-19ubuntu
redhatopenssl-1:3.5.8-1.el10_22026-09-14redhat
redhatopenssl-1:3.5.8-1.el9_82026-09-14redhat
redhatopenssl-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat

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

(6 across 6 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.8-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 4.0.2-1 (86 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)3.5.7-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 4.0.2-1 (28 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 41× in last 7d / 148× 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.

Showing the most recent 100 of 148 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54874?
CVE-2026-54874 is a high vulnerability published on August 25, 2026. Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large…
When was CVE-2026-54874 disclosed?
CVE-2026-54874 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54874 actively exploited?
CVE-2026-54874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.6% of all scored CVEs.
What is the CVSS score of CVE-2026-54874?
CVE-2026-54874 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-54874?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54874, 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-54874

Explore →

Is Your Infrastructure Affected by CVE-2026-54874?

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

Start Free Scan →Browse All CVEs