DHI-wgnc-ioxs-6ntt-wshb

Source
https://scout.docker.com/v/DHI-wgnc-ioxs-6ntt-wshb
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-wgnc-ioxs-6ntt-wshb.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-wgnc-ioxs-6ntt-wshb
Upstream
Published
2026-11-11T15:55:45Z
Modified
2026-11-20T18:15:21Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
  • 4.6 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/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:Amber CVSS Calculator
Summary
NLnet Labs Unbound 1.14.0 up to and including version 1.25.0 has a locking inconsistency vulnerability that when…
Details

NLnet Labs Unbound 1.14.0 up to and including version 1.25.0 has a locking inconsistency vulnerability that when certain conditions are met (multi-threaded, RPZ XFR reload, RPZ zone with 'rpz-nsip'/'rpz-nsdname' triggers) it could result in heap use-after-free and eventual crash. An adversary can exploit the vulnerability if conditions are first met on a vulnerable Unbound, i.e., multi-threaded, an RPZ zone with 'rpz-nsip'/'rpz-nsdname' triggers and an ongoing XFR for that RPZ zone. Local RPZ files do not trigger the vulnerability. If the timing is right and an XFR happens at the same time another thread needs to read that RPZ zone, the reader may not hold the lock long enough and the thread applying the XFR may free objects that the reader is about to walk causing the use-after-free. Unbound 1.25.1 contains a patch with a fix to the locking code.

References

Affected packages

Docker Hardened Images:Alpine:3.23 / unbound

Package

Name
unbound
Purl
pkg:apk/dhi/unbound

Affected ranges

Affected versions

1.*
1.24.2-r0
1.25.2-r0
1.25.2-r1
1.25.2-r2

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-wgnc-ioxs-6ntt-wshb.json"