CVE-2026-52684

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-23. a secondary CVSS source baseline 3.7; sources differ by 0.0.

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

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

If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the child records are used immediately if not expired and thus valid, or the records are expired, and in that case not used. So this case can only happen if almost expired records are used to refresh the authoritative NS records.

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

Published

July 23, 2026

Last Modified

July 23, 2026

References (1)

Vendor Advisories for CVE-2026-52684(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pdns-recursor4.4.2-3 ... 5.4.4-1 (65 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pdns-recursor4.8.4-1 ... 5.4.4-1 (50 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pdns-recursor5.2.11-0+deb13u1 ... 5.4.4-1 (26 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pdns-recursor5.2.4-2 ... 5.4.4-1 (19 versions)——

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 21:09 UTCEG score recompute
  4. 2026-08-27 21:09 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-24 14:23 UTCEG score recompute
  9. 2026-08-24 14:22 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 07:55 UTCEG score recompute
  13. 2026-08-21 07:55 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-18 01:28 UTCEG score recompute
  18. 2026-08-18 01:28 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 18:03 UTCEG score recompute
  24. 2026-08-14 18:03 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 31 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 11:36 UTCEG score recompute
  3. 2026-08-11 11:36 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-08 05:09 UTCEG score recompute
  8. 2026-08-08 05:09 UTCGHSA enrichment
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 22:42 UTCEG score recompute
  12. 2026-08-04 22:42 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 16:15 UTCEG score recompute
  18. 2026-08-01 16:15 UTCGHSA enrichment
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 09:47 UTCEG score recompute
  23. 2026-07-29 09:47 UTCGHSA enrichment
  24. 2026-07-28 15:37 UTCEPSS rescore
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 03:20 UTCEG score recompute
  27. 2026-07-26 03:19 UTCGHSA enrichment
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 08:35 UTCEG score recompute
  31. 2026-07-23 08:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-52684?
CVE-2026-52684 is a low vulnerability published on July 23, 2026. If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the child records are used immediately if not expired and thus valid, or the records are expired, and in that case not used.…
When was CVE-2026-52684 disclosed?
CVE-2026-52684 was first published in the National Vulnerability Database 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-52684 actively exploited?
CVE-2026-52684 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 96.1% of all scored CVEs.
What is the CVSS score of CVE-2026-52684?
CVE-2026-52684 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-52684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52684, 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-52684

Explore →

Is Your Infrastructure Affected by CVE-2026-52684?

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

Start Free Scan →Browse All CVEs