01Top stories

Primary intelligence

Broadcom patches exploited critical VMware vCenter authentication bypass

Monitoring Track this incident

Broadcom issued VMSA-2026-0009 on November 19, patching five vulnerabilities across VMware vCenter, SDDC Manager and VMware Tools. The most urgent is CVE-2026-123890, a 9.8-rated VMware Directory Service authentication bypass that could let a network-reachable attacker obtain unauthorized vCenter access. Broadcom lists no workaround, making patched releases the primary defense.

The response matrix lists vCenter 8.0 U3m, 9.0.2.0200 and 9.1.1.0200 among fixed versions. Separate reporting says Google/Mandiant identified earlier exploitation by a suspected espionage actor, but the scale of compromise is not established.

Why it matters

A network-reachable management-plane authentication bypass can compromise control of an organization's virtual infrastructure.

via Broadcom advisory & VMware FAQ
Read full briefing Collapse briefing

Detailed briefing

Management-plane exposure

vCenter controls virtualization hosts, virtual machines and administrative operations, so compromise of its authentication boundary can have effects beyond a single workload. Broadcom describes the vulnerable component as VMware Directory Service and specifies network access to the affected vCenter service as the prerequisite. The advisory also includes separate SDDC Manager SQL injection, command injection and privilege-escalation issues, plus a VMware Tools SAML signature bypass. These are distinct vulnerabilities and should not be conflated with the authentication bypass.

Fixed versions and response

Broadcom's November 19 response matrix lists fixes for vCenter 8.0 and supported 9.x and Cloud Foundation branches, with special support guidance for vCenter 7 under extended support. The critical authentication bypass has no published workaround. Operators should identify affected management appliances, restrict management-network exposure where possible, apply the exact vendor patch for their branch and review authentication and administrative activity for anomalies.

Exploitation and uncertainty

Google Threat Intelligence and Mandiant reportedly observed exploitation before public disclosure and described tooling associated with a suspected espionage actor. That account increases urgency but does not establish the number of affected enterprises. The first-party advisory confirms the vulnerability and remediation, not the broader campaign attribution. A detailed independent account of affected victims and completed patch deployments remains unavailable.

Limitations & caveats

The full scope of observed exploitation and patch adoption is unknown.

European Commission confirms AI-assisted cyberattack, with some applications still offline

Investigating Track this incident

The European Commission confirmed November 19 that an AI-assisted cyber campaign detected October 22 prompted it to take several internal applications offline. Most services have been restored, but some tools remain unavailable, and the investigation is continuing. Officials confirmed misuse of AI tools without identifying the attacker or detailing how the intrusion occurred.

Politico reported possible exposure of personnel information and disruption to administrative systems, but the Commission has not corroborated those details. Its spokesperson said there was no evidence of a breach affecting Commission staff as a whole; that is not a guarantee that no individual records were exposed.

Why it matters

A major public institution confirms real service disruption and AI-assisted attacker activity, while data exposure remains under investigation.

via Reuters & Associated Press
Read full briefing Collapse briefing

Detailed briefing

Incident and reporting timeline

The Commission says it detected the campaign on October 22 and launched an investigation and preventive shutdowns. It publicly confirmed the AI-assisted nature of the campaign November 19. The reported operational disruption lasted beyond the initial detection, but officials did not provide a complete per-application outage timeline. Publication date should not be confused with the incident's October occurrence.

Operational and data impact

Several internal applications were deliberately taken offline as a protective measure, and most were subsequently restored. Reports describe possible effects on translation, payroll, timesheets and reimbursement systems, but the Commission declined to confirm those specific systems. It also said it had found no evidence of a staff-wide data breach. The unknown number of affected individuals and remaining offline tools prevent a definitive blast-radius estimate.

What AI involvement establishes

Officials described the campaign as involving AI tools, but did not publish a reproducible technical chain or identify a particular agent or model. AI-assisted vulnerability discovery does not itself demonstrate autonomous end-to-end exploitation. The investigation is open, and claims about the attacker's identity, initial access and stolen records remain unverified.

Limitations & caveats

No verified attribution, technical entry point or comprehensive breach assessment.

02Also worth knowing

Rapid scan briefs
Securityvirtualizationreview.com

CISA flags exploited LiteLLM and legacy software vulnerabilities

CISA added four vulnerabilities to its Known Exploited Vulnerabilities catalog November 18, including a LiteLLM sandbox escape, Apache Axis, REDCap and Synology flaws. Inclusion reflects evidence of exploitation, not a shared attacker or a common incident.

LiteLLM operators should review exposure of the custom-code guardrail testing endpoint and the project's patched version guidance. The affected endpoint is especially relevant to organizations centralizing access to AI models.

via Technical reporting
Read full briefing Collapse briefing

Detailed briefing

Affected surfaces

The reported LiteLLM flaw involves escaping a Python sandbox through custom guardrail testing functionality. The other entries affect older Java web services, a research-data platform and NAS software. They represent distinct technical conditions and require product-specific patch decisions.

Prioritization

A KEV entry is a stronger exploitation signal than an unexploited CVE score, but it does not provide a victim count. Teams should prioritize internet exposure and sensitive credentials, verify vendor fixes and review suspicious access logs.

Securityft.com

European AI security debate intensifies after official incident confirmation

European security officials are warning that AI tools can shorten the time required to discover and exploit vulnerabilities. The European Commission's newly confirmed October incident supplies an operational example, but published accounts do not yet establish the exact tooling, exploit chain or scope.

The broader concern is defensive response time: patching, asset inventory and change management become more difficult as attackers automate discovery. Claims that AI patching caused unrelated recent outages remain unsupported.

via Financial Times reporting & Commission confirmation via Reuters
Read full briefing Collapse briefing

Detailed briefing

What is observed

Germany's cybersecurity agency reported increasing attack pressure and faster exploitation timelines, while the European Commission confirmed misuse of AI in its own October cyber incident.

What is not established

No evidence reviewed connects the recent unrelated cloud, banking, aviation or infrastructure incidents to a common AI-driven patching failure. Security trends should not be used as a substitute for individual incident root-cause analysis.