Skip to content
major vulnerability· requires attention

Affects widely-used IdentityIQ enterprise product; could disrupt IAM governance and operations.

Applications

CVE-2026-4857

8.4
High
EPSS 0.27%Patch availableApr 16, 2026

Auth users with Debug Pages rights can create IdentityIQ objects.

common questions

Is CVE-2026-4857 being exploited?

Not confirmed. CVE-2026-4857 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.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-4857?

CVE-2026-4857 is rated High with a CVSS score of 8.4. 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-4857?

Yes. A fix has been recorded for CVE-2026-4857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-4857 affect?

CVE-2026-4857 affects SailPoint IdentityIQ 8.4, 8.5 (all patch levels). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-4857?

Remove Debug Pages rights and apply latest patch (8.5p2/8.4p4+).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
SailPoint IdentityIQ 8.4, 8.5 (all patch levels)
impact

Authenticated users with Debug Pages Read Only or ViewAccessDebugPage can create new IdentityIQ objects, enabling abuse/privilege escalation.

action required

Immediate action required

affected versions
SailPoint Technologies IdentityIQ
  • affected>= 8.5 and < 8.5p2
  • affected>= 8.4 and < 8.4p4

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free