Cyber Resilience

CVE-2026-5926

Crypto Weakness in Ibm Security Verify Access 10.0.0.0 – 10.0.9.1

Published
23 April 2026
Modified
13 May 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-5926 is a medium-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Ibm Security Verify Access. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-28 (Protection of Information at Rest) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 uses weaker than expected cryptographic algorithms that…

more

could allow an attacker to decrypt highly sensitive information.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Why these techniques?

Weak/broken crypto (CWE-327) directly enables decryption of sensitive data such as credentials stored or transmitted by the identity product.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-14480Same vendor: Ibm
CVE-2026-1346Same product: Ibm Security Verify Access
CVE-2026-1491Same product: Ibm Security Verify Access
CVE-2026-2862Same product: Ibm Security Verify Access
CVE-2026-1345Same product: Ibm Security Verify Access
CVE-2026-1342Same product: Ibm Security Verify Access
CVE-2026-2475Same product: Ibm Security Verify Access
CVE-2026-4101Same product: Ibm Security Verify Access
CVE-2026-1343Same product: Ibm Security Verify Access
CVE-2024-27256Same vendor: Ibm

Affected Assets

ibm
security verify access
10.0.0.0 — 10.0.9.1
ibm
security verify access container
10.0.0.0 — 10.0.9.1
ibm
verify identity access
11.0.0.0 — 11.0.2.0
ibm
verify identity access container
11.0.0.0 — 11.0.2.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-13 Cryptographic Protection
  • SC-8 Transmission Confidentiality and Integrity
  • SC-28 Protection of Information at Rest
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires implementation of approved cryptographic algorithms and protections, preventing use of weak algorithms that enable decryption of sensitive data.

prevent

Enforces cryptographic protection for transmission confidentiality/integrity, mitigating weak-algorithm exposure of sensitive information in transit.

prevent

Requires cryptographic protection of information at rest, addressing the risk of weak algorithms allowing decryption of stored sensitive data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 partial match
prevents

PR.DS-01 promotes encryption for data-at-rest but never requires strong algorithms, leaving CWE-327 fully possible; the weakness is also far broader than data-at-rest so one narrow control removes none of its total risk.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Mandating approved algorithms, cipher strength and usage standards directly stops the selection of broken or weak cryptographic primitives that attackers can exploit.

prevents

The explicit call-out of cryptography-related legal constraints (import/export, key escrow, digital-signature validity) reduces the likelihood that an organization will adopt broken or non-compliant cryptographic algorithms that violate those rules.

prevents

Access to current specialist guidance and early vulnerability alerts enables timely replacement of broken or risky cryptographic algorithms with stronger alternatives.

References