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]
6,423
[LAST_24H]
7
[LAST_7D]
166
Daily BriefingFriday, August 14, 2026
>

Critical RCE in Cortex MCP Server: CVE-2026-49986 affects the Cortex MCP server (a tool enabling AI assistants like Claude to access persistent memory across projects) before version 3.17.1, allowing arbitrary Python code execution when an attacker plants malicious files in a repository and the `open_visualization` tool is invoked. The vulnerability stems from inadequate validation of project directories set by Claude Code, enabling attackers to run commands with user privileges.

>

Cyera Acquires Oasis Security for $1 Billion to Unify AI Agent Controls: Cyera's acquisition of Oasis Security combines data security and identity management into a unified control system for AI agents (autonomous software programs), shifting from fixed permission roles to context-aware access based on business needs.

Latest Intel

page 115/643
VIEW ALL
01

Enforce least-privilege authorization in multi-agent AI chains using Cedar

securitysafety
Critical This Week5 issues
critical

CVE-2026-49986: The Cortex MCP server (`neuro-cortex-memory`), a cross-platform persistent memory MCP, prior to version 3.17.1 treats th

CVE-2026-49986NVD/CVE DatabaseAug 14, 2026
Aug 14, 2026
>

OpenAI Faces Executive Exodus Ahead of IPO: OpenAI is experiencing significant departures of senior leadership, including Chief Revenue Officer Denise Dresser and Operating Chief Brad Lightcap, as the company prepares for its initial public offering. Industry observers view the exits as a potential warning sign that could undermine investor confidence amid intensifying competition from Google and Anthropic.

>

Google Enables Watermark Removal for Gemini-Generated Media: Google now allows users to disable visible watermarks on AI-generated images, videos, and music in Gemini and Flow, though invisible SynthID watermarks and C2PA metadata (hidden markers tracking AI-generated content) remain embedded in all outputs.

Jul 6, 2026

When multiple AI agents work together and delegate tasks to each other, an agent might gain more permissions than the original user intended, even with standard access controls in place. This post explains how to prevent this using Cedar, an open source authorization policy language, which enforces permissions at three levels: checking if an agent can use a tool, checking if one agent can delegate to another agent, and verifying the original human user still has permission for the entire chain of delegated tasks.

Fix: The source provides a reference implementation using a three-layer Cedar policy model deployed on AWS. The solution involves: (1) authenticating the user through an OIDC-compliant identity provider (Amazon Cognito with MFA) to obtain a signed JWT; (2) filtering requests through AWS WAF with CommonRuleSet, SQLiRuleSet, rate limiting, and body size constraints; (3) verifying JWT signatures via Amazon API Gateway; (4) using an MCP adapter Lambda function to extract verified claims from the token and map them to Cedar context attributes (role, MFA status, user ID, session ID, and authentication method); (5) cryptographically signing the user context with HMAC-SHA256 to prevent tampering; and (6) evaluating authorization through three sequential Cedar policy layers that check agent-to-tool trust scores and lifecycle stage, agent-to-agent delegation hop counts and task capabilities, and originating user role and MFA status.

AWS Security Blog
02

JadePuffer: The First Complete LLM-Driven Ransomware Attack

security
Jul 6, 2026

A malicious actor used an agentic threat actor (an AI system designed to perform tasks autonomously) to exploit a vulnerability in Langflow (an open-source platform for building AI applications) and conducted a complete ransomware attack (malware that encrypts data and demands payment for its return). The attack resulted in stolen data from a production database and encrypted systems across the targeted infrastructure.

Dark Reading
03

The agentic blind spots in your zero trust program

securitypolicy
Jul 6, 2026

AI agents (software systems that can independently perform tasks) are creating security challenges for organizations because they lack human judgment and can be created and destroyed rapidly, breaking traditional zero trust models (security approaches where all access requests are verified, not automatically trusted). Many organizations are responding by giving AI agents overly broad access permissions instead of redesigning their security systems, which has already caused serious incidents like AI agents accidentally deleting production databases (live data systems).

CSO Online
04

Identity: The operational control plane for agentic AI

securitypolicy
Jul 6, 2026

Traditional security controls like static passwords and fixed permissions don't work well for agentic AI (autonomous AI systems that operate independently and make decisions). Organizations need new approaches to manage agentic identity (how AI agents prove who they are), control what resources agents can access, handle secrets (like passwords and API keys) that agents use, and ensure permissions get restricted as workflows move between agents.

CSO Online
05

Operationalizing Agentic AI: from assisted to autonomous

securitypolicy
Jul 6, 2026

As AI tools move from being used as assistants (where humans direct each action) to autonomous agents and operators (where AI acts on its own), organizations are not updating their security and governance practices to match this increased risk. The article explains that when humans stay close to AI interactions, risks like accidentally sharing API keys or credentials can be managed with existing controls, but autonomous AI agents need stronger identity management, access controls, and auditability since humans are no longer in the loop to catch mistakes.

CSO Online
06

⚡ Weekly Recap: Proxy Botnets, Browser Ransomware, AI Agent Tricks, Fake PoC Malware and More

security
Jul 6, 2026

This week's security recap highlights how trust placed too early in systems created widespread vulnerabilities. Key incidents include Google disrupting the NetNut residential proxy botnet (a network of compromised home devices like smart TVs used to hide malicious traffic) affecting at least 2 million devices, WhatsApp introducing usernames to protect privacy but raising impersonation concerns, and security researchers being tricked into running malicious code hidden in fake proof-of-concept repositories on GitHub that deliver ChocoPoC (a trojan capable of stealing passwords and browser data).

Fix: For the NetNut botnet: Google disabled Google accounts used by NetNut for command-and-control, updated Google Play Protect, and disabled applications known to incorporate NetNut SDKs. For WhatsApp username impersonation: Meta reserves usernames for public figures, government entities, and some of their variations so that only legitimate users can claim them. For ChocoPoC malware in fake PoC repos: N/A -- no mitigation discussed in source.

The Hacker News
07

This AI agent autonomously hacked a network, adapted on the fly, and demanded a ransom

securityresearch
Jul 6, 2026

Researchers documented JadePuffer, an autonomous AI agent that conducted a complete ransomware attack by exploiting a vulnerability in a Langflow server, then adapted its tactics in real-time to breach a production database and demand a ransom. What made this attack notable was not the individual hacking techniques used, but the AI's ability to make operational decisions on its own, diagnose failures, and generate corrected attack code without human guidance. An independent security researcher noted this represents an evolution in how attacks are executed rather than a completely new technique, with the biggest concern being the AI agent's ability to quickly change tactics if defenses block it.

CSO Online
08

Prompt Injection Attacks Trick AI Agents Into Making Crypto Payments

security
Jul 6, 2026

Threat actors are using prompt injection attacks (tricking an AI by hiding instructions in its input) embedded in malicious websites and search results to trick AI agents into making cryptocurrency payments or trusting fake platforms. Researchers at Zscaler found two campaigns: one hiding payment instructions in a fake Python library website using SEO poisoning (manipulating search rankings with keyword-stuffed content), and another impersonating DeBank, a cryptocurrency platform. When tested on 26 different language models, four were successfully tricked into making payments, while two misidentified the fraudulent website as legitimate.

SecurityWeek
09

CVE-2026-44934: A information disclosure when DEBUG loglevel is set in SUSE Rancher AI Agent 1.0 before 1.0.2 could leak API keys or LLM

security
Jul 6, 2026

When DEBUG loglevel (a setting that outputs detailed program information for troubleshooting) is enabled in SUSE Rancher AI Agent versions before 1.0.2, sensitive data like API keys (credentials for accessing external services) and LLM response text can be written to logfiles where local attackers (people with access to the same computer) could find and misuse them. This is rated as HIGH severity with a CVSS score (a 0-10 rating of how severe a vulnerability is) of 7.0.

Fix: Update SUSE Rancher AI Agent to version 1.0.2 or later.

NVD/CVE Database
10

AI isn’t closing the skills gap — it’s exposing the validation gap

securitypolicy
Jul 6, 2026

The cybersecurity industry faces a 'validation gap' rather than a true skills gap, meaning the problem isn't that skilled people don't exist but that we can't verify who is actually ready for real-world security work. Traditional training like courses and certifications can't keep pace with rapidly evolving threats from AI and attacker tactics, so security professionals need continuous hands-on experience with their organization's actual systems and attack scenarios, not just theoretical knowledge.

CSO Online
Prev1...113114115116117...643Next
critical

CVE-2026-19297: IBM Langflow OSS 1.0.0 through 1.9.6 could allow a remote attacker to obtain unauthorized access to user accounts due to

CVE-2026-19297NVD/CVE DatabaseAug 13, 2026
Aug 13, 2026
critical

CVE-2026-73656: Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.6, POST /api/v1

CVE-2026-73656NVD/CVE DatabaseAug 13, 2026
Aug 13, 2026
critical

CVE-2026-73487: Flowise before 3.1.3 contains a regex-based Python code validator bypass in CSV and Airtable Agent nodes that allows una

CVE-2026-73487NVD/CVE DatabaseAug 13, 2026
Aug 13, 2026
critical

CVE-2026-73485: Flowise before 3.1.3 contains a code injection vulnerability in the Airtable Agent node that allows unauthenticated atta

CVE-2026-73485NVD/CVE DatabaseAug 13, 2026
Aug 13, 2026