# CVE-2026-4857: SailPoint IdentityIQ Debug UI Incorrect Authorization

> Authenticated users with read-only debug capabilities can incorrectly create new IdentityIQ objects, requiring patching or capability removal.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-vcp6-gxf9-8g4m

## What is CVE-2026-4857?

CVE-2026-4857 is a high-severity missing authorization vulnerability in SailPoint Technologies IdentityIQ, published on 15 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

IdentityIQ 8.5, all
IdentityIQ 8.5 patch levels prior to 8.5p2, IdentityIQ 8.4, and all IdentityIQ
8.4 patch levels prior to 8.4p4 allow authenticated users assigned the Debug
Pages Read Only capability or any custom capability with the ViewAccessDebugPage
SPRight to incorrectly create new IdentityIQ objects.  Until a remediating security fix or patches
containing this security fix are installed, the Debug Pages Read Only
capability and any custom capabilities that contain the ViewAccessDebugPage
SPRight should be unassigned from all identities and workgroups.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-4857?


## How do I fix CVE-2026-4857?

No fix has been published for CVE-2026-4857 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4857 being exploited?

There is no known exploitation of CVE-2026-4857 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4857 and fix it if it is affected.

What it is: CVE-2026-4857 is a high-severity missing authorization vulnerability in SailPoint Technologies IdentityIQ, published on 15 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4857 in the wild and no public exploit code.

Affected product: SailPoint Technologies IdentityIQ. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4857/ (Markdown: https://insights.sbomify.com/CVE-2026-4857/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4857
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4857
- OSV: https://osv.dev/vulnerability/CVE-2026-4857

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4857/
Summaries are generated and may contain mistakes; the official description above is the record.