Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify Access

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Security Verify Access (generic), IBM/Security Verify Access Container (generic), IBM/Verify Identity Access (generic), IBM/Verify Identity Access Container (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Security Verify Access, IBM/Security Verify Access Container, IBM/Verify Identity Access.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 4, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 4, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• Code injection in the CDK generator in Amazon awslabs.dynamodb-mcp-serverAlso CWE-1336
• undici vulnerable to Denial of Service via orphaned RetryHandler response bodySame generic ecosystem
• undici vulnerable to downstream response splitting via retry interceptorSame generic ecosystem
• undici vulnerable to Denial of Service via unrequested WebSocket subprotocolSame generic ecosystem
• Note Mark: Path traversal via unsanitized book/note slug in migrate export (sibling of GHSA-g49p)Same generic ecosystem
• PJSIP: SDP parser out-of-bounds write in remote payload-type map maintenanceSame generic ecosystem