# CVE-2026-10723: Incorrect acceptance of NSEC3 records

> Attackers can forge authenticated NXDOMAIN responses by exploiting incorrect NSEC3 record validation in BIND, potentially misleading DNS clients.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** ALPINE-CVE-2026-10723, AZL-93120, BELL-CVE-2026-10723, DEBIAN-CVE-2026-10723, ECHO-ed2d-c1b0-5e9e, GHSA-4fw4-hmvf-4www, MINI-h959-8whg-8c2p, MINI-jfjm-xxfg-945w, MINI-p9f7-r7hx-cqfc, UBUNTU-CVE-2026-10723

## What is CVE-2026-10723?

CVE-2026-10723 is a medium-severity vulnerability in ISC BIND 9, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-10723?


## How do I fix CVE-2026-10723?

Apply the vendor's patch.

## Is CVE-2026-10723 being exploited?

There is no known exploitation of CVE-2026-10723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10723 and fix it if it is affected.

What it is: CVE-2026-10723 is a medium-severity vulnerability in ISC BIND 9, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10723 in the wild and no public exploit code.

Affected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10723/ (Markdown: https://insights.sbomify.com/CVE-2026-10723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10723
- OSV: https://osv.dev/vulnerability/CVE-2026-10723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10723/
Summaries are generated and may contain mistakes; the official description above is the record.