What Happened
A Russian state-supported espionage group spent months reading Western mailboxes through a then-unknown flaw in Zimbra's webmail client. The payload goes after the last 90 days of email, the organization's entire email directory, the password saved in the browser and the codes kept for two-factor recovery. Opening the message was enough to start it. The NSA, CISA and partner agencies published
Why It Matters
The article describes a Russian state-supported espionage group exploiting a zero-day stored XSS flaw (CVE-2025-66376) in Zimbra’s Classic Webmail UI to silently execute JavaScript when a crafted email is merely opened or previewed.[1][7][9] This payload exfiltrates the last 90 days of email, the organization’s email directory, browser-saved passwords, and two-factor authentication scratch/recovery codes, enabling sustained unauthorized access even after password resets.[1][2][7][9] From a RealGround perspective, this is primarily a data leakage risk: any AI agents or LLM workflows integrated with Zimbra or fed email data could inadvertently expose highly sensitive communications and credentials to a compromised mail environment, and compromised 2FA codes materially weaken identity controls protecting downstream AI systems. Practically, organizations should pair aggressive patching and account remediation with continuous AI red teaming focused on how email-sourced data and credentials flow into AI agents, testing for scenarios where an attacker controlling mailboxes can pivot into AI systems, poison inputs, or misuse exfiltrated secrets.
RealGround Analysis
This signal maps to data leakage. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.
Recommended Actions
- Restrict AI agent tool permissions and production write paths.
- Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
- Add human approval workflows for high-impact or state-changing actions.
- Run prompt injection and indirect prompt injection tests against affected workflows.
- Document the owner, control gap, and remediation deadline for this risk class.
Source
https://thehackernews.com/2026/07/russian-espionage-group-exploited.html
