CVE-2026-42923

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 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

A fix is available — apply it.

NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability in the DNSSEC validator where the code path to consult the negative cache for DS records does not take into account the limit on NSEC3 hash calculations introduced in 1.19.1. This leads to degradation of service during the attack. An adversary that controls a DNSSEC signed zone can exploit this by signing NSEC3 records with acceptably high iterations for child delegations and querying a vulnerable Unbound. Unbound will keep performing the allowed hash calculations on the NSEC3 records and will not limit the work by the mitigation introduced in 1.19.1. As a side effect, a global lock for the negative cache will be held for the duration of the hashing, blocking other threads that need to consult the negative cache. Coordinated attacks could raise the vulnerability to denial of service. Unbound 1.25.1 contains a patch with a fix to bound the vulnerable code path with the existing limit for NSEC3 hash calculations.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated May 20, 2026
No patch confirmed yet.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuunbound-host (1.13.1-1ubuntu5.15) @ jammy2026-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.25.2-1 (23 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

(1)

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 14× in last 7d / 75× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42923?
CVE-2026-42923 is a medium vulnerability published on May 20, 2026. NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability in the DNSSEC validator where the code path to consult the negative cache for DS records does not take into account the limit on NSEC3 hash calculations introduced in 1.19.1. This leads to degradation of service during the…
When was CVE-2026-42923 disclosed?
CVE-2026-42923 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-42923 actively exploited?
CVE-2026-42923 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 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-42923?
CVE-2026-42923 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-42923?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42923, 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-42923

Explore →

Is Your Infrastructure Affected by CVE-2026-42923?

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