What changed in AI security—and what needs your attention.

BugSkan consolidates security reporting into scannable incidents with clear response guidance. Currently watching 162 sources.

Lead story

One development worth checking first

REVIEW Vulnerability

PyTorch Remote Code Execution Vulnerability

Who should check
Confirm whether PyTorch is present in your environment and review the affected configuration.
What changed
Publisher reporting describes a security event affecting aged. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 12d ago 3 publishers Multiple publisher reports
Read incident →

Latest intelligence

Scannable incident feed

Filter by category or response. Research stays separate from patchable vulnerabilities.

1,046 reports → 305 items
REVIEW Vulnerability

F5 DoS for Nginx heap buffer overflow Vulnerability

Who should check
Confirm whether F5 is present in your environment, compare your versions against the report, and apply available vendor patches or mitigations.
What changed
Publisher reporting describes a security event affecting F5 and references CVE-2026-40701, CVE-2026-42934, CVE-2026-42945. Treat the source details as the current record until affected versions and vendor remediation are confirmed.
Published 1d ago 3 publishers Multiple publisher reports
Read incident →
WATCH Vulnerability

CVE-2026-109618 Security Incident affecting Amazon AWS

Attackers TryDeploy Mirai Malware
Who should check
Confirm whether Millions is present in your environment, compare your versions against the report, and apply available vendor patches or mitigations.
What changed
Publisher reporting describes a security event affecting Millions. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 1d ago 2 publishers Early multi-source coverage
Read incident →
WATCH Research & guidance

From eMudhra to PHP: Breach spree hits tech infrastructure, AI emerges as threat multiplier

aroundincidents
Who should check
Confirm whether any named organizations, identity tenants, or cloud environments you operate are implicated.
What changed
This is source reporting of a security event, not a confirmed product vulnerability or patchable CVE. Use it as situational awareness if named organizations, cloud tenants, or identity systems overlap with yours.
Published 5d ago 1 publisher Limited source evidence
Read incident →
WATCH Research & guidance

“Next Exploit Opportunities”: How a Threat Actor Used AI to Help Plan and Execute Multiple Types of Cybercrime Activities

Cybercrime ActivitiesExecute Multiple Types
Who should check
Confirm whether any named organizations, identity tenants, or cloud environments you operate are implicated.
What changed
This is source reporting of a security event, not a confirmed product vulnerability or patchable CVE. Use it as situational awareness if named organizations, cloud tenants, or identity systems overlap with yours.
Published 5d ago 1 publisher Limited source evidence
Read incident →
WATCH Vulnerability

Adobe Commerce Backdoor Vulnerability

Adobe CommerceClaude
Who should check
Confirm whether and is present in your environment and review vendor guidance for this report.
What changed
Publisher reporting describes a security event affecting and. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 6d ago 2 publishers Early multi-source coverage
Read incident →
WATCH Vulnerability

Google API Keys Data Exposure

chargesfixes
Who should check
Confirm whether oct is present in your environment and review vendor guidance for this report.
What changed
The evidence matters to defenders using Google API Keys because it may expose sensitive data handled by affected deployments.
Published 8d ago 1 publisher Limited source evidence
Read incident →
WATCH Vulnerability

Magento Security Incident

MagentoCritical BlockStrap
Who should check
Confirm whether Magento is present in your environment, compare your versions against the report, and apply available vendor patches or mitigations.
What changed
Publisher reporting describes a security event affecting Magento. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 10d ago 1 publisher Limited source evidence
Read incident →
WATCH Vulnerability

Anthropic Remote Code Execution Vulnerability

almostversion
Who should check
Confirm whether Gat is present in your environment, compare your versions against the report, and apply available vendor patches or mitigations.
What changed
The evidence matters to defenders using Anthropic because it could let an attacker run code in affected environments.
Published 12d ago 1 publisher Limited source evidence
Read incident →
WATCH Vulnerability

Langflow Security Incident

LangflowCritical Authenticated RCE
Who should check
Confirm whether february is present in your environment, compare your versions against the report, and apply available vendor patches or mitigations.
What changed
Publisher reporting describes a security event affecting february. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 12d ago 1 publisher Limited source evidence
Read incident →
REVIEW Vulnerability

Easy Part Authentication Bypass

Easy PartProduction
Who should check
Confirm whether Found is present in your environment and review vendor guidance for this report.
What changed
The evidence matters to defenders using Easy Part because it could allow access without the expected authentication controls.
Published 13d ago 1 publisher Limited source evidence
Read incident →

Explore all intelligence →

Technology watchlist

Follow the stack you actually run

Open a technology page for directly affected issues, attacks involving it, and research that only mentions it.

Follow technologies →

Weekly briefing

What readers get each week

Sample brief

  • Top ACT / REVIEW developments affecting popular AI tools
  • One paragraph on what changed and who should check
  • Links back to full BugSkan incidents with sources

Research & explainers

Analysis, separate from incident reporting

Browse research →
IGNORE Research & guidance

AI Security Breach

stealthan
Who should check
Confirm whether ARTEX AI is present in your environment and review the affected configuration.
What changed
Current evidence identifies a security issue involving ARTEX AI, but does not yet support a more specific impact claim.
Published 16h ago 1 publisher Limited source evidence
Read incident →
IGNORE Research & guidance

AI Prompt Injection Vulnerability

Who should check
Confirm whether the affected technology is present in your environment and review the affected configuration.
What changed
Current evidence identifies a security issue involving the affected technology, but does not yet support a more specific impact claim.
Published 16h ago 1 publisher Limited source evidence
Read incident →
IGNORE Research & guidance

OpenAI AI Security Breach Triggers 14-State Legal Reckoning

Who should check
Confirm whether and is present in your environment and review vendor guidance for this report.
What changed
Publisher reporting describes a security event affecting and. BugSkan could not yet bind a CVE or affected version, so treat the source details as the current record.
Published 4d ago 5 publishers Multiple publisher reports
Read incident →