DHI-c5sd-h6ek-ruja-a6lt

Source
https://scout.docker.com/v/DHI-c5sd-h6ek-ruja-a6lt
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-c5sd-h6ek-ruja-a6lt.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-c5sd-h6ek-ruja-a6lt
Upstream
  • CVE-2026-35501
Published
2026-11-11T15:55:45Z
Modified
2026-11-16T02:34:57Z
Severity
  • 3.7 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N CVSS Calculator
Summary
When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an…
Details

When NLnet Labs Unbound 1.0.1 up to and including version 1.26.1 is configured with both a root trust anchor and an additional 'trust-anchor:' for an island-of-security zone whose parent is provably insecure under the root chain, a malicious actor with a forged NSEC reply with the SOA bit cleared can trick Unbound to treat the configured trust island as insecure. This happens because the DNSSEC validator in Unbound accepts and caches the NSEC insecure response bypassing the RRSIG validation that the validator was supposed to do. The acceptance of the NSEC record at the trust anchor apex was allowed due to and old fix for type DS and NSEC queries from clients when trust anchor for that name existed.

References

Affected packages

Docker Hardened Images:Alpine:3.24 / unbound

Package

Name
unbound
Purl
pkg:apk/dhi/unbound

Affected ranges

Affected versions

1.*
1.25.1-r0
1.25.2-r0
1.25.2-r1
1.25.2-r2
1.25.2-r3

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-c5sd-h6ek-ruja-a6lt.json"

Docker Hardened Images:Debian:13 / unbound

Package

Name
unbound
Purl
pkg:deb/dhi/unbound

Affected ranges

Affected versions

1.*
1.22.0-2+deb13u3+dhi0
1.22.0-2+deb13u3+dhi1
1.26.1-0+deb13u1+dhi0
1.26.2-0+deb13u1+dhi0

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-c5sd-h6ek-ruja-a6lt.json"