ASR AI Security Radar
Back to homepage

Recent AI Security Incidents

This archive includes all published incident pages. Page 7 of 18.

Each page is intended to help a security team answer three questions quickly: why the issue is AI-relevant, what part of the workflow may be exposed, and what actions should happen first.

Selection criteria and correction policy are documented in Methodology & Editorial Policy.

AI security incident: Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion...

Incident date: February 24, 2026 | Published: February 25, 2026

Impact Wasmtime's implementation of WASI host interfaces are susceptible to guest-controlled resource exhaustion on the host. Wasmtime did not appropriately place limits on resource allocations requested by the guests.

Read details

AI security incident: Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future (GHS...

Incident date: February 24, 2026 | Published: February 25, 2026

The affected versions of Wasmtime can panic if the host embedder drops the future returned by wasmtime::component::[Typed]Func::call_async before it resolves. ### Details Starting with Wasmtime 39.0.

Read details

AI security incident: Caddy: Unicode case-folding length expansion causes incorrect split_path index in Fas...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary Caddy's FastCGI path splitting logic computes the split index on a lowercased copy of the request path and then uses that byte index to slice the original path. This is unsafe for Unicode because strings.

Read details

AI security incident: Caddy: MatchHost becomes case-sensitive for large host lists (>100), enabling host-ba...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary Caddy's HTTP host request matcher is documented as case-insensitive, but when configured with a large host list (>100 entries) it becomes case-sensitive due to an optimized matching path.

Read details

AI security incident: Caddy: MatchPath %xx (escaped-path) branch skips case normalization, enabling path-ba...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary Caddy's HTTP path request matcher is intended to be case-insensitive, but when the match pattern contains percent-escape sequences ( %xx ) it compares against the request's escaped path without lowercasing.

Read details

AI security incident: Caddy: mTLS client authentication silently fails open when CA certificate file is mis...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary Two swallowed errors in ClientAuthentication.provision() cause mTLS client certificate authentication to silently fail open when a CA certificate file is missing, unreadable, or malformed.

Read details

AI security incident: ActualBudget server is Missing Authentication for SimpleFIN and Pluggy AI bank sync e...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary Missing authentication middleware in the ActualBudget server component allows any unauthenticated user to query the SimpleFIN and Pluggy.ai integration endpoints and read sensitive bank account balance and transaction information.

Read details

AI security incident: MindsDB: Path Traversal in /api/files Leading to Remote Code Execution (GHSA-4894-xqv...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary There is a path traversal vulnerability in Mindsdb's /api/files interface, which an authenticated attacker can exploit to achieve remote command execution.

Read details

AI security incident: Isso affected by Stored XSS via comment website field (GHSA-9fww-8cpr-q66r)

Incident date: February 24, 2026 | Published: February 25, 2026

Impact This is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped.

Read details

AI security incident: OneUptime:: node:vm sandbox escape in probe allows any project member to achieve RCE...

Incident date: February 24, 2026 | Published: February 25, 2026

Summary OneUptime lets project members write custom JavaScript that runs inside monitors. The problem is it executes that code using Node.js's built-in vm module, which Node.

Read details