CVE-2026-34183

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. 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 — 4 sources updated 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: Remote peer may exhaust heap memory of the QUIC server or client by flooding it with packets containing PATH_CHALLENGE frames.

Impact summary: A malicious remote peer can cause an unbounded memory allocation which can lead to an abnormal termination of the application acting as a QUIC client or server and a Denial of Service.

A remote peer may exhaust heap memory by flooding the local QUIC stack with PATH_CHALLENGE frames. The local QUIC stack allocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives. The allocated PATH_RESPONSE frame gets freed only when the remote peer acknowledges reception of the PATH_RESPONSE frame which will not be done by a malicious peer.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue. The QUIC stack is outside of OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
62%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (5)

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

commit fbaa83859c01 (openssl/openssl)

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

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

commit d2e9efbe4900 (openssl/openssl)

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

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

commit 7d06955ebe0e (openssl/openssl)

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

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

commit 5b306efb0b37 (openssl/openssl)

Fix landed in openssl/openssl commit 5b306efb0b37 — awaiting tagged release

https://github.com/openssl/openssl/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3.4) @ questing2026-08-21ubuntu
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17835391562026-07-15redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatopenssl-1:3.5.5-4.el9_82026-06-11redhat
redhatopenssl-1:3.5.5-4.el10_22026-06-11redhat

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
openssl3.5.7-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.7-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.7-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.6-1~deb13u1 (11 versions)3.5.6-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.2-1 (19 versions)3.6.3-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 31× in last 7d / 145× 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 325 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-34183?
CVE-2026-34183 is a high vulnerability published on June 9, 2026. Issue summary: Remote peer may exhaust heap memory of the QUIC server or client by flooding it with packets containing PATH_CHALLENGE frames. Impact summary: A malicious remote peer can cause an unbounded memory allocation which can lead to an abnormal termination of the application acting as a…
When was CVE-2026-34183 disclosed?
CVE-2026-34183 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34183 actively exploited?
CVE-2026-34183 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 38.4% of all scored CVEs.
What is the CVSS score of CVE-2026-34183?
CVE-2026-34183 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-34183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34183, 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-34183

Explore →

Is Your Infrastructure Affected by CVE-2026-34183?

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