CVE-2023-31005 is a medium severity (CVSS 6.2) improper privilege management flaw in IBM Security Verify Access, formerly Security Access Manager. A local user could escalate privileges. IBM's remedy is fix pack 10.0.7 on appliances, or the latest published container tag.
What's affected
IBM's bulletin 7106586 lists IBM Security Verify Access Appliance and Docker 10.0.0.0 through 10.0.6.1 as affected. IBM's vector shows local access with no privileges and a high confidentiality impact only. IBM's remediation is to pull the latest published container tag, and for appliances to install fix pack 10.0.7-ISS-ISVA-FP0000, which IBM lists for IBM Security Verify Access 10.0.0.0. IBM lists no workarounds or mitigations.
A later IBM bulletin (7158790) covers release 10.0.8.0. Check it as well, since it may carry newer fixes for this product line.
How to check if you're exposed
For the container, list the image tag you are running:
docker ps --format "table {{.Names}}\t{{.Image}}"
Compare the tag with the affected range. IBM's remediation for the container is to pull the latest published tag:
docker pull icr.io/isva/verify-access:TAG
Replace TAG with the latest version listed on IBM's page. For appliances, read the firmware version in the appliance management interface. This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.
What to do now
- Identify every IBM Security Verify Access (formerly Security Access Manager) appliance and container you run, and record the version.
- Apply the fix IBM lists: pull the latest container tag, or install the fix pack for appliances.
- Treat IBM's bulletin as the source for the current fix, and check it for newer releases.
Why it matters
The class is CWE-269, improper privilege management. A configuration leaves a local account with more power than intended. IBM does not say which setting is involved.
The score is 6.2 because the attacker must already be on the system and only confidentiality is affected in the vector. Even so, local flaws in a container image matter when several teams share a host. Applying the same fix as the other entries in the bulletin closes it. The CVE is not on the CISA KEV list.
Medium scores are easy to defer. A useful rule is to ask what else the same machine exposes. A local attacker on an access manager is already close to credentials and session data, so even a flaw that only raises privileges is worth closing in the next planned update.
Quick check
Why Medium?
The attack is local and only confidentiality is rated as affected.
Is it fixed by the same update as the others?
Yes. IBM's bulletin lists one fix pack and one container update for the whole set.
Sources
Last reviewed: 19 October 2026.