NVD / CVE Program· CNA isc

CVE-2026-10723: Incorrect acceptance of NSEC3 records

MediumCVSS 6.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: azl3 bind 9.20.23-1 on Azure Linux 3.0 9.20.26-1.

Low priority for now. Upgrade to azl3 bind 9.20.23-1 on Azure Linux 3.0 9.20.26-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Jul 22, 2026
Updated: Nov 2, 2026
EPSS: 0.2% · 19th percentile
CWE: CWE-347

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · isc: 6.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
isc	bind	cpe:2.3:a:isc:bind

Versions reported by the vendor

Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.

ISC BIND 9
- 9.18.0 and later · up to and including 9.18.50affected
- 9.20.0 and later · up to and including 9.20.24affected
- 9.21.0 and later · up to and including 9.21.23affected
- 9.11.3-S1 and later · up to and including 9.18.50-S1affected
- 9.20.9-S1 and later · up to and including 9.20.24-S1affected

Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

isc bind9.11.3 and later · up to 9.18.50 inclusive
isc bind9.18.0 and later · up to 9.18.50 inclusive
isc bind9.20.0 and later · up to 9.20.24 inclusive
isc bind9.20.9 and later · up to 9.20.24 inclusive
isc bind9.21.0 and later · up to 9.21.23 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	bind	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-chroot	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-devel	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-dnssec-utils	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-doc	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-libs	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-license	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:10	bind-utils	before 32:9.18.33-15.el10_2.10	32:9.18.33-15.el10_2.10
AlmaLinux:8	bind	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-chroot	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-devel	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-export-devel	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-export-libs	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-libs	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-libs-lite	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-license	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-lite-devel	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-pkcs11	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-pkcs11-devel	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-pkcs11-libs	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-pkcs11-utils	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-sdb	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-sdb-chroot	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14
AlmaLinux:8	bind-utils	before 32:9.11.36-16.el8_10.14	32:9.11.36-16.el8_10.14

+96

Same product

isc: all records

Other highest-scoring records for the same primary product.

CVE-2015-5477named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion…KEV
90Now
CVE-2020-8617A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c
60This week
CVE-2016-2776buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct…
60This week

Published before and after this one in the same product

← EarlierCVE-2026-5947May 20, 2026 · SIG(0) validation during query flood may lead to undefined behavior
23Monitor
← EarlierCVE-2026-5950May 20, 2026 · Unbounded resend loop in BIND 9 resolver
21Monitor
Later →CVE-2026-10822Jul 22, 2026 · Key Record using PRIVATEDNS algorithm may lead to unexpected exit
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
azl3 bind 9.20.23-1 on Azure Linux 3.0	9.20.26-1 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:bind	32:9.16.23-40.el9_8.8 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-chroot	32:9.16.23-40.el9_8.8 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-devel	32:9.16.23-40.el9_8.8 · AlmaLinux:9	Package registry (OSV)
almalinux:bind9.16	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-chroot	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-devel	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-dnssec-utils	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-doc	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-libs	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-license	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-utils	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
almalinux:python3-bind9.16	32:9.16.23-0.22.el8_10.12 · AlmaLinux:8	Package registry (OSV)
alpine:bind	9.20.26-r0 · Alpine:v3.22	Package registry (OSV)
debian:bind9	1:9.18.49-1~deb12u2 · Debian:12	Package registry (OSV)
opensuse:bind	9.20.26-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:bind	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-chroot	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-devel	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-dnssec-utils	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-doc	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-libs	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind-utils	0:9.20.26-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:bind9.16	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-chroot	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-debuginfo	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-debugsource	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-dnssec-utils	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-dnssec-utils-debuginfo	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bind9.16-libs	32:9.16.23-0.22.el8_10.12 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Qifan ZhangPalo Alto Networks for bringing this vulnerability to our attention.

Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Changed
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

nvd-secondary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const claims = jwt.verify(token, publicKey);

Fixed

1const claims = jwt.verify(token, publicKey, {
2  algorithms: ["RS256"],
3  issuer: "https://id.example.com",
4  audience: "portal",
5});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

downloads.isc.org/isc/bind9/9.20.26

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records