unbound — security advisory
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.
- Products
- unbound
- Affected versions
- 1.17.1-2, 1.17.1-2+deb12u1, 1.17.1-2+deb12u2, 1.17.1-2+deb12u3, 1.22.0-2, 1.23.1-1, 1.24.0-1, 1.24.0-2, 1.24.1-1, 1.24.1-2
- Fixed versions
- 1.17.1-2+deb12u4, 1.22.0-2+deb13u1, 1.24.2-1
- CVEs
- CVE-2025-11411
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 28 Oct 2026, 11:07 UTC · Revision 1
Source evidence
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.
osv:DEBIAN-CVE-2025-11411
unbound
Fixed versions: 1.17.1-2+deb12u4
unbound
Fixed versions: 1.22.0-2+deb13u1
unbound
Fixed versions: 1.24.2-1
Complete source record
{
"id": "14efe64a03f5c47614d548043e175ee9c349267d177305eb90a8fcb3997c0881",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2025-11411",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2025-11411",
"summary": "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.",
"evidence": "osv:DEBIAN-CVE-2025-11411",
"products": [
{
"name": {
"value": "unbound",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.17.1-2+deb12u4",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "1.17.1-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.17.1-2+deb12u1",
"evidence": "/affected/0/versions"
},
{
"value": "1.17.1-2+deb12u2",
"evidence": "/affected/0/versions"
},
{
"value": "1.17.1-2+deb12u3",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "unbound",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.22.0-2+deb13u1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": [
{
"value": "1.22.0-2",
"evidence": "/affected/1/versions"
}
]
},
{
"name": {
"value": "unbound",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.24.2-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": [
{
"value": "1.22.0-2",
"evidence": "/affected/2/versions"
},
{
"value": "1.23.1-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.24.0-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.24.0-2",
"evidence": "/affected/2/versions"
},
{
"value": "1.24.1-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.24.1-2",
"evidence": "/affected/2/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2025-11411",
"aliases": [
"DEBIAN-CVE-2025-11411"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.17.1-2+deb12u4"
}
]
}
],
"package": {
"name": "unbound",
"purl": "pkg:deb/debian/unbound?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"1.17.1-2",
"1.17.1-2+deb12u1",
"1.17.1-2+deb12u2",
"1.17.1-2+deb12u3"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-11411.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.22.0-2+deb13u1"
}
]
}
],
"package": {
"name": "unbound",
"purl": "pkg:deb/debian/unbound?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"1.22.0-2"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-11411.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.24.2-1"
}
]
}
],
"package": {
"name": "unbound",
"purl": "pkg:deb/debian/unbound?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"1.22.0-2",
"1.23.1-1",
"1.24.0-1",
"1.24.0-2",
"1.24.1-1",
"1.24.1-2"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-11411.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-09T09:47:26.404397368Z",
"provider": "osv",
"upstream": [
"CVE-2025-11411"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2025-11411"
]
},
"related_cves": [
{
"value": "CVE-2025-11411",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 111504,
"published_at": "2025-10-22T13:15:29.21+00:00"
}