CVE-2026-40898

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
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: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.59.1, an attacker can cause excessive memory allocation in quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large trailer field section with many unique field names and/or large values. The implementation builds an http.Header for the corresponding http.Request or http.Response, while only enforcing limits on the size of the QPACK-compressed HEADERS frame, not on the decoded field section. This can lead to memory exhaustion. This is very similar to CVE-2025-64702. The difference is that this issue uses HTTP trailers, rather than HTTP headers, as the attack vector. A misbehaving or malicious peer can cause a denial-of-service (DoS) attack against quic-go's HTTP/3 servers or clients by triggering excessive memory allocation, potentially leading to crashes or resource exhaustion. This affects both servers and clients due to symmetric header construction. Version 0.59.1 enforces RFC 9114 decoded field section size limits for trailers as well. It incrementally decodes QPACK entries and checks the field section size after each entry, aborting the stream if an entry causes the limit to be exceeded.

CVSS v3
7.5
EG Score
7.5(medium)
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
34%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github_release, github.
github Patch Available

HTTP/3 QPACK Trailer Expansion Memory Exhaustion · Advisory · quic-go/quic-go · GitHub

https://github.com/quic-go/quic-go/security/advisories/GHSA-vvgj-x9jq-8cj9
github_release Patch Available

v0.59.1

Patch available: quic-go/quic-go v0.59.1

https://github.com/quic-go/quic-go/releases/tag/v0.59.1

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdevspaces/traefik-rhel9:17877567992026-09-01redhat
redhatcontainer-native-virtualization/kubevirt-apiserver-proxy-rhel9:17861257622026-08-11redhat
redhatansible-automation-platform-27/receptor-rhel9:17853894822026-08-04redhat
redhatreceptor-0:1.6.7-1.el9ap2026-08-04redhat
redhatansible-automation-platform-26/receptor-rhel9:17856321172026-08-04redhat
redhatcaddy-main-2.11.4-0.2.hum12026-07-15redhat
redhatrust-main-1.97.0-1.1.hum12026-07-11redhat
redhatcaddy-main-2.11.4-0.1.hum12026-06-11redhat
redhattrivy-main-0.69.3-1.2.hum12026-05-09redhat

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)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-github-lucas-clemente-quic-go0.19.3-1 ... 0.59.0-2~bpo13+1 (30 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-lucas-clemente-quic-go0.29.0-1 ... 0.59.0-2~bpo13+1 (23 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-lucas-clemente-quic-go0.50.1-2 ... 0.59.0-2~bpo13+1 (9 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-lucas-clemente-quic-go0.50.1-2 ... 0.59.0-2~bpo13+1 (9 versions)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/quic-go/quic-go0.59.1

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 10× in last 7d / 39× 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 190 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40898?
CVE-2026-40898 is a high vulnerability published on June 3, 2026. quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.59.1, an attacker can cause excessive memory allocation in quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large trailer field section with many unique field…
When was CVE-2026-40898 disclosed?
CVE-2026-40898 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40898 actively exploited?
CVE-2026-40898 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 66.4% of all scored CVEs.
What is the CVSS score of CVE-2026-40898?
CVE-2026-40898 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-40898?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40898, 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-40898

Explore →

Is Your Infrastructure Affected by CVE-2026-40898?

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