dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-4857

HIGH · 8.4 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IdentityIQ versions 8.4 prior to 8.4p4 and 8.5 prior to 8.5p2 contain a vulnerability where authenticated users with the Debug Pages Read Only capability or custom capabilities containing the ViewAccessDebugPage SPRight can incorrectly CREATE new IdentityIQ objects when they should only have read access. This is a privilege escalation/authorization flaw in the debug page access control.

MitigationImmediately unassign the Debug Pages Read Only capability and any custom capabilities containing the ViewAccessDebugPage SPRight from all identities and workgroups until the vendor security patches (8.4p4 or 8.5p2) can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IdentityIQ version
    Locate the IdentityIQ version information in the system (typically found in the IdentityIQ dashboard under About, or in the iiq.properties file, or in the WAR file manifest)
    Affected if The installed version is 8.4 prior to 8.4p4, or 8.5 prior to 8.5p2
  2. Check for Debug Pages Read Only capability
    Review IdentityIQ capability assignments to identify any identities or workgroups that have the Debug Pages Read Only capability assigned
    Affected if The Debug Pages Read Only capability is assigned to any user, group, or workgroup
  3. Identify custom capabilities with ViewAccessDebugPage SPRight
    Inspect IdentityIQ's SPRight definitions to find any custom capabilities that include the ViewAccessDebugPage right
    Affected if Any custom capability containing the ViewAccessDebugPage SPRight exists in the system
  4. Verify assignment of custom debug capabilities
    Review which identities have the custom capabilities containing ViewAccessDebugPage SPRight assigned to them
    Affected if Any custom capability with ViewAccessDebugPage SPRight is assigned to users or workgroups

You are affected if your IdentityIQ version is 8.4 before 8.4p4 or 8.5 before 8.5p2 AND any user has the Debug Pages Read Only capability or any custom capability containing ViewAccessDebugPage SPRight assigned to them.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately unassign the Debug Pages Read Only capability and any custom capabilities containing the ViewAccessDebugPage SPRight from all identities and workgroups until the vendor security patches (8.4p4 or 8.5p2) can be applied.

Recommended fix High confidence

IdentityIQ 8.4p4 or later; IdentityIQ 8.5p2 or later

  1. Identify all identities and workgroups that have the 'Debug Pages Read Only' capability assigned
  2. Identify any custom capabilities that contain the ViewAccessDebugPage SPRight
  3. Unassign the 'Debug Pages Read Only' capability from all identified identities and workgroups
  4. Unassign any custom capabilities that contain the ViewAccessDebugPage SPRight from all identities and workgroups
  5. Upgrade IdentityIQ 8.4 to patch level 8.4p4 or later, or upgrade IdentityIQ 8.5 to patch level 8.5p2 or later
  6. After applying the security patch, re-evaluate whether the Debug Pages Read Only capability is truly required before re-assigning it

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4857 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4857 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data