Edition 2026-05-09 · read as Security
IvantiEPMMThirdZero-DayExposesJanuaryPatchGap
- Sources
- 40
- Words
- 1,189
- Read
- 6min
Topics Agentic AI AI Regulation AI Safety
◆ The signal
CVE-2026-6973 is Ivanti EPMM's third zero-day in six months and is under active exploitation. It requires admin credentials, which means January's zero-days already handed those over. Instances exposed in January and patched without credential rotation are still compromised. Separately, Anthropic's Claude Chrome extension is still exploitable post-patch via cross-extension prompt injection. No malware, no anomalous login. The SOC does not see it. The agent just follows the wrong instructions.
◆ INTELLIGENCE MAP
01 Ivanti EPMM Chained Zero-Day — January's Compromise Is Today's Backdoor
act nowCVE-2026-6973 requires admin auth — the tell that attackers from January's EPMM zero-days are cashing in footholds. This is Ivanti's 34th CISA KEV entry since 2021. Patch alone won't evict persistence; credential rotation and admin-session forensics are mandatory.
- CISA KEV deadline
- CVEs patched this cycle
- Auth required
- KEV entries since 2021
- Jan 2026Two EPMM zero-days exploited
- May 7CVE-2026-6973 patch + 4 co-fixes
- May 8CISA KEV addition
- May 10KEV remediation deadline
- May 12Canvas leak deadline (unrelated)
02 AI Agent Attack Surface Goes Live — Claude Extension, MCP GA, Braintrust
act nowThree events converged: Claude's Chrome extension remains hijackable post-patch via cross-extension prompt injection; AWS MCP Server hit GA exposing 15,000+ API operations to agents; and Braintrust's AWS breach likely leaked API keys to Cloudflare, Vercel, and Stripe. SOCs have near-zero telemetry on any of these surfaces.
- Claude patch status
- Braintrust customers
- MCP detection maturity
- Agent principal class
03 Social Engineering Cost Curve Collapses
monitorMuddyWater is running Microsoft Teams help-desk impersonation with DWAgent persistence and Chaos RaaS as false flag. Simultaneously, GPT-Realtime-2 ships 70-language voice at $0.034/min, and Seedance 2.0 delivers executive-video impersonation at $0.24/sec. The entire voice and video verification model is economically obsolete.
- GPT-Realtime-2 cost
- Seedance 2.0 cost
- Languages supported
- MuddyWater vector
- Voice clone cost (2024)5
- Voice clone cost (now)0.034
- Video fake cost (2024)3
- Video fake cost (now)0.24
04 Vendor Workforce Volatility Creates Supply-Chain Fragility
monitorCloudflare cut 1,100 staff (20%) while AI traffic surged 600%. Thousands of 'vibe-coded' apps on Replit/Lovable/Base44 are exposing corporate data with no auth. Shadow IT grew faster while the edge vendor shrank — the map of what needs watching expanded in the same week staffing at a critical dependency contracted.
- CF staff cut
- CF AI traffic surge
- Vibe-coded app exposure
- Stock impact
05 AI Regulatory Regime Hardens Into Compliance Obligations
backgroundOSTP designated adversarial distillation a national security threat. NIST signed pre-deployment evaluation pacts with Google, Microsoft, and xAI — not Anthropic. Oregon's private right of action for AI disclosure failures activates Jan 2027. Tennessee introduces Class A felony liability for developers. The AI pipeline is now regulated infrastructure.
- Oregon PRA effective
- Tennessee liability
- NIST partners
- EU Cloud Act debate
- May 2026OSTP distillation designation
- May 19DC Circuit Claude oral argument
- End MayEU Cloud Act debate begins
- Jan 2027Oregon private right of action
- 2027GUARD Act age-gating
◆ DEEP DIVES
01 Claude Chrome Extension Takeover: The Attack Your SOC Cannot See
The Exploit Class Nobody Is Detecting
LayerX has shown that Anthropic's Claude Chrome extension remains exploitable after the May 6 patch via cross-extension prompt injection. No elevated permissions required. Any co-installed extension on the same browser profile can hijack Claude's agent and exfiltrate from Google Drive, GitHub, and email, riding the user's own authorized sessions.
A SOC watching endpoint, identity, and network telemetry will not see this. The exfiltration rides the user's own authorized sessions. There is no malware. There is no anomalous login. There is an AI agent doing what it was told, by the wrong party.
This is a genuinely new detection blind spot. The traditional indicators do not fire: no malicious binary, no credential anomaly, no lateral movement. The agent calls legitimate APIs with legitimate tokens belonging to the legitimate user. The only signal is behavioral. The agent performs reads or actions the user did not request.
Converging Agent Attack Surfaces This Week
The Claude extension is not a one-off. Three other events this week establish that AI agent identity is now a first-class attack surface without first-class defenses:
- AWS MCP Server went GA, granting AI agents authenticated access to 15,000+ AWS API operations through existing developer IAM credentials, with sandboxed Python execution. A prompt injection sitting in a documentation page or a poisoned GitHub issue can invoke arbitrary AWS APIs under the developer's identity.
- Braintrust (AI observability) was breached. The API key database was likely accessed. Named customers include Cloudflare, Vercel, and Stripe. Keys held there fan out into the infrastructure stack.
- Google Cloud shipped first-class agent identity primitives, alongside AWS. Non-human agent identities are now a recognized principal class.
The Detection Architecture Gap
Surface Auth Model SOC Visibility Primary Risk Claude Chrome extension User's OAuth sessions None — looks like normal browsing Cross-extension prompt injection → Drive/GitHub/email exfil AWS MCP Server Developer IAM credentials CloudTrail (but agent indistinguishable from human) Prompt injection → arbitrary API calls Braintrust breach blast radius Stored API keys Depends on key-owner's logging Cascading access to Cloudflare/Vercel/Stripe Why This Is Different From Friday's Agent Coverage
Friday's briefing framed AI agents as a destruction risk, via the PocketOS database deletion. Today's threat is stealth exfiltration through legitimate channels. The attacker never trips an alert because the operation sits inside the trust boundary of a sanctioned tool. The blast radius is not availability. It is confidentiality, and it stays invisible until forensic reconstruction.
Action items
- Inventory Claude Chrome extension deployments via managed browser policy and disable or restrict to vetted allowlist until Anthropic ships a full fix
- Rotate all API keys issued to or stored by Braintrust; review AWS CloudTrail for anomalous access from Braintrust IP ranges over last 30 days
- Scope IAM permissions for any developer role connected to AWS MCP Server to short-lived sessions with explicit deny on destructive operations
- Stand up agent-behavior telemetry: log all MCP tool invocations and Claude extension API calls with session attribution, separate from human activity
Sources:CyberScoop · Risky.Biz · TLDR DevOps · TLDR IT · TLDR AI · Daily Dose of DS
02 Ivanti EPMM CVE-2026-6973: The January Compromise You Didn't Finish Cleaning
Why This Zero-Day Is Different
CVE-2026-6973. Ivanti EPMM. Active exploitation confirmed, listed on CISA KEV with a May 10 remediation deadline. The relevant detail is the prerequisite: authenticated admin access. That is not a mitigation. That is the fingerprint of operators who already got in through January's EPMM zero-days and are using this one to keep the access.
Treating these as independent vulnerabilities is how organizations end up getting hit a fourth time.
Multiple sources agree on the pattern. Ivanti's own advisory states that customers who rotated credentials after earlier EPMM bugs are at lower risk. Read plainly: the credentials being chained now were staged during prior incidents. This is Ivanti's 34th CISA-flagged defect since 2021.
The MDM Pivot Threat Model
MDM admin compromise is not a standard RCE. In the 2024 Stryker incident the attackers used the victim's own MDM to wipe every managed device. An EPMM admin foothold is a fleet-wide destructive-action primitive. The blast radius is every phone, tablet, and laptop enrolled.
Android ADB Adds a Second Mobility Vector
Running in parallel: CVE-2026-0073, a logic flaw in Android ADB authentication affecting every device on Android 11 or later. A mismatched key type — RSA versus Ed25519 — returns an error and still opens a remote shell. Exploitation requires reachable ADB. On a managed fleet, that number should be zero. Discovery is credited to BARGHEST, a non-profit researching mobile surveillance against human rights defenders.
Dimension Ivanti EPMM Android ADB CVE CVE-2026-6973 CVE-2026-0073 Auth required Admin (chained from January) Bypass via key mismatch Patch Available: 12.6.1.1 / 12.7.0.1 / 12.8.0.1 May 2026 Android update Exploitation Active, chaining prior compromises No confirmed wild exploitation yet Fleet impact Full MDM control of all managed devices Shell user on any ADB-exposed device The Vendor-Risk Pattern
Four sources independently reach the same conclusion. Continued reliance on Ivanti EPMM is a conscious risk-acceptance decision. The pattern across 34 KEV entries does not vary: exploitation precedes disclosure, credential material is staged early, and organizations that patch without rotating credentials find the intruder still resident. A vendor-risk review that does not model this pattern is underweighting the evidence.
Action items
- Patch Ivanti EPMM to 12.6.1.1 / 12.7.0.1 / 12.8.0.1 and rotate ALL admin credentials — including API tokens and service accounts
- Hunt EPMM admin session logs for unauthorized account creation, policy pushes, or mass device actions since January 2026
- Push May 2026 Android security update across MDM fleet and disable ADB via device policy where not strictly required
- Schedule formal Ivanti vendor-risk review: evaluate MDM/UEM alternatives or implement architectural segmentation to contain blast radius
Sources:SANS NewsBites · Risky.Biz · CyberScoop · Matt Johansen
03 MuddyWater's Teams Campaign and the $0.03/Minute Voice-AI Arms Race
Iran's Help-Desk Social Engineering Has Gone Live
The actor is MuddyWater, Iran-nexus. The vector is posing as IT support on Microsoft Teams. Operators get the victim to screen-share, harvest credentials in real time, coach the target through MFA prompts, and drop DWAgent for persistence. They then skip encryption entirely and move to pure exfiltration. The whole chain hides under a Chaos RaaS false flag to look like commodity ransomware.
The campaign is built to evade ransomware-centric detection stacks. The chain omits mass file writes, shadow-copy deletion, and encryption behaviors, which is the entire detection surface most stacks are tuned for. The signal lives at the identity layer: RMM installation on non-IT endpoints, Teams federation with external tenants, and credential reset flows initiated inside a screen-share session.
Any ransomware-centric detection stack looking for mass file writes, shadow-copy deletion, or encryption behaviors is blind to this chain.
The Economics Just Broke the Defender's Advantage
Voice and video impersonation are now priced like a phone call. The pricing moves that landed this week make that literal:
Capability Product Cost Implication Real-time voice + 70 languages GPT-Realtime-2 + Translate $0.034/min Native-quality vishing in any language, with reasoning Lip-sync video + ambient audio Seedance 2.0 (ByteDance) $0.24/sec Executive video impersonation at scale Live voice translation GPT-Realtime-Whisper $0.017/min Cross-border social engineering without accent tells Genspark's production deployment on GPT-Realtime-2 reports a 26% effective conversation rate on automated outbound calls. Roughly four calls per credential. At $0.034 per minute, a ten-minute pretext call costs $0.34. A stolen credential now costs under $1.50.
The ByteDance Wrinkle
Seedance 2.0's face and copyright filter is app-layer only, scoped to CapCut. The same model ships through BytePlus, Volcengine, Dreamina, and Higgsfield.ai without those filters. The invisible watermark is ByteDance-proprietary and cannot be independently verified. C2PA provenance is not mentioned.
Converging Signals
The Iran-nexus Teams campaign and commodity voice-AI pricing land in the same operational window. The consequence is narrow and specific: voice, accent, fluency, and security-question checks no longer discriminate attacker from executive. Help desks still relying on caller recognition, security questions, or callbacks to a caller-provided number are running obsolete controls against a state actor and a commodity market at the same time.
Action items
- Implement out-of-band verification for all help-desk credential and MFA resets: callback to HR-sourced directory number only, never the number on the call or in email
- Disable Teams external-tenant screen-share by default; alert on DWAgent, AnyDesk, and non-IT RMM tool installations on endpoints
- Commission a red-team vishing exercise using a commercial real-time voice stack within 30 days — measure helpdesk pass-through rate
- Add CapCut, BytePlus, Volcengine, Dreamina, and Higgsfield.ai to CASB/DLP high-risk classification; alert on corporate video uploads
Sources:Matt Johansen · Risky.Biz · AINews · Simplifying AI · The Batch @ DeepLearning.AI · Techpresso
◆ QUICK HITS
Update: PAN-OS CVE-2026-0300 patches confirmed for May 13–28 window; compensating controls (disable User-ID Auth Portal response pages) remain the only defense for another week
SANS NewsBites
Update: ShinyHunters claims second Canvas breach impacting ~9,000 institutions with May 12 leak deadline — Instructure has not closed the second entry point
CyberScoop
Braintrust AI observability platform breached via AWS; API keys to Cloudflare, Vercel, and Stripe likely in attacker hands — rotate any key issued to Braintrust immediately
Risky.Biz
Thousands of 'vibe-coded' apps built on Replit, Lovable, and Base44 are publicly exposing corporate data with no authentication — hunt egress logs for these domains now
StrictlyVC
Cloudflare cuts 1,100 staff (20%) while AI traffic surges 600% — re-score vendor risk, validate failover paths, and confirm named support contacts still employed
The Information AM
Jenkins threat landscape: 59% of environments carry critical vulnerabilities, 87% run end-of-life versions — any Jenkins with cloud IAM role trust is a privileged bastion for lateral movement
TLDR IT
Five malicious NuGet packages impersonating Chinese .NET libraries reached ~65,000 downloads, stealing creds from 12 browsers and 8 crypto wallets
Risky.Biz
OSTP designates adversarial distillation as national security threat with four countermeasure pillars — expect CISA-style reporting obligations for suspected extraction campaigns
a16z AI Policy Brief
React Server Components DoS patched across 5 releases (React 19.0.6/19.1.7/19.2.6, Next.js 15.5.18/16.2.6) — RSC is now a repeat-offender CVE class
React Status
Bitsight finds 1 in 5 IPs in residential proxy networks also beacon to malware C2 — treat residential proxy traffic in logs as structurally indistinguishable from botnet tunnels
Risky.Biz
GPT-5.5-Cyber shipped in limited preview to CrowdStrike and Intel with 'more permissive' malware-analysis behavior — write internal policy for offensive-AI access before someone requests it
AI Breakfast
Google DeepMind investing in training AI agents on deception, coordination, and long-horizon planning inside EVE Online — social engineering by persistent AI personas is being deliberately developed
Not Boring
◆ Bottom line
The take.
Your mobility stack has a chained zero-day that's only exploitable because January's compromise was never fully evicted (Ivanti EPMM, patch + rotate by May 10). Your developers' AI agents are now a live exfiltration channel that SOCs cannot see (Claude extension, AWS MCP, Braintrust breach). And the cost of a successful voice-impersonation attack just dropped below $1.50, while Iran is already running it against Teams. Rotate Ivanti creds today, block Claude's extension until the class of issue is fixed, and kill knowledge-based authentication at the help desk before Monday.
Frequently asked
- Why does patching Ivanti EPMM CVE-2026-6973 not fully resolve the compromise?
- Because the vulnerability requires admin credentials to exploit, attackers who used January's EPMM zero-days to steal those credentials retain access even after the patch. Ivanti's own advisory notes that only customers who rotated credentials after earlier bugs are at lower risk. Patch the binary, rotate every admin credential and API token, and hunt session logs back to January for unauthorized policy pushes or device actions.
- What makes the Claude Chrome extension exploit invisible to a traditional SOC?
- The attack rides the user's own authorized OAuth sessions to Google Drive, GitHub, and email, so there is no malware, no anomalous login, and no lateral movement to alert on. A co-installed extension injects instructions into Claude's agent, which then makes legitimate API calls with legitimate tokens. The only signal is behavioral — the agent reading or acting on data the user never requested — and most stacks have no telemetry for that.
- How should help desks adapt to commodity real-time voice cloning at $0.034 per minute?
- Treat voice, accent, and security-question recognition as defeated controls and require out-of-band verification for every credential or MFA reset. Callbacks must go to an HR-sourced directory number, never a number provided on the call or in email. A red-team vishing exercise using a commercial real-time voice stack is the fastest way to measure current help-desk pass-through rates against this threat.
- What is the blast radius of the Braintrust breach for downstream infrastructure?
- Braintrust stored API keys for named customers including Cloudflare, Vercel, and Stripe, and the key database was likely accessed. Those keys fan out into production infrastructure across multiple vendors, so anyone who issued keys to Braintrust should rotate them immediately and review CloudTrail and equivalent logs for anomalous access from Braintrust IP ranges over the past 30 days.
- Why is MuddyWater's Teams campaign invisible to ransomware-focused detection?
- The chain deliberately skips encryption, shadow-copy deletion, and mass file writes — the exact behaviors most stacks are tuned to catch — and goes straight to exfiltration under a Chaos RaaS false flag. Detection has to move to the identity layer: RMM tools like DWAgent installing on non-IT endpoints, Teams federation with external tenants, and credential resets initiated during an active screen-share session.
◆ Same day, different angle
Read this day as…
◆ Recent in security
Keep reading.
- A self-replicating supply-chain worm (Miasma) has infected 73 Microsoft-owned GitHub repos and 50+ npm packages with a Rust-based credential…
- Meta's AI chatbot was socially engineered into hijacking high-profile Instagram accounts by changing the registered email address — the firs…
- The NGINX rewrite module carries an 18-year-old pre-auth RCE disclosed today.
- Lead item is the NGINX rewrite module: an unauthenticated RCE, eighteen years old, disclosed today.
- Two pre-auth bugs dropped on the same day: an 18-year-old unauthenticated RCE in the NGINX rewrite module, and a CVSS 10.0 auth bypass in Tr…