CVE-2026-3591: BIND 9 SIG(0) Stack Use-After-Return ACL Bypass
- Vendor
- Internet Systems Consortium
CVE-2026-3591 is a stack use-after-return vulnerability in the BIND 9 named server's handling of SIG(0)-signed DNS queries. During asynchronous SIG(0) signature verification, the request-processing path passes a pointer to a stack-resident source-address structure into view-matching state. The request function can return before signature verification completes, leaving the asynchronous callback to dereference the invalid address while performing ACL evaluation. The resulting stale or garbage source-address data can cause an IP address to be incorrectly matched against an ACL. Affected releases are BIND 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and Supported Preview Edition 9.20.9-S1 through 9.20.20-S1. BIND 9.18 branches are not affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker may cause ACL evaluation to use invalid source-address data. In default-allow configurations that deny only selected source addresses, this can permit unauthorized access by causing a restricted client not to match the intended restrictive ACL or view. The flaw can also incorrectly deny legitimate clients. Default-deny ACL configurations are expected to fail secure. The stated primary security consequence is an access-control bypass rather than code execution or service termination.
Mitigation
If you can’t patch tonight, do this now.
Until an update can be deployed, use default-deny ACL policies where feasible, explicitly permit only required trusted source networks, and restrict access to SIG(0)-authenticated DNS services and affected views. Review ACL and view configurations that rely on deny-list semantics, as these are the configurations most likely to permit unauthorized access when matching fails. Monitor for unexpected ACL or view-selection behavior involving SIG(0)-signed requests.
Remediation
Patch, then assume compromise.
Upgrade BIND 9 to a fixed release: 9.20.21 or later for the 9.20 branch, or 9.21.20 or later for the 9.21 branch. Update Supported Preview Edition deployments to a vendor-fixed release. No remediation is required for BIND 9.18 because it is not affected.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-3591 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-3591 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-3591?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-3591.
- Is there a patch for CVE-2026-3591?
- Upgrade BIND 9 to a fixed release: 9.20.21 or later for the 9.20 branch, or 9.21.20 or later for the 9.21 branch. Update Supported Preview Edition deployments to a vendor-fixed release.
- What products are affected by CVE-2026-3591?
- Internet Systems Consortium Bind.
- How severe is CVE-2026-3591?
- CVE-2026-3591 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.38% (32nd percentile) as of Sep 25, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.