CVE-2025-11411: Possible domain hijacking via promiscuous records in the authority section
Noroxi assessment
Priority: Monitor (action score 22/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.33% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 unbound 1.19.1-4 on Azure Linux 3.0 1.19.1-5; azl3 unbound 1.19.1-5 on Azure Linux 3.0 1.19.1-5; cbl2 unbound 1.19.1-3 on CBL Mariner 2.0 1.19.1-4.
Low priority for now. Upgrade to azl3 unbound 1.19.1-4 on Azure Linux 3.0 1.19.1-5; azl3 unbound 1.19.1-5 on Azure Linux 3.0 1.19.1-5; cbl2 unbound 1.19.1-3 on CBL Mariner 2.0 1.19.1-4 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
NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.
- BDU:2026-03595
- ALSA-2026:18556
- ALSA-2026:18931
- DLA-4365-1
- DLA-4365-2
- DSA-6071-1
- openSUSE-SU-2025:15668-1
- openSUSE-SU-2026:20139-1
- RHSA-2026:18556
- RHSA-2026:18931
- RHSA-2026:7645
- RLSA-2026:18556
- RLSA-2026:18931
- SUSE-SU-2025:21050-1
- SUSE-SU-2025:21065-1
- SUSE-SU-2025:4134-1
- SUSE-SU-2025:4391-1
- SUSE-SU-2026:20180-1
- SUSE-SU-2026:20201-1
- Published
- Oct 22, 2025
- Updated
- Oct 8, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-349
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · NLnet Labs
- 5.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P
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 itNoroxi 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 helpAffected 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.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (NLnet Labs). Independent of NVD's CPE analysis and usually ahead of it.
NLnet Labs Unbound
- up to and including 1.24.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | python3-unbound | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound-anchor | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound-devel | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound-dracut | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound-libs | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:10 | unbound-utils | before 1.24.2-7.el10 | 1.24.2-7.el10 |
| AlmaLinux:9 | python3-unbound | before 1.24.2-2.el9 | 1.24.2-2.el9 |
| AlmaLinux:9 | unbound | before 1.24.2-2.el9 | 1.24.2-2.el9 |
| AlmaLinux:9 | unbound-devel | before 1.24.2-2.el9 | 1.24.2-2.el9 |
| AlmaLinux:9 | unbound-dracut | before 1.24.2-2.el9 | 1.24.2-2.el9 |
| AlmaLinux:9 | unbound-libs | before 1.24.2-2.el9 | 1.24.2-2.el9 |
| Alpine:v3.19 | unbound | before 1.20.0-r2 | 1.20.0-r2 |
| Alpine:v3.21 | unbound | before 1.22.0-r1 | 1.22.0-r1 |
| Alpine:v3.22 | unbound | before 1.23.1-r1 | 1.23.1-r1 |
| Alpine:v3.23 | unbound | before 1.24.1-r0 | 1.24.1-r0 |
| Debian:11 | unbound | before 1.13.1-1+deb11u7 | 1.13.1-1+deb11u7 |
| Debian:11 | unbound | before 1.13.1-1+deb11u6 | 1.13.1-1+deb11u6 |
| Debian:12 | unbound | before 1.17.1-2+deb12u4 | 1.17.1-2+deb12u4 |
| Debian:13 | unbound | before 1.22.0-2+deb13u1 | 1.22.0-2+deb13u1 |
| Debian:14 | unbound | before 1.24.2-1 | 1.24.2-1 |
| openSUSE:Leap 15.6 | unbound | before 1.20.0-150600.23.13.1 | 1.20.0-150600.23.13.1 |
| openSUSE:Leap 16.0 | unbound | before 1.24.1-160000.1.1 | 1.24.1-160000.1.1 |
| openSUSE:Tumbleweed | unbound | before 1.24.1-1.1 | 1.24.1-1.1 |
+37
Same product
nlnet labs: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-5994Cache poisoning via the ECS-enabled Rebirthday Attack34Monitor
- CVE-2026-97206DNS-over-QUIC (DoQ) path-migration can lead to use-after-free on multi-threaded deployments.30Monitor
- CVE-2026-50106Possible insecure NXDOMAIN for non-existing records under a configured island trust anchor underneath an insecure parent.26Monitor
Published before and after this one in the same product
- Later →CVE-2026-14586Jul 22, 2026 · Assertion in libngtcp2 when under pressure in high concurrency DNS-over-QUIC environments23Monitor
- Later →CVE-2026-109125Oct 21, 2026 · Possible cache poisoning vulnerability via a cache side-channel exposed by 'unwanted-reply-threshold'21Monitor
- Later →CVE-2026-35501Oct 21, 2026 · Bypass of a configured island trust anchor underneath an insecure parent from an atacker-controlled NSEC record.14Monitor
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 unbound 1.19.1-4 on Azure Linux 3.0 | 1.19.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 unbound 1.19.1-5 on Azure Linux 3.0 | 1.19.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 unbound 1.19.1-3 on CBL Mariner 2.0 | 1.19.1-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 unbound 1.19.1-4 on CBL Mariner 2.0 | 1.19.1-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:python3-unbound | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound-anchor | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound-devel | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound-dracut | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound-libs | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:unbound-utils | 1.24.2-7.el10 · AlmaLinux:10 | Package registry (OSV) |
| alpine:unbound | 1.20.0-r2 · Alpine:v3.19 | Package registry (OSV) |
| debian:unbound | 1.17.1-2+deb12u4 · Debian:12 | Package registry (OSV) |
| opensuse:unbound | 1.20.0-150600.23.13.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:python3-unbound | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:python3-unbound-debuginfo | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-anchor | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-anchor-debuginfo | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-debuginfo | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-debugsource | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-dracut | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-libs | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-libs-debuginfo | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-utils | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:unbound-utils-debuginfo | 0:1.24.2-7.el10 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:unbound | 0:1.24.2-7.el10 · Rocky Linux:10 | Package registry (OSV) |
| suse:unbound | 1.20.0-150600.23.13.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:unbound | 1.22.0-2.1 · SUSE:Linux Micro 6.0 | 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-599498 days apartCache poisoning via the ECS-enabled Rebirthday Attack34Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-349 · Acceptance of Extraneous Untrusted Data With Trusted DataCVSS vector
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
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)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.