Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 04:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

154-74% vs 7-day avg of 597

2 critical, 44 high, 61 medium, 27 low

Expand	Severity	Score	Advisory	Title	Source	Published
	High	8.8	CVE-2026-115392	Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std... bytecodealliance, Wasmtimebytecodealliance wasmtime, Wasmtime, wasmtime-wasi	NVD	Oct 22 19:17 UTC
CVE-2026-115392Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std... Executive summary A flaw in Wasmtime, a WebAssembly runtime, lets guest code escape its filesystem sandbox and read or write files outside it on the host. The advisory rates it High with a CVSS v4 base score of 8.8 and recommends upgrading to a patched Wasmtime release (24.0.13, 36.0.14, 46.0.3, or 47.0.4, depending on the branch). Technical summary The weakness is CWE-61 (UNIX symbolic link following) in the wasmtime-wasi crate, which relies on the cap-std crate, where a trailing slash in paths or symlinks can escape the sandbox. The attack vector is network, with low complexity, requires low privileges, and needs passive user interaction; the advisory's CVSS v4 vector is CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L. Affected versions are listed as up to and including 24.0.12, 25.0.0 through 36.0.13, 37.0.0 through 46.0.2, and 47.0.0 through 47.0.3; patched versions are 24.0.13, 36.0.14, 46.0.3, and 47.0.4, and release 48.0.0 and later is stated as not affected. The advisory says Linux kernels after 5.6 with openat2 are not affected, while macOS and older Linux kernels are. No workaround is stated (the advisory says there is no known workaround), and no detection guidance or evidence of exploitation in the wild is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Dropped extracted product not named in the source: Bytecode Alliance cap-std Summarized from github.com/bytecodealliance/wasmtime/se…/GHSA-vqjp-4c8c-hfgg Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityLow How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required Low User interaction Passive CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/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 Affects bytecodealliance Wasmtime bytecodealliance wasmtime Wasmtime wasmtime-wasi NIST National Vulnerability DatabasePublished Oct 22, 2026 19:17 UTC Read the advisory
	Low	2.1	CVE-2026-115386	Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains an information disclosure vulnerability in the WASIp1 fd_readdir implementation that copies... bytecodealliance, Wasmtimebytecodealliance wasmtime, Wasmtime, wasmtime-wasi	NVD	Oct 22 19:17 UTC
CVE-2026-115386Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains an information disclosure vulnerability in the WASIp1 fd_readdir implementation that copies... Executive summary Wasmtime, a WebAssembly runtime, has an information disclosure flaw that can leak a few bytes of host memory to guest programs that have a preopened directory. The advisory rates it Low severity, and the vendor recommends upgrading to a patched release because no workaround is available when WASIp1 is enabled with a preopened directory. Technical summary The flaw is classified as CWE-908, use of uninitialized resource, in the WASIp1 fd_readdir implementation, where struct padding bytes from the host are copied into guest memory, leaking 3 bytes per directory entry. The attack vector is network with low privileges and passive user interaction, and it only affects guests with a preopened directory when WASIp1 is enabled. Affected versions are stated as before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2, with fixed versions 36.0.17, 48.0.4, and 49.0.2. The advisory states there is no workaround when WASIp1 is enabled and guests have preopened directory access. The advisory does not state whether exploitation in the wild has occurred, and it gives no specific detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/bytecodealliance/wasmtime/se…/GHSA-96f6-r43r-8c24 Impact if exploited ConfidentialityLow IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required Low User interaction Passive CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/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 Affects bytecodealliance Wasmtime bytecodealliance wasmtime Wasmtime wasmtime-wasi NIST National Vulnerability DatabasePublished Oct 22, 2026 19:17 UTC Read the advisory
	Medium	5.9	CVE-2026-115381	Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains an unbounded memory allocation in the wasmtime-wasi WASIp2 write-zeroes method of... bytecodealliance, Wasmtimebytecodealliance wasmtime, wasmtime-wasi	NVD	Oct 22 19:17 UTC
CVE-2026-115381Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains an unbounded memory allocation in the wasmtime-wasi WASIp2 write-zeroes method of... Executive summary A memory allocation flaw in Wasmtime, a WebAssembly runtime, affects embeddings that do not configure stdout or stderr streams. Exploitation could exhaust memory on the host, and the advisory rates the issue Moderate with a CVSS v4 base score of 5.9. The vendor recommends upgrading to Wasmtime 36.0.17, 48.0.4, or 49.0.2, or applying a custom OutputStream workaround. Technical summary The flaw is CWE-770, allocation of resources without limits, in the wasmtime-wasi WASIp2 write-zeroes method for SinkOutputStream, which allows an unlimited-size allocation of a buffer of zeros on the host. It affects only embeddings that do not configure stdout or stderr streams, and the CVSS v4 vector indicates network attack vector, low attack complexity, low privileges required, passive user interaction, and high availability impact. Affected versions are below 36.0.17, from 37.0.0 before 48.0.4, and from 49.0.0 before 49.0.2, with fixed versions 36.0.17, 48.0.4, and 49.0.2. The advisory recommends a custom OutputStream whose check_write returns a limited value as a workaround, or updating to a patch release. The advisory does not state whether the issue is being exploited in the wild, and it does not provide specific detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/bytecodealliance/wasmtime/se…/GHSA-gqmc-89g8-p25r Impact if exploited ConfidentialityNone IntegrityNone AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required Low User interaction Passive CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/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 Affects bytecodealliance Wasmtime bytecodealliance wasmtime wasmtime-wasi NIST National Vulnerability DatabasePublished Oct 22, 2026 19:17 UTC Read the advisory
	Medium	5.1	CVE-2026-115380	Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains a denial of service vulnerability in the wasmtime-wasi WASI preview 0 poll_oneoff adapter,... bytecodealliance, Wasmtimebytecodealliance wasmtime, wasmtime-wasi, Wasmtime CLI	NVD	Oct 22 19:17 UTC
CVE-2026-115380Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains a denial of service vulnerability in the wasmtime-wasi WASI preview 0 poll_oneoff adapter,... Executive summary A flaw in the Wasmtime WebAssembly runtime's WASI preview 0 poll_oneoff adapter lets guest code run long computations that skip fuel limits, enabling denial of service on affected hosts. The advisory rates it Moderate with a CVSS 3.1 base score of 4.0, and the vendor's fix is to upgrade to patched releases (36.0.17, 48.0.4, or 49.0.2) or disable WASI preview 0 in the CLI. Technical summary The weakness is a resource exhaustion issue: the WASI preview 0 poll_oneoff adapter in wasmtime-wasi performs work proportional to the number of subscriptions without consuming fuel or checking whether fuel has run out, because the adapter rewrites each subscription before calling the WASI preview 1 implementation, which is the only path with a fuel check. The attack requires a local guest with no privileges, and the CVSS vector is AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. Affected versions are below 36.0.17, from 37.0.0 before 48.0.4, and from 49.0.0 before 49.0.2; patched versions are 36.0.17, 48.0.4, and 49.0.2. The CLI is affected by default, while library users are affected only if they explicitly enable WASI preview 0. The stated workaround is disabling WASI preview 0 in the CLI with -Spreview0=n. The advisory does not state any detection guidance or evidence of exploitation in the wild. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/bytecodealliance/wasmtime/se…/GHSA-j366-h8gg-77pm Impact if exploited ConfidentialityNone IntegrityNone AvailabilityLow How it is exploited Attack vector Local Attack complexity Low Attack requirements None Privileges required None User interaction None CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/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 Affects bytecodealliance Wasmtime bytecodealliance wasmtime wasmtime-wasi Wasmtime CLI NIST National Vulnerability DatabasePublished Oct 22, 2026 19:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee