🛡️ CVE-2026-4101 — security-verify-access

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-4101 is classified as CWE-287: Improper Authentication. The identity of the caller is not established correctly, so an attacker can act as another user.

Affected software

CVE-2026-4101 is recorded against 4 packages.

• security-verify-access (from 10.0.0.0 up to 10.0.9.1)
• security-verify-access-container (from 10.0.0.0 up to 10.0.9.1)
• verify-identity-access (from 11.0.0.0 up to 11.0.2.0)
• verify-identity-access-container (from 11.0.0.0 up to 11.0.2.0)

Timeline and source

Published on 1 April 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.ibm.com

Other advisories for this package

security-verify-access has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2026-4938 (6.5 Medium, published 17 Jul 2026)
• CVE-2026-8861 (5.3 Medium, published 17 Jul 2026)
• CVE-2026-7364 (3.1 Low, published 17 Jul 2026)
• CVE-2026-5926 (6.5 Medium, published 23 Apr 2026)
• CVE-2026-1346 (9.3 Critical, published 8 Apr 2026)
• CVE-2026-1343 (7.2 High, published 8 Apr 2026)
• CVE-2026-1342 (8.5 High, published 8 Apr 2026)
• CVE-2026-1345 (7.3 High, published 1 Apr 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-287: Improper Authentication) in other software:

• CVE-2022-24885 (2.0 Low, published 12 Jul 2026)
• CVE-2022-39254 (8.0 High, published 7 Jul 2026)
• CVE-2012-4456 (8.0 High, published 6 Jul 2026)
• CVE-2014-0056 (published 6 Jul 2026)
• CVE-2000-1211 (8.0 High, published 2 Jul 2026)
• CVE-2000-0483 (published 2 Jul 2026)
• CVE-2022-37298 (9.8 Critical, published 29 Jun 2026)
• CVE-2019-17134 (9.5 Critical, published 29 Jun 2026)

Details

Affected Packages

References