CVE-2026-17290
8.5 HIGHPublished 2026-11-07 · Updated 2026-11-10
AI risk analysis
- Summary
- IBM API Connect versions 10.0.8.0–10.0.8.12 and 12.1.0.0–12.1.1.2 fail to fully verify cryptographic signatures on identity assertions from login providers, allowing authenticated attackers to forge identity data and create unauthorized user accounts via improper signature validation (CWE-290).
- Exploitability
- Exploitation requires valid authentication as a low-privilege user and the ability to submit forged identity tokens without proper signature verification.
- Blast radius
- Successful exploitation enables privilege escalation by allowing attackers to create new accounts with arbitrary identities, potentially gaining unauthorized access to resources or data.
- Detection
- No reliable host or network indicator is derivable from the published description.
- Prioritized remediation
- Upgrade to IBM API Connect 10.0.8.13 or 12.1.1.3, where the cryptographic signature verification flaw has been addressed.
Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.
NVD description
IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to create unauthorized user accounts due to improper verification of cryptographic signatures. Identity information from a login provider is accepted without its signature being fully verified, so forged identity data could be used to create accounts.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
Weaknesses
CWE-290
Vendors
ibm
Products
api connect
All references
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- HIGHCVE-2026-19121
- CRITICALCVE-2026-123218
- HIGHCVE-2026-16716
- CRITICALCVE-2026-17158
- HIGHCVE-2026-17228
- CRITICALCVE-2026-17298
- HIGHCVE-2026-17352
- HIGHCVE-2026-17397
Related by shared AI tags and CWE weakness class. Browse the full archive.