CVE-2026-40211

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An attacker can send crafted DNS over HTTP/3 queries, triggering an exception that prevents some buffer from being freed right away. The buffer will be freed at the end of the QUIC connection, but on some setups it might be possible to open enough concurrent DoH3 streams to trigger an out-of-memory condition, resulting in a denial of service.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 27, 2026
No patch confirmed yet.
generic

PowerDNS Security Advisory 2026-09 for DNSdist: Multiple issues - dnsdist documentation

https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2026-09.html

Vendor Advisories for CVE-2026-40211(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 58× 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.

  1. 2026-07-28 21:21 UTCEG score recompute
  2. 2026-07-28 21:20 UTCGHSA enrichment
  3. 2026-07-27 17:24 UTCEG score recompute
  4. 2026-07-27 17:24 UTCGHSA enrichment
  5. 2026-07-27 14:13 UTCEPSS rescore
  6. 2026-07-26 15:08 UTCEG score recompute
  7. 2026-07-26 15:08 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-24 14:17 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:11 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:24 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 02:29 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-16 17:03 UTCEPSS rescore
  23. 2026-07-16 14:16 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 41 more
  1. 2026-07-15 12:47 UTCGHSA enrichment
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 11:40 UTCGHSA enrichment
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 10:32 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 09:26 UTCGHSA enrichment
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:21 UTCGHSA enrichment
  12. 2026-07-10 07:16 UTCGHSA enrichment
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 06:12 UTCGHSA enrichment
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 05:04 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 03:58 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 02:39 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-05 01:34 UTCGHSA enrichment
  26. 2026-07-04 06:31 UTCEPSS rescore
  27. 2026-07-04 00:28 UTCGHSA enrichment
  28. 2026-07-02 23:24 UTCGHSA enrichment
  29. 2026-07-01 22:20 UTCGHSA enrichment
  30. 2026-07-01 15:06 UTCEPSS rescore
  31. 2026-06-30 23:22 UTCEPSS rescore
  32. 2026-06-30 21:13 UTCGHSA enrichment
  33. 2026-06-29 20:07 UTCGHSA enrichment
  34. 2026-06-28 19:03 UTCGHSA enrichment
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-27 17:59 UTCGHSA enrichment
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-26 16:54 UTCGHSA enrichment
  40. 2026-06-25 15:50 UTCEG score recompute
  41. 2026-06-25 15:50 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-40211?
CVE-2026-40211 is a medium vulnerability published on June 25, 2026. An attacker can send crafted DNS over HTTP/3 queries, triggering an exception that prevents some buffer from being freed right away. The buffer will be freed at the end of the QUIC connection, but on some setups it might be possible to open enough concurrent DoH3 streams to trigger an out-of-memory…
When was CVE-2026-40211 disclosed?
CVE-2026-40211 was first published in the National Vulnerability Database on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40211 actively exploited?
CVE-2026-40211 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 78.1% of all scored CVEs.
What is the CVSS score of CVE-2026-40211?
CVE-2026-40211 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-40211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40211, 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-40211

Explore →

Is Your Infrastructure Affected by CVE-2026-40211?

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

Start Free Scan →Browse All CVEs