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	Flags	Published
	Medium	6.9	CVE-2026-115388	wasmtime-wasi-http in Wasmtime before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1 does not enforce the wasi:io/streams check-write allowance for WASIp2 outgoing... bytecodealliance, Wasmtimebytecodealliance wasmtime, wasmtime-wasi-http	NVD		Oct 22 19:17 UTC
CVE-2026-115388wasmtime-wasi-http in Wasmtime before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1 does not enforce the wasi:io/streams check-write allowance for WASIp2 outgoing... Executive summary A flaw in the wasmtime-wasi-http component of the Wasmtime WebAssembly runtime lets guest code exhaust host memory and cause a denial of service. The advisory rates it Moderate with a CVSS v3.1 base score of 6.2 and recommends upgrading to patched versions 36.0.16, 48.0.3, or 49.0.1. Technical summary The vulnerability is classified as uncontrolled resource consumption (CWE-400) and allocation without limits (CWE-770). The wasmtime-wasi-http component does not enforce the write allowance returned by wasi:io/streams check-write for WASIp2 outgoing HTTP bodies, so a guest can pass a buffer larger than permitted and have the write succeed, holding host allocations for the lifetime of the store. The advisory states affected versions as before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1, with fixes in 36.0.16, 48.0.3, and 49.0.1. The attack vector is local, requires no privileges or user interaction, and the CVSS vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. No workaround is stated, and no detection guidance is stated. Whether the flaw is exploited in the wild is not stated. 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-c9gc-w9vx-w86p Impact if exploited ConfidentialityNone IntegrityNone AvailabilityHigh 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: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-http 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

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee