CVE-2026-42960

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: None knownExposed: 0

A fix is available — apply it.

NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the authority section. Promiscuous RRSets that complement DNS replies in the authority section can be used to trick Unbound to cache such records. If an adversary is able to attach such records in a reply (i.e., spoofed packet, fragmentation attack) he would be able to poison Unbound's cache. A malicious actor can exploit the possible poisonous effect by injecting RRSets other than NS that are also accompanied by address records in a reply, for example MX. This could be achieved by trying to spoof a reply packet or fragmentation attacks. Unbound would then accept the relative address records in the additional section and cache them if the authority RRSet has enough trust at this point, i.e., in-zone data for the delegation point. Unbound 1.25.1 contains a patch with a fix that disregards address records from the additional section if they are not explicitly relevant only to authority NS records, mitigating the possible poison effect. This is a complement fix to CVE-2025-11411.

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

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Sep 18, 2026
No patch confirmed yet.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuunbound-host (1.9.4-2ubuntu1.11+esm1) @ focal2026-08-23ubuntu
ubuntuunbound-host (1.24.2-1ubuntu2.1) @ resolute2026-08-23ubuntu
redhatunbound-main-1.25.1-1.hum12026-05-23redhat

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)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
unbound1.25.1-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
unbound1.17.1-2 ... 1.26.0-2 (25 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2, 1.22.0-2+deb13u1, 1.22.0-2+deb13u21.22.0-2+deb13u3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.25.0-1 (8 versions)1.25.1-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 6× in last 7d / 36× 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 507 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-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 17:23 UTCOSV refresh
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-23 21:10 UTCVendor advisory
  24. 2026-08-23 21:10 UTCGHSA enrichment
  25. 2026-08-23 16:57 UTCEG score recompute
Show 75 more
  1. 2026-08-23 16:57 UTCVendor advisory
  2. 2026-08-23 16:57 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 22:55 UTCEG score recompute
  6. 2026-08-21 22:55 UTCVendor advisory
  7. 2026-08-21 22:55 UTCGHSA enrichment
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 18:56 UTCEG score recompute
  10. 2026-08-20 18:56 UTCVendor advisory
  11. 2026-08-20 18:56 UTCGHSA enrichment
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:57 UTCEG score recompute
  15. 2026-08-17 13:57 UTCVendor advisory
  16. 2026-08-17 13:57 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 09:54 UTCVendor advisory
  19. 2026-08-17 09:54 UTCGHSA enrichment
  20. 2026-08-16 16:55 UTCEG score recompute
  21. 2026-08-16 16:55 UTCVendor advisory
  22. 2026-08-16 16:55 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 11:40 UTCVendor advisory
  25. 2026-08-16 11:40 UTCGHSA enrichment
  26. 2026-08-16 07:36 UTCVendor advisory
  27. 2026-08-16 07:36 UTCGHSA enrichment
  28. 2026-08-16 03:30 UTCEG score recompute
  29. 2026-08-16 03:30 UTCVendor advisory
  30. 2026-08-16 03:30 UTCGHSA enrichment
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 02:23 UTCEG score recompute
  33. 2026-08-15 02:23 UTCVendor advisory
  34. 2026-08-15 02:23 UTCGHSA enrichment
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 22:19 UTCVendor advisory
  37. 2026-08-14 22:19 UTCGHSA enrichment
  38. 2026-08-14 18:16 UTCVendor advisory
  39. 2026-08-14 18:16 UTCGHSA enrichment
  40. 2026-08-14 14:12 UTCVendor advisory
  41. 2026-08-14 14:12 UTCGHSA enrichment
  42. 2026-08-14 10:09 UTCVendor advisory
  43. 2026-08-14 10:09 UTCGHSA enrichment
  44. 2026-08-14 06:05 UTCVendor advisory
  45. 2026-08-14 06:05 UTCGHSA enrichment
  46. 2026-08-14 02:02 UTCEG score recompute
  47. 2026-08-14 02:02 UTCVendor advisory
  48. 2026-08-14 02:02 UTCGHSA enrichment
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-13 08:19 UTCVendor advisory
  51. 2026-08-13 08:19 UTCGHSA enrichment
  52. 2026-08-13 04:14 UTCVendor advisory
  53. 2026-08-13 04:14 UTCGHSA enrichment
  54. 2026-08-13 00:10 UTCVendor advisory
  55. 2026-08-13 00:10 UTCGHSA enrichment
  56. 2026-08-12 20:07 UTCVendor advisory
  57. 2026-08-12 20:07 UTCGHSA enrichment
  58. 2026-08-12 16:01 UTCEG score recompute
  59. 2026-08-12 16:01 UTCVendor advisory
  60. 2026-08-12 16:01 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 11:57 UTCVendor advisory
  63. 2026-08-12 11:57 UTCGHSA enrichment
  64. 2026-08-11 22:54 UTCVendor advisory
  65. 2026-08-11 22:54 UTCGHSA enrichment
  66. 2026-08-11 18:46 UTCVendor advisory
  67. 2026-08-11 18:46 UTCGHSA enrichment
  68. 2026-08-11 13:52 UTCEG score recompute
  69. 2026-08-11 13:52 UTCVendor advisory
  70. 2026-08-11 13:52 UTCGHSA enrichment
  71. 2026-08-11 13:43 UTCEPSS rescore
  72. 2026-08-11 08:43 UTCVendor advisory
  73. 2026-08-11 08:42 UTCGHSA enrichment
  74. 2026-08-11 04:39 UTCVendor advisory
  75. 2026-08-11 04:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42960?
CVE-2026-42960 is a critical vulnerability published on May 20, 2026. NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the authority section. Promiscuous RRSets that complement DNS replies in the authority section can be used to trick Unbound to cache such records. If an adversary is able to attach such…
When was CVE-2026-42960 disclosed?
CVE-2026-42960 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42960 actively exploited?
CVE-2026-42960 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 83.4% of all scored CVEs.
What is the CVSS score of CVE-2026-42960?
CVE-2026-42960 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-42960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42960, 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-42960

Explore →

Is Your Infrastructure Affected by CVE-2026-42960?

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