CVE-2026-52684
LOW
Published Jul 23, 2026
Modified Jul 23, 2026
Description
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.
Is your site exposed to CVE-2026-52684?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
3.7
LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS — Exploit Prediction
0.0014
Probability of exploitation
0.04%
Percentile rank
EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.
References
Other References
Frequently Asked Questions
What is CVE-2026-52684? +
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. It has a CVSS v3.1 base score of 3.7 (LOW).
How severe is CVE-2026-52684? +
CVE-2026-52684 has a CVSS v3.1 score of 3.7 out of 10, rated LOW. This is a low-severity vulnerability with limited impact. The EPSS score is 0.0014, placing it in the 0th percentile for exploitation probability.
How do I check if I'm vulnerable to CVE-2026-52684? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.
