VMware Tools signature verification bypass in SAML token handling
- Exploited
- No known exploitation
- Fix
- Fixed in 13.1.5.0, 12.5.5
- Who is exposed
- Not reported
Summary
VMware Tools for Windows contains a SAML token signature bypass flaw. An attacker who already has high-privilege access to the local machine can exploit it, and no user interaction is needed.
Written by a model
Original description
VMware Tools for Windows contains a SAML token signature bypass vulnerability. Affected versions: 13.x.x.x (fixed in 13.1.5.0); 12.3.x (fixed in 12.5.5).
What to do
Upgrade to a fixed version: 13.1.5.0, 12.5.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123894 (VMware Tools SAML Token Signature Bypass vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123894 (entry last updated 2026-11-20):
Affected:
- VMware VMware Tools: from 13.x.x.x, fixed in 13.1.5.0; from 12.3.x, fixed in 12.5.5
Fixed versions: 13.1.5.0, 12.5.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123894 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123894 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123894
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123894"}.Affected versions
- VMware VMware ToolsFrom 13.x.x.x · fixed in 13.1.5.0; From 12.3.x · fixed in 12.5.5
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach14/20Affects VMware (an enterprise product or network appliance)
- Severity7.7/10CVSS 6.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-123894 |
| Record | NVD · CVE-2026-123894 |
| Other links 1 | |
| Link | support.broadcom.com · web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495 |
Questions about CVE-2026-123894
Is CVE-2026-123894 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-123894?
VMware Tools: from 13.x.x.x before 13.1.5.0; from 12.3.x before 12.5.5.
Source: cve.now feed data
How do I fix CVE-2026-123894?
Upgrade to a fixed version: 13.1.5.0, 12.5.5.
Source: cve.now feed data
Related
- CVE-2025-41244VMSA-2025-0015: VMware Aria Operations and VMware Tools updates address multiple vulnerabilities (CVE-2025-41244,CVE-2025-41245, CVE-2025-41246)
- CVE-2025-41246Improper authorisation vulnerability
- CVE-2019-5522VMware Tools for Windows update addresses an out of bounds read vulnerability in vm3dmp driver which is installed with vmtools in Windows…
- CVE-2020-3941The repair operation of VMware Tools for Windows 10.x.y has a race condition which may allow for privilege escalation in the Virtual…
- CVE-2018-6969VMware Tools (10.x and prior before 10.3.0) contains an out-of-bounds read vulnerability in HGFS.
- CVE-2015-5191VMware Tools prior to 10.0.9 contains multiple file system races in libDeployPkg, related to the use of hard-coded paths under /tmp.
No corrections so far. Something wrong on this page? Report an error.