Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
10.0

Debian Linux: Unprivileged users can gain root access

DEBIAN-CVE-2026-42960
Summary

A security issue in Debian Linux allows unprivileged users to gain elevated privileges, potentially allowing them to access sensitive areas of the system or execute malicious code. This affects all Debian Linux systems and can be mitigated by keeping the system up to date with the latest security patches.

What to do
  • Update debian unbound to version 1.25.1-1.
Affected software
Ecosystem VendorProductAffected versions
Debian:11 debian unbound All versions
Debian:12 debian unbound All versions
Debian:13 debian unbound All versions
Debian:14 debian unbound < 1.25.1-1
Fix: upgrade to 1.25.1-1
Original title
NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the authority section. Promiscuous RRSets that complement DNS replies in the authority s...
Original description
NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via promiscuous records for the authority section. Promiscuous RRSets that complement DNS replies in the authority section can be used to trick Unbound to cache such records. If an adversary is able to attach such records in a reply (i.e., spoofed packet, fragmentation attack) he would be able to poison Unbound's cache. A malicious actor can exploit the possible poisonous effect by injecting RRSets other than NS that are also accompanied by address records in a reply, for example MX. This could be achieved by trying to spoof a reply packet or fragmentation attacks. Unbound would then accept the relative address records in the additional section and cache them if the authority RRSet has enough trust at this point, i.e., in-zone data for the delegation point. Unbound 1.25.1 contains a patch with a fix that disregards address records from the additional section if they are not explicitly relevant only to authority NS records, mitigating the possible poison effect. This is a complement fix to CVE-2025-11411.
Published: 20 May 2026 · Updated: 23 May 2026 · First seen: 21 May 2026