CVE-2026-10842
Ibm Websphere Application Server 8.5.0.0 – 8.5.5.31
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2026-10842 is a high-severity Authentication Bypass by Alternate Name (CWE-289) vulnerability in Ibm Websphere Application Server. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-4 (Identifier Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-51184
Vulnerability Data
IBM WebSphere Application Server 8.5, and 9.0 and IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.7 Traditional and Liberty could allow a remote attacker to bypass security constraints.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 3 OS baselines
V8.3.3V10.3.2V6.4.3
Mitigating Controls (NIST 800-53 r5) AI
Requiring unique identification and authentication of users forces the system to resolve all name variants to a single identity before access is granted.
Identifier management directly requires authorization and uniqueness checks that eliminate alternate-name aliases for the same actor or resource.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication mechanisms directly prevent name-based bypass when they enforce canonical name checks.
Proper identity management reduces alternate-name collisions but does not guarantee canonicalization inside the auth decision.
Authorization policy enforcement assumes correct identity; the weakness occurs before policy is applied.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access-control policy can mandate canonical-name checks but does not prescribe the technical implementation.
Identity-management processes can require unique, canonical identifiers, reducing alternate-name bypass risk.
Proper management of authentication credentials can include rules against duplicate or alias identities.
Access-rights provisioning can enforce canonical-name validation when granting rights.
Information-access-restriction mechanisms can implement canonical-name checks to prevent bypass.
Secure-authentication controls can require canonical identifiers and reject alternate names.
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 `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248538 OL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must have a unique name for the grub superusers account when booting into single-user mode and maintenance. prevents CWE-289
RHEL 7 (1 rule)
- V-244558 Red Hat Enterprise Linux operating systems version 7.2 or newer booted with United Extensible Firmware Interface (UEFI) must have a unique name for the grub superusers account when booting into single-user mode and maintenance. prevents CWE-289