Skip to main content

Verify Identity Access EUVDEUVD-2026-78897

| CVE-2026-11921 CRITICAL
Insufficiently Protected Credentials (CWE-522)
2026-09-15 ibm GHSA-fjcx-78mp-2w2c
9.1
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain prior/unrotated management credential
  2. Delivery
    Reach management interface over network
  3. Exploit
    Authenticate with credential admin believed retired
  4. Execution
    Access appliance management console
  5. Impact
    Read and alter IAM/access-policy configuration

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
Exploitation Conditions

Applies to IBM Verify Identity Access / Security Verify Access in CONTAINER deployments (and the associated appliance images) where a management (administrative) password-change operation was performed - the flaw is that this change may not be applied correctly, so the exploit precondition is a management credential that was supposed to be rotated but remains active. Concretely limiting factors: an attacker must be able to reach the management interface over the network and must possess a management credential the operator believed was superseded (an old, default, or previously leaked password); environments that never changed the management password, or where rotation succeeded, are not exposed. Affected versions are VIA/SVA Container and appliance 11.0.0-11.0.3 IF001 and SVA 10.0.0-10.0.9.2 IF001; upgrading to the interim-fix release removes the condition.

Impact

The vendor CVSS of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) presents this as a critical, remotely exploitable, unauthenticated flaw, but the description and CWE-522 (Insufficiently Protected Credentials) point to a narrower reality: management password-change operations are 'not applied correctly,' meaning a rotated/changed management credential may not actually take effect and the superseded (old, possibly default or already-compromised) credential can remain valid. Exploitation therefore hinges on an attacker possessing or having previously obtained a management credential that the administrator believed was retired - this is a credential-hygiene weakness, not a spray-and-pray remote code path, which conflicts with the AC:L/PR:N framing. Corroborating low-urgency signals: EPSS is only 0.13% (3rd percentile), there is no CISA KEV listing, and no public exploit code was identified; the issue was self-reported by IBM with a patch already available. Net: despite the 9.1 label this is best treated as an important-but-not-emergency patch-and-rotate item - real risk concentrates on environments where management passwords were changed in response to a known compromise and the change silently failed, leaving stale credentials live.

Exploit ScenarioDerived

An administrator rotates the IBM Verify Identity Access / Security Verify Access management password after staff turnover or a suspected compromise, but on the affected container the change is not applied, so the previous credential silently remains valid. An attacker who still knows that old management password (a former admin, or someone who captured a default/prior credential) authenticates to the management interface and gains full read/write control over the IAM appliance configuration. No public proof-of-concept exists; the flaw is a credential-persistence logic error rather than a memory-safety bug.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 17, 2026

IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fail to apply management password-change operations, leaving a supposed-to-be-rotated administrative credential valid for network-accessible management interfaces. The flaw, tracked as CWE-522 (Insufficiently Protected Credentials), affects 11.0.0 through 11.0.3 Interim Fix 001 and the 10.0.0 through 10.0.9.2 Interim Fix 001 streams, with a high confidentiality and integrity impact on the affected management plane. Vendor-rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) presents this as trivially unauthenticated, and our assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms the high confidentiality and integrity impact but applies a higher attack complexity because practical exploitation requires reaching the management interface and possessing an old, default, or previously leaked management credential that the operator believed had been superseded; no public exploit has been identified at time of analysis and EPSS is negligible at 0.13% (3rd percentile), and IBM has released a patch.

RemediationAI

IBM has released a patch; apply the current vendor-supplied interim fix for your release stream (the 11.0.x and 10.0.x lines listed above) using the instructions and download links in the IBM advisory at https://www.ibm.com/support/pages/node/7286188, and treat any deployment at or below 11.0.3 Interim Fix 001 or 10.0.9.2 Interim Fix 001 as affected. Because the defect is that a rotation silently does not take effect, patching alone is not sufficient assurance: after upgrading, re-authenticate with the intended current management credential and positively confirm that the superseded password is rejected, and re-run the password change after the upgrade rather than assuming the pre-upgrade change was honored. If you cannot patch immediately, the most effective compensating control is to restrict network reachability to the management interface to a trusted administrative network or bastion (the trade-off is loss of remote manageability and a need to route all admin traffic through the jump host), and to rotate management credentials by rebuilding or reinitializing the container from configuration with the new secret injected at deployment time rather than through the in-product change flow (trade-off: brief service interruption and potential loss of in-place runtime settings). Additionally, audit for any instance where a default or previously leaked management password may still be live, and invalidate those credentials externally where the product supports an out-of-band reset. Note that these are compensating measures only; the vendor patch is the definitive fix, and an unpatched instance with an already-rotated-looking but still-valid administrative credential remains exposed to an attacker who has obtained that old secret.

Affected VersionsENISA

Verify Identity Access Container 11.0.0 ≤11.0.3 Interim Fix 001
Verify Identity Access 11.0.0 ≤11.0.3 Interim Fix 001
Security Verify Access Container 10.0.0 ≤10.0.9.2 Interim Fix 001
Security Verify Access 10.0.0 ≤10.0.9.2 Interim Fix 001

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability sits in the credential-management subsystem of IBM Verify Identity Access and IBM Security Verify Access, specifically in their container images and appliance builds (CPE coverage spans ibm:verify_identity_access, ibm:security_verify_access, and the *_container variants). The underlying class is CWE-522, Insufficiently Protected Credentials: the software accepts a management password change but does not consistently persist or enforce it across the deployment, so the previous administrative secret continues to authenticate. This is a state-consistency defect rather than a memory-safety or injection bug, which is why the vendor's flat AV:N/AC:L/PR:N rating overstates the ease of attack relative to the described behavior. Because the affected component is the management/administrative plane of an identity and access management product, a stale but valid administrative credential grants high confidentiality and integrity impact over realm configuration, policy, and federation data, though availability is unaffected (A:N). Containerized deployments are of particular concern because the credential state may be replicated or cached separately from the configuration that the operator edits, so an apparently successful rotation can be a no-op on the running instance.

Know when Verify Identity Access gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.4 HIGH

Network-reachable management interface with no working auth barrier once rotation fails, but AC:H because the attacker must possess a specific superseded management credential; full management C:H/I:H, no availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

3
CVSS changed
Sep 17, 2026 - 17:22 NVD
9.1 (CRITICAL)
CVE Published
Sep 15, 2026 - 17:27 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 15, 2026 - 17:27 cve.org
CRITICAL 9.1

DescriptionCVE.org

IBM Verify Identity Access containers may not apply management password change operations correctly.

Executive ViewAI

Why It Matters

IBM Verify Identity Access container and appliance deployments in the affected 10.x and 11.x streams may leave privileged management credentials active after administrators believe they have been rotated. This undermines a core identity-governance control and can give an attacker with an old, default, or previously leaked credential a path into the management plane, creating risk to enterprise authentication and administrative integrity. Leadership should prioritize remediation because the flaw affects a critical access-control function and a vendor patch is available per advisory; no public exploit identified at time of analysis.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
Enterprise IAM/reverse-proxy appliance, common in large orgs but not universal
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-78401 CRITICAL
9.8 Oct 08

Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity A

CVE-2026-78406 CRITICAL
9.8 Oct 08

Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 1

CVE-2025-36087 CRITICAL
9.8 Oct 13

Hard-coded credentials in IBM Security Verify Access 10.0.0 through 10.0.9 and 11.0.0, and in Verify Identity Access Con

CVE-2026-11928 CRITICAL
9.8 Sep 15

An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus bot

CVE-2026-4101 CRITICAL
9.8 Apr 01

Authentication bypass in IBM Verify Identity Access and IBM Security Verify Access (versions 10.0-10.0.9.1 and 11.0-11.0

CVE-2025-36356 CRITICAL
9.3 Oct 06

Local privilege escalation in IBM Security Verify Access and Verify Identity Access 10.0.x/11.0.x allows an authenticate

CVE-2026-16916 HIGH
8.8 Oct 08

Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.

CVE-2026-19482 HIGH
8.8 Oct 08

Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 thro

CVE-2026-18740 HIGH
8.8 Oct 08

Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0

CVE-2026-78388 HIGH
8.8 Oct 08

Cross-site request forgery in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 throu

CVE-2026-12004 HIGH
8.7 Aug 12

Format string injection in IBM Security Verify Access (10.0-10.0.9.2) and IBM Verify Identity Access (11.0-11.0.3, inclu

CVE-2025-36355 HIGH
8.5 Oct 06

Security Verify Access and its Docker deployment can be induced to execute malicious scripts sourced from outside the pr

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy