Affects SailPoint IdentityIQ, a widely used enterprise identity governance product; unauthenticated API/data access can cause broad data exposure and operational impact.
CVE-2026-12341
OAuth token validation flaw in SailPoint IdentityIQ allows unauthenticated API/data access
Is CVE-2026-12341 being exploited?
Not confirmed. CVE-2026-12341 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-12341?
CVE-2026-12341 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-12341?
Yes. A fix has been recorded for CVE-2026-12341. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12341 affect?
CVE-2026-12341 affects SailPoint IdentityIQ (all versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12341?
Apply vendor patch when released; restrict external access, enforce WAF, rotate/revoke tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can bypass OAuth token validation to call protected APIs, access/exfiltrate identity data, and potentially modify accounts.
Immediate action required
- affected>= 8.5 and <= 8.5p1
- affected>= 8.4 and <= 8.4p4
- affected>= 8.3 and <= 8.3p5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.