aisecwatch.com
DashboardVulnerabilitiesNewsResearchArchiveStatsDatasetFor devs
Subscribe
aisecwatch.com

Real-time AI security monitoring. Tracking AI-related vulnerabilities, safety and security incidents, privacy risks, research developments, and policy changes.

Navigation

VulnerabilitiesNewsResearchDigest ArchiveNewsletter ArchiveSubscribeData SourcesStatisticsDatasetAPIIntegrationsWidgetRSS Feed

Maintained by

Truong (Jack) Luu

Information Systems Researcher

AI Sec Watch

The security intelligence platform for AI teams

AI security threats move fast and get buried under hype and noise. Built by an Information Systems Security researcher to help security teams and developers stay ahead of vulnerabilities, privacy incidents, safety research, and policy developments.

Independent research. No sponsors, no paywalls, no conflicts of interest.

[TOTAL_TRACKED]
3,710
[LAST_24H]
1
[LAST_7D]
1
Daily BriefingSunday, May 17, 2026

No new AI/LLM security issues were identified today.

Latest Intel

page 180/371
VIEW ALL
01

Former Alphabet 'moonshot' robotics company Intrinsic is folding into Google

industry
Feb 25, 2026

Alphabet is folding its robotics software company Intrinsic into Google to streamline its business. Intrinsic developed Flowstate, a web-based platform that lets users build robotic applications without writing thousands of lines of code, addressing the challenge that programming robots remains extremely complex despite hardware becoming cheaper. By joining Google, Intrinsic will use Google's AI models and infrastructure to expand its industrial robotics platform for manufacturing and logistics.

CNBC Technology
02

GHSA-mhr3-j7m5-c7c9: LangGraph: BaseCache Deserialization of Untrusted Data may lead to Remote Code Execution

security
Feb 25, 2026

LangGraph versions before 4.0.0 have a remote code execution vulnerability in their caching layer when applications enable cache backends and opt nodes into caching. The vulnerability occurs because the default serializer uses pickle deserialization (a Python feature that can execute arbitrary code) as a fallback when other serialization methods fail, allowing attackers who can write to the cache to execute malicious code.

Fix: Upgrade to langgraph-checkpoint>=4.0.0, which disables pickle fallback by default (pickle_fallback=False).

GitHub Advisory Database
03

GHSA-76rv-2r9v-c5m6: zae-limiter: DynamoDB hot partition throttling enables per-entity Denial of Service

security
Feb 25, 2026

The zae-limiter library has a security flaw where all rate limit buckets for a single user share the same DynamoDB partition key (the identifier that determines which storage location holds the data), allowing a high-traffic user to exceed DynamoDB's write limits and cause service slowdowns for that user and potentially others sharing the same partition. This vulnerability affects multi-tenant systems, like shared LLM proxies (AI services shared across multiple customers), where one customer's heavy traffic can degrade service for others.

Fix: The source explicitly describes a remediation design called 'Pre-Shard Buckets' that includes: moving buckets to a new partition key format with sharding (`PK={ns}/BUCKET#{entity}#{resource}#{shard}, SK=#STATE`), auto-injecting a `wcu:1000` reserved limit on every bucket to track DynamoDB write pressure, implementing shard doubling (1→2→4→8) when capacity is exhausted, storing original limits on the bucket with effective limits derived by dividing by shard count, using random or round-robin shard selection with retry logic (maximum 2 retries), lazy shard creation on first access, discovering shards via GSI3 (a secondary index), and implementing a clean break migration with a schema version bump so old buckets are ignored and new buckets are created on first access.

GitHub Advisory Database
04

GHSA-vpcf-gvg4-6qwr: n8n: Expression Sandbox Escape Leads to RCE

security
Feb 25, 2026

n8n, a workflow automation tool, has a vulnerability where authenticated users with permission to create or modify workflows can exploit expression evaluation (the process of interpreting code within workflow parameters) to execute arbitrary system commands on the host server. This is a serious security flaw because it allows attackers to run unintended commands on the underlying system.

Fix: Upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not possible, limit workflow creation and editing permissions to fully trusted users only, and deploy n8n in a hardened environment with restricted operating system privileges and network access. However, these temporary mitigations do not fully remediate the risk.

GitHub Advisory Database
05

Flaws in Claude Code Put Developers' Machines at Risk

security
Feb 25, 2026

Flaws have been discovered in Claude (an AI assistant) that can put developers' computers at risk when Claude is used in software development workflows. These vulnerabilities could potentially affect supply chains, which are the networks of companies and systems that work together to deliver software and products.

Dark Reading
06

GHSA-x2mw-7j39-93xq: n8n has Arbitrary Command Execution via File Write and Git Operations

security
Feb 25, 2026

n8n (a workflow automation tool) has a vulnerability where an authenticated user with workflow editing permissions could combine the Read/Write Files from Disk node (a component that modifies files on the server) with git operations (version control commands) to execute arbitrary shell commands (any commands an attacker chooses) on the n8n server. This requires the attacker to already have valid user access.

Fix: The issue has been fixed in n8n versions 2.2.0 and 1.123.8. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can temporarily: (1) Limit workflow creation and editing permissions to fully trusted users only, or (2) Disable the Read/Write Files from Disk node by adding `n8n-nodes-base.readWriteFile` to the `NODES_EXCLUDE` environment variable. The source notes these workarounds do not fully remediate the risk and should only be short-term measures.

GitHub Advisory Database
07

GHSA-wxx7-mcgf-j869: n8n has Potential Remote Code Execution via Merge Node

security
Feb 25, 2026

n8n, a workflow automation tool, has a vulnerability where authenticated users with workflow editing permissions could use the Merge node's SQL query mode to execute arbitrary code (running any commands they want on the server) and write files to the n8n server. This is a serious security issue because it lets trusted insiders cause significant damage.

Fix: The vulnerability is fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22 or later. If upgrading immediately is not possible, administrators can temporarily restrict workflow creation and editing permissions to only fully trusted users, or disable the Merge node by adding `n8n-nodes-base.merge` to the `NODES_EXCLUDE` environment variable (a configuration setting that tells n8n which features to turn off). Note: these workarounds do not fully eliminate the risk and are only short-term measures.

GitHub Advisory Database
08

GHSA-jjpj-p2wh-qf23: n8n has a Sandbox Escape in its JavaScript Task Runner

security
Feb 25, 2026

n8n, a workflow automation tool, has a sandbox escape vulnerability in its JavaScript Task Runner that lets authenticated users run code outside the sandbox (a restricted environment for running untrusted code). On default setups, this could give attackers full control of the n8n server, while on systems using external task runners, attackers could impact other workflows.

Fix: Upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not possible, temporarily limit workflow creation and editing permissions to trusted users only, or use external runner mode by setting N8N_RUNNERS_MODE=external to reduce potential damage.

GitHub Advisory Database
09

GHSA-75g8-rv7v-32f7: n8n has Unauthenticated Expression Evaluation via Form Node

security
Feb 25, 2026

n8n had a vulnerability in its Form nodes where an unauthenticated attacker could inject malicious code by submitting specially crafted form data that starts with an equals sign (=), which the system would then execute as an expression. While this vulnerability alone is limited, it could potentially lead to remote code execution if combined with another type of attack that bypasses n8n's expression sandbox (a security boundary that restricts what code can access).

Fix: The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can temporarily: (1) manually review form nodes to check if they have the problematic configuration, (2) disable the Form node by adding `n8n-nodes-base.form` to the `NODES_EXCLUDE` environment variable, or (3) disable the Form Trigger node by adding `n8n-nodes-base.formTrigger` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term measures.

GitHub Advisory Database
10

Google and Samsung just launched the AI features Apple couldn’t with Siri

industry
Feb 25, 2026

Google and Samsung announced that Gemini, Google's AI assistant, will soon handle multi-step tasks on phones like ordering food or booking rides, starting with Pixel 10 and Galaxy S26 phones. This represents agentic AI features (AI that can take multiple actions toward a goal) that Apple had planned for Siri but delayed in March 2025 and hasn't yet released.

The Verge (AI)
Prev1...178179180181182...371Next