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 — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
40.5%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 15, 2026

Advisory Details (5)

Auto-updated Jun 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://openssl-library.org/news/secadv/20260609.txt
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

Vendor Advisories for CVE-2026-34183(8)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (3.0.13-0ubuntu3.11) @ noble2026-07-16ubuntu
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.

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 11× in last 7d / 116× 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 181 total refreshes for this CVE.

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

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 June 15, 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 40.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs