CVE-2026-123894
Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-123894 is a medium-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability. Its CVSS base score is 6.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Invalid Code Signature (T1036.001); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
Advisories
- CCCS: VMware security advisory (AV26-1185) (Nov 19)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-130200
Vulnerability Data
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).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
Affected Assets
Mitigating Controls
Control response
—
—
- 14 hardening rules · 5 OS baselines
—
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Requiring cryptographic protection mechanisms forces correct signature verification to be implemented for data protection.
Mandating integrity verification tools directly requires proper cryptographic signature checking to detect unauthorized changes.
Protecting session authenticity requires correct verification of cryptographic signatures or equivalent mechanisms.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.
Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.
Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.
Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's source reach (code review, SAST) catches the common case — missing or obviously misconfigured signature verification calls — and runtime reach (penetration testing) catches cases where unsigned or malformed data is accepted; the remainder is verification logic that is present but subtly incorrect (e.g., a verify flag set wrong, a check that accepts a null signature), which requires careful review or targeted test cases to surface.
Training technical teams on cryptographic practices (which A.6.3's education-and-training half explicitly covers) reduces signature-verification omissions where the defect is a knowledge gap or a deliberate shortcut, but most CWE-347 instances are implementation errors — wrong API, missing verify call, incorrect verification logic — that training does not reach, mirroring the A.6.3 vs CWE-598 anchor.
A.8.24 mandates approved cryptographic solutions and usage practices, which can require signature verification in code the organization writes, but the actual prevention of the code defect (calling or correctly using a verification API) depends on implementation rigor and does not reach third-party components or code that misuses approved cryptographic libraries.
A.8.28 mandates secure coding practices (standards, peer review, threat modelling, prohibition of insecure design techniques, use of vetted cryptographic components) that reduce the likelihood of improper signature verification being written, but it is a practice-based control whose effect depends on developer rigour; the weakness still arises where developers misuse verification APIs, omit checks, or use libraries that don't verify by default, leaving a nameable remainder that A.8.29 (security testing) is better positioned to catch.
A.8.30's contractual requirements for secure coding/testing (8.25-8.29) and acceptance testing lead to finding CWE-347 instances through the testing programme it mandates, but the clause itself is a process/contractual wrapper — the actual finding is performed by the controls it requires, not by A.8.30 directly.
A.8.8's reach is DISCLOSURE-based (vendor advisories, vulnerability scanning of known issues), and CWE-347 does surface as CVEs (observed examples include CVE-2002-1796, CVE-2005-2181/2182, CVE-2002-1706), so the disclosed third-party share is found; the majority of CWE-347 instances live in first-party code where developers wrote signature verification incorrectly, which A.8.8's scanning and advisory programme does not reach.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (2 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-347
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
Oracle Linux 9 (2 rules)
- V-271525 OL 9 must have GPG signature verification enabled for all software repositories. blocks CWE-347
- V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. blocks CWE-347
RHEL 7 (2 rules)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
- V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
RHEL 8 (1 rule)
- V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
RHEL 9 (1 rule)
- V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. blocks CWE-347