Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/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-17278 is a critical-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Ibm Api Connect. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 48% of CVEs by exploit likelihood; 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-3 (Device Identification and Authentication) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-118671
Vulnerability Data
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to gain unauthorized access to sensitive API catalog and runtime configuration data due to improper authentication. Information supplied by the client is not sufficiently verified, which could allow a…
more
caller to appear as a trusted party.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 3 OS baselines
V6.4.3V10.4.16V11.4.3
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Proper unique identification and authentication of users directly stops spoofing-based bypass of authentication.
Device identification and authentication before connection prevents spoofing of devices to bypass auth.
Authenticator management ensures credentials cannot be easily spoofed or reused to bypass authentication.
Authentication of non-organizational users blocks external spoofing attempts against the scheme.
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.
Protecting, conveying, and verifying identity assertions specifically prevents the spoofing that enables authentication bypass.
Requiring authentication of users/services/hardware directly counters spoofing-based bypass when strong methods are used.
Proofing and binding identities reduces spoofing opportunities during enrollment but does not address runtime authentication implementation flaws.
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.
Security testing can detect spoofing vulnerabilities but does not prevent them by itself.
A.8.5 mandates strong authentication, multi-factor authentication, and log-on procedures that resist brute force and credential capture, which blocks the vast majority of spoofing-based bypass attempts; the nameable remainder is spoofing attacks that exploit implementation flaws in the authentication scheme itself (e.g., IP allowlist bypass) rather than credential or session weaknesses.
Authentication information management directly addresses credential handling that prevents spoofing.
Privileged access rights reduce attack surface but do not prevent spoofing of authentication.
A.8.20's network-level controls (firewalls, ingress filtering, network authentication per items h/i/j/n) can block some spoofing attempts at the network layer, but the application-level authentication defect that trusts spoofable values remains present and exploitable through other vectors (DNS spoofing, Host header manipulation, on-path attacks within the trusted network).
Network segregation blocks external attackers and attackers on other network domains from reaching the authentication endpoint, and makes IP spoofing harder by preventing the attacker from being on the same subnet to sniff responses, but the weakness remains present in the authentication code and is fully exploitable by anyone who can reach the endpoint (insider, compromised host on the same domain, or misconfigured gateway).
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 (1 rule)
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-290
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-290
RHEL 8 (1 rule)
- V-230492 RHEL 8 must not have the rsh-server package installed. blocks CWE-290