Skip to content
L4Major NewsCybersecurity & InfrastructureActiveGlobal

CVE-2026-123890: GTIG links BONESAW exploitation to vCenter, patched 19 Nov; CISA KEV listing 20 Nov with Nov 23 federal remediation due

GTIG links ARMORY CASTLE's BONESAW to active exploitation of CVE-2026-123890 in September; VMware issued patches on Nov 19; KEV listing reported Nov 20 with Nov 23 federal remediation date.

By Chronos Editorial Desk · AI-assisted

Published Last updated Original version
Urgency
L4
75
85
50
60
85

At a glance

Google GTIG reported that ARMORY CASTLE used BONESAW to exploit VMware vCenter vulnerability CVE-2026-123890 in early September 2026. VMware/Broadcom published VMSA-2026-0009 with patches on Nov 19, 2026. An aggregator reports CISA added the vulnerability to its KEV catalog on Nov 20, 2026 with a Nov 23 federal remediation due date, creating immediate patching pressure for affected organizations.

  • GTIG links ARMORY CASTLE's BONESAW to active exploitation of CVE-2026-123890 in September; VMware issued patches on Nov 19; KEV listing reported Nov 20 with Nov 23 federal remediation date.
CHRONOS Cybersecurity & Infrastructure category illustration. Illustrative only, not specific to this event.
Illustrative image, not a photograph of this event.

CHRONOS Wire · November 21 · Alert 5

What happened

A critical VMware vCenter authentication bypass, tracked as CVE-2026-123890, was patched on Nov 19, 2026. Google Threat Intelligence Group reported that the China-linked actor ARMORY CASTLE used a tool called BONESAW to exploit this vulnerability in early September 2026. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on Nov 20, 2026, with a federal remediation due date of Nov 23, 2026.

Why it matters

Public forensic reporting of active exploitation combined with vendor patches and a KEV remediation deadline requires immediate assessment and patching of vCenter deployments to prevent high‑impact compromises.

CHRONOS Bottom Line

CVE-2026-123890 is a high‑impact vCenter authentication bypass that was actively exploited in September 2026 according to Google GTIG, patched by VMware on Nov 19, 2026, and added to CISA KEV on Nov 20 with a Nov 23 federal remediation deadline.

Full detail

What changed

Google GTIG published forensic reporting linking ARMORY CASTLE and its BONESAW utility to active exploitation of CVE-2026-123890 in early September 2026. Broadcom/VMware published VMSA-2026-0009 with patches on Nov 19, 2026. CISA KEV listing was reported on Nov 20, 2026, with a Nov 23 federal remediation due date.

What is genuinely new

Google GTIG public reporting linking ARMORY CASTLE’s BONESAW utility to exploitation of CVE-2026-123890 in early September 2026, and reporting that CISA KEV listing was added on Nov 20, 2026 with a Nov 23 federal remediation date.

Detailed analysis

Google GTIG reports that ARMORY CASTLE used a Golang utility called BONESAW to exploit CVE-2026-123890 in early September 2026, enabling LMDB exfiltration, SAML STS hijacking, and creation of SSO administrator accounts. Broadcom/VMware published VMSA-2026-0009 with fixes on Nov 19, 2026. Public KEV reporting indicates CISA added the CVE to its Known Exploited Vulnerabilities catalog on Nov 20, 2026 with a Nov 23 federal remediation deadline. Public sources do not provide a verified victim count.

U.S. Impact

Current impact

Elevated

Elevated. Patches were published Nov 19, 2026 and CISA KEV reporting increases immediate remediation pressure for US federal agencies and contractors.

Potential impact

Elevated

High. CISA added CVE-2026-123890 to KEV on Nov 20, 2026 with a federal remediation date of Nov 23, 2026, obligating accelerated patching for federal agencies and increasing likelihood of rapid mitigation action across US critical infrastructure and suppliers.

Impact type
Direct
Confidence
High

U.S. Impact is an analytical assessment of the estimated current and potential effects on the United States. It is not a probability forecast.

Follow CHRONOS ALERTS

Published alerts also appear on Instagram and Threads as @chronosalerts.

Add Chronos Alerts as a preferred source on Google