DHI-3a5c-wn6t-vzke-ndbk

Source
https://scout.docker.com/v/DHI-3a5c-wn6t-vzke-ndbk
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-3a5c-wn6t-vzke-ndbk.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-3a5c-wn6t-vzke-ndbk
Upstream
Published
2026-11-10T07:27:12Z
Modified
2026-11-21T14:15:53Z
Severity
  • 8.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H CVSS Calculator
  • 9.0 (Critical) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/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 CVSS Calculator
Summary
Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime with its Winch…
Details

Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime with its Winch (baseline) non-default compiler backend may allow properly constructed guest Wasm to access host memory outside of its linear-memory sandbox. This vulnerability requires use of the Winch compiler (-Ccompiler=winch). By default, Wasmtime uses its Cranelift backend, not Winch. With Winch, the same incorrect assumption is present in theory on both aarch64 and x86-64. The aarch64 case has an observed-working proof of concept, while the x86-64 case is theoretical and may not be reachable in practice. This Winch compiler bug can allow the Wasm guest to access memory before or after the linear-memory region, independently of whether pre- or post-guard regions are configured. The accessible range in the initial bug proof-of-concept is up to 32KiB before the start of memory, or ~4GiB after the start of memory, independently of the size of pre- or post-guard regions or the use of explicit or guard-region-based bounds checking. However, the underlying bug assumes a 32-bit memory offset stored in a 64-bit register has its upper bits cleared when it may not, and so closely related variants of the initial proof-of-concept may be able to access truly arbitrary memory in-process. This could result in a host process segmentation fault (DoS), an arbitrary data leak from the host process, or with a write, potentially an arbitrary RCE. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

References

Affected packages

Docker Hardened Images:Debian:13 / apisix-3

Package

Name
apisix-3
Purl
pkg:deb/dhi/apisix-3

Affected ranges

Affected versions

3.*
3.17.0-0
3.18.0-0
3.18.0-1
3.18.0-2
3.18.0-3
3.19.0-0
3.19.0-1
3.19.0-2
3.19.0-3
3.20.0-0
3.20.0-1
3.21.0-0

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-3a5c-wn6t-vzke-ndbk.json"

Docker Hardened Images:Debian:13 / influxdb3-3.10

Package

Name
influxdb3-3.10
Purl
pkg:deb/dhi/influxdb3-3.10

Affected ranges

Affected versions

3.*
3.10.6-0
3.10.6-1

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-3a5c-wn6t-vzke-ndbk.json"

Docker Hardened Images:Debian:13 / influxdb3-3.11

Package

Name
influxdb3-3.11
Purl
pkg:deb/dhi/influxdb3-3.11

Affected ranges

Affected versions

3.*
3.11.8-0
3.11.10-0
3.11.10-1

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-3a5c-wn6t-vzke-ndbk.json"