CVE-2026-42960

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-31083 (ENISA EUVD) · GHSA-x7f7-rggg-4jvv (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 10.0Exploit: None knownExposed services: Not assessed

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.0CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Oct 30, 2026
Patch available.
Web page
https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-42960.txt

Vendor Advisories for CVE-2026-42960(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuunbound-host (1.5.8-1ubuntu1.1+esm3) @ xenial2026-11-02ubuntu
ubuntuunbound-host (1.19.2-1ubuntu3.8) @ noble2026-11-02ubuntu
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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • every version up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • every version up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • every version up to 1.25.1-r0: fixed in 1.25.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.17.1-2 ... 1.26.1-1 (26 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2, 1.22.0-2+deb13u1, 1.22.0-2+deb13u2
  • every version up to 1.22.0-2+deb13u3: fixed in 1.22.0-2+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2 ... 1.25.0-1 (8 versions)
  • every version up to 1.25.1-1: fixed in 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 28× in last 7d / 97× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 611 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 511 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42960?
CVE-2026-42960 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-42960 was made public on May 20, 2026: that is the date its CVE record's CNA, NLnet Labs, gives for when the vulnerability was made public. The CVE record itself was published on May 20, 2026. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-42960 actively exploited?
CVE-2026-42960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-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?
A fix for CVE-2026-42960 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42960 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs