ASR AI Security Radar
Back to homepage

Recent AI Security Incidents

This archive includes all published incident pages. Page 1 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: VU#281278: SGLang contains six different vulnerabilities including RCE, data exfiltra...

Incident date: July 30, 2026 | Published: July 30, 2026

Overview Six vulnerabilities have been discovered within the SGLang project, including remote code execution (RCE), server-side request forgery (SSRF), local file read, credential leakage, and model weight exfiltration on a target server.

Read details

AI security incident: VU#326070: SGLang contains a vulnerable pickle deserialization vulnerability through...

Incident date: July 16, 2026 | Published: July 16, 2026

Overview A Pickle deserialization vulnerability has been discovered within the SGLang project , enabling an attacker to perform remote code execution (RCE) on the target vulnerable server.

Read details

AI security incident: CVE-2025-66389 (NVD)

Incident date: June 22, 2026 | Published: August 20, 2026

GitHub Copilot 1.372.0 allows filesystem access outside of a workspace folder (without user approval) via a file-handler URI parameter to fetch webpage. Therefore, exfiltration could occur if there is indirect prompt injection.

Read details

AI security incident: VU#777338: SGLang contains two remote code execution and one path traversal vulnerabi...

Incident date: May 18, 2026 | Published: May 18, 2026

Overview Three vulnerabilities have been discovered in the SGLang project, two enabling remote code execution (RCE), and one regarding a path traversal vulnerability.

Read details

AI security incident: Keras vulnerable to DoS via Malicious .keras Model (HDF5 Shape Bomb Causes Petabyte A...

Incident date: May 6, 2026 | Published: May 7, 2026

Keras vulnerable to DoS via Malicious .keras Model (HDF5 Shape Bomb Causes Petabyte Allocation in KerasFileEditor) Summary Keras’s model loader (KerasFileEditor) unsafely loads user-supplied .

Read details

AI security incident: PPTAgent: Arbitrary Code Execution via Python eval() of LLM-Generated Code with Built...

Incident date: May 5, 2026 | Published: May 5, 2026

PPTAgent: Arbitrary Code Execution via Python eval() of LLM-Generated Code with Builtins in Scope Summary This vulnerability has been fixed in https://github.com/icip-cas/PPTAgent/commit/418491a9a1c02d9d93194b5973bb58df35cf9d00.

Read details

AI security incident: Pelican Web UI Affected by a Privilege Escalation Attack (GHSA-rpfr-x88x-xwcw)

Incident date: May 4, 2026 | Published: May 4, 2026

Pelican Web UI Affected by a Privilege Escalation Attack Background On April 2nd, 2026, a Claude coding agent alerted Pelican PI Brian Bockelman to a privilege escalation vulnerability affecting Pelican's Web User Interface...

Read details

AI security incident: Gemini CLI: Remote Code Execution via workspace trust and tool allowlisting bypasses...

Incident date: April 24, 2026 | Published: April 24, 2026

Gemini CLI: Remote Code Execution via workspace trust and tool allowlisting bypasses Summary Gemini CLI (@google/gemini-cli) and the run-gemini-cli GitHub Action are being updated to harden workspace trust and tool allowlisting, in...

Read details

AI security incident: k8sGPT has Prompt Injection through its k8sGPT-Operator (GHSA-rp7v-4384-hfrp)

Incident date: April 24, 2026 | Published: April 24, 2026

k8sGPT has Prompt Injection through its k8sGPT-Operator Summary In the auto-remediation pipeline, object to execution.go was deserializing the AI-generated YAML directly into a Deployment object, but there was lack of...

Read details

AI security incident: Claude Code: Trust Dialog Bypass via Git Worktree Spoofing Allows Arbitrary Code Exec...

Incident date: April 24, 2026 | Published: April 24, 2026

Claude Code: Trust Dialog Bypass via Git Worktree Spoofing Allows Arbitrary Code Execution Claude Code used the git worktree commondir file when determining folder trust but did not validate its contents.

Read details