CVSS 3.1
8.5 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:NCVE-2026-17290
High (8.5) in ibm api connect. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-290 Authentication Bypass by Spoofing
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-17290 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17290?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17290?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-17290 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| IBM API Connect | from 12.1.0.0 through 12.1.1.2 |
| IBM API Connect | from 10.0.8.0 through 10.0.8.12 |
Attack patterns (CAPEC)
- CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
- CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
- CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
- CAPEC-473 Signature Spoof
- CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
- CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.