CVE-2026-63075

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: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection.

Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service.

The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself.

FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (5)

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

commit c902e5f16d6a (openssl/openssl)

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

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

commit 7c98d7973854 (openssl/openssl)

Fix landed in openssl/openssl commit 7c98d7973854 — awaiting tagged release

https://github.com/openssl/openssl/commit/7c98d79738549df92868e7dd9be4bbf061eed709
github_commit

commit bf84721c2548 (openssl/openssl)

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

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

commit 7308946576b1 (openssl/openssl)

Fix landed in openssl/openssl commit 7308946576b1 — awaiting tagged release

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

Vendor Advisories for CVE-2026-63075(5)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-09-19ubuntu
redhatopenssl-1:3.5.8-1.el10_22026-09-14redhat
redhatopenssl-1:3.5.8-1.el9_82026-09-14redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl-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

(5 across 5 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: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

(2)

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 42× in last 7d / 155× 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 155 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63075?
CVE-2026-63075 is a high vulnerability published on August 25, 2026. Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC…
When was CVE-2026-63075 disclosed?
CVE-2026-63075 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-63075 actively exploited?
CVE-2026-63075 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 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63075?
CVE-2026-63075 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-63075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63075, 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-63075

Explore →

Is Your Infrastructure Affected by CVE-2026-63075?

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

Start Free Scan →Browse All CVEs