CVE-2026-10723

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 6.8; sources differ by 0.0.

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

A fix is available — apply it.

BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

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

Published

July 22, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic

CVE-2026-10723: Incorrect acceptance of NSEC3 records

https://kb.isc.org/docs/cve-2026-10723
generic

Index of /isc/bind9/9.21.24

https://downloads.isc.org/isc/bind9/9.21.24
generic

Index of /isc/bind9/9.20.26

https://downloads.isc.org/isc/bind9/9.20.26

Vendor Advisories for CVE-2026-10723(13)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9-utils (1:9.20.24-1ubuntu0.2) @ resolute2026-09-14ubuntu
redhatrhcos-416.94.202609011112-02026-09-10redhat
redhatrhcos-4.22.9.8.202608251819-02026-09-01redhat
redhatbind-32:9.11.4-26.P2.el7_9.212026-08-26redhat
redhatbind-32:9.16.23-18.el9_4.122026-08-19redhat
redhatbind-32:9.16.23-31.el9_6.42026-08-17redhat
redhatbind9.18-32:9.18.29-14.el9_8.82026-08-17redhat
redhatbind-32:9.18.33-15.el10_2.102026-08-17redhat
redhatbind9.16-32:9.16.23-0.22.el8_10.122026-08-13redhat
redhatbind-32:9.11.36-16.el8_10.142026-08-13redhat
redhatbind-32:9.16.23-40.el9_8.82026-08-13redhat
redhatbind-main-9.20.26-0.1.hum12026-08-12redhat

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 rangeFixed inDependents
bind—9.20.26-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.26-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.26-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u5 (17 versions)1:9.16.50-1~deb11u6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind91:9.18.12-1 ... 1:9.18.49-1~deb12u1 (16 versions)1:9.18.49-1~deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.26-1~deb13u1~bpo12+1 (21 versions)1:9.20.26-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.26-1~deb13u1~bpo12+1 (22 versions)1:9.20.26-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 20× in last 7d / 86× 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 165 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-10723?
CVE-2026-10723 is a medium vulnerability published on July 22, 2026. BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through…
When was CVE-2026-10723 disclosed?
CVE-2026-10723 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10723 actively exploited?
CVE-2026-10723 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 80.4% of all scored CVEs.
What is the CVSS score of CVE-2026-10723?
CVE-2026-10723 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-10723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10723, 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-10723

Explore →

Is Your Infrastructure Affected by CVE-2026-10723?

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

Start Free Scan →Browse All CVEs