CVE-2026-5712
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 · uneditedThis vulnerability impacts all versions of IdentityIQ and allows an authenticated identity that is the requestor or assignee of a work item to edit the definition of a role without having an assigned capability that would allow role editing.
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 confidenceThis is an authorization bypass vulnerability in IdentityIQ where authenticated users who are either the requestor or assignee of a work item can edit role definitions without possessing the required capability for role editing. The vulnerability stems from improper access control enforcement in the work item workflow, allowing privilege escalation through the role editing functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.3= 8.3= 8.4= 8.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Determine IdentityIQ versionCheck the IdentityIQ version via the UI (Help > About) or by inspecting the identityiq.jar/identityiq.properties file for the build.version or iiq.version propertyAffected if Running version < 8.3, 8.3, 8.4, or 8.5 (including patch versions within these releases)
-
Verify work item functionality is accessibleConfirm that authenticated users can access work items (work lists, approval items, or certification tasks) through the IdentityIQ UI or APIAffected if Work item functionality is enabled and accessible to standard users in the environment
-
Confirm role management interface is accessibleCheck if users with work item association (as requestor or assignee) can access the role definition editing interface via UI or API endpointAffected if Role editing interface is accessible without explicit capability validation for work item holders
-
Inspect access control configuration for role editsReview the IdentityIQ access policies or role editing rules in the SPML or internal access config to verify if work item association bypasses the Edit Role capability checkAffected if The access control configuration allows role definition edits based solely on work item ownership rather than requiring the Edit Role capability
The environment is affected if running IdentityIQ version 8.3, 8.4, or 8.5 (or any version below 8.3) and users can edit role definitions through work item association without possessing the Edit Role capability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.3
Apply the vendor-provided patch for IdentityIQ that enforces proper capability validation before allowing role definition edits, regardless of work item association.
IdentityIQ 8.6 or later
- Contact SailPoint support or access the customer portal to obtain the IdentityIQ 8.6 upgrade package
- Review the IdentityIQ 8.6 release notes for any configuration or compatibility requirements
- Apply the upgrade in a non-production environment first to validate functionality
- Deploy the upgrade to production following standard SailPoint upgrade procedures
- Verify that the role editing capability restrictions are properly enforced after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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