Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-11921 – Insufficiently Protected Credentials / Stale Password Reuse – IBM Verify Identity A

Be the first to know when new zero-days emerge:

Summary

CVE-2026-11921 is a critical credential-handling flaw in IBM Verify Identity Access and IBM Security Verify Access. Affected containers may fail to correctly apply management password change operations, meaning a previously set administrative password can remain valid even after it has supposedly been changed. IBM’s CVE record rates the issue 9.1 (Critical) under CVSS v3.1, reflecting a network-exploitable weakness with no privileges or user interaction required.

Technical details

  • Root cause: The containerized management interface of IBM Verify Identity Access / IBM Security Verify Access does not correctly enforce password change operations, classified as CWE-522 (Insufficiently Protected Credentials).
  • Trigger condition: An administrator (or the platform) performs a management password change on an affected container deployment; the old credential is not properly invalidated.
  • Attack vector: Network — the flaw can potentially be leveraged remotely against the exposed management interface without requiring privileges or user interaction, per the published CVSS vector.
  • Impact: High confidentiality and integrity impact. Stale or superseded management passwords may continue to grant access to the identity and access management platform, undermining credential rotation and access-revocation controls.

Affected software

  • IBM Verify Identity Access: 11.0.0 through 11.0.3 IF1
  • IBM Verify Identity Access Container: 11.0.0 through 11.0.3 IF1
  • IBM Security Verify Access: 10.0.0 through 10.0.9.2 IF1
  • IBM Security Verify Access Container: 10.0.0 through 10.0.9.2 IF1

Severity

CVSS v3.1 Base Score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to the fixed interim fix releases:
    • IBM Verify Identity Access → v11.0.3 IF2
    • IBM Verify Identity Access Container → v11.0.3 IF2 (container image)
    • IBM Security Verify Access → v10.0.9.2 IF2
    • IBM Security Verify Access Container → v10.0.9.2 IF2
  • If patching cannot occur immediately: Restrict network access to the management interfaces of Verify Identity Access / Security Verify Access to trusted administrative networks only, and treat any management password rotated prior to patching as potentially still exposed — rotate credentials again immediately after applying the fix.
  • Validation: After upgrading, confirm that previously "changed" management passwords no longer authenticate, and audit administrative access logs for use of old credentials.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge