CWE · MITRE source
CWE-289Authentication Bypass by Alternate Name
The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
Last updated: 15 October 2026 20:36 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 2 framework(s): STIG oracle linux 8 1 (mostly) · STIG rhel 7 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
PR.AA-01PR.AA-03PR.AA-05IA-2Identification and Authentication (Organizational Users)
—
- 8 hardening rules · 3 OS baselines
V8.3.3V10.3.2V6.4.3
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-56511 UPD | 9.2 | 9.8 | 0.4446 | 2025-01-10 |
CVE-2021-34746 UPD | 8.5 | 9.8 | 0.1766 | 2021-09-02 |
CVE-2023-1803 UPD | 7.4 | 9.8 | 0.0077 | 2023-04-14 |
CVE-2026-24058 UPD | 7.4 | 9.8 | 0.0059 | 2026-01-22 |
CVE-2026-39858 UPD | 7.4 | 10.0 | 0.0060 | 2026-04-30 |
CVE-2026-53622 UPD | 7.4 | 10.0 | 0.0063 | 2026-06-23 |
CVE-2026-8457 UPD | 7.4 | 9.8 | 0.0070 | 2026-08-02 |
CVE-2025-13613 UPD | 7.3 | 9.8 | 0.0048 | 2025-12-10 |
CVE-2026-9701 | 7.3 | 9.8 | 0.0048 | 2026-07-08 |
CVE-2026-15980 | 7.3 | 9.8 | 0.0045 | 2026-08-30 |
CVE-2026-76183 UPD | 7.3 | 9.8 | 0.0039 | 2026-09-23 |
CVE-2025-55130 UPD | 7.2 | 9.1 | 0.0172 | 2026-01-20 |
CVE-2017-16590 UPD | 7.1 | 8.8 | 0.0333 | 2018-01-23 |
CVE-2023-20046 UPD | 6.7 | 8.8 | 0.0086 | 2023-05-09 |
CVE-2025-29266 UPD | 6.7 | 9.6 | 0.0042 | 2025-03-31 |
CVE-2026-50627 UPD | 6.5 | 9.1 | 0.0078 | 2026-06-12 |
CVE-2026-44492 UPD | 6.4 | 8.6 | 0.0078 | 2026-06-11 |
CVE-2024-55634 UPD | 6.1 | 8.1 | 0.0041 | 2024-12-10 |
CVE-2023-41890 UPD | 6.0 | 7.5 | 0.0075 | 2023-09-19 |
CVE-2026-15985 | 6.0 | 8.1 | 0.0032 | 2026-08-26 |
CVE-2026-12101 | 6.0 | 8.1 | 0.0027 | 2026-09-15 |
CVE-2023-3263 UPD | 5.9 | 7.5 | 0.0069 | 2023-08-14 |
CVE-2024-51996 UPD | 5.9 | 7.5 | 0.0062 | 2024-11-13 |
CVE-2026-10842 | 5.9 | 7.5 | 0.0053 | 2026-07-30 |
CVE-2024-2098 UPD | 5.8 | 7.5 | 0.0045 | 2024-06-13 |