Safeguard
Vulnerability Analysis•

CVE-2023-31003: High Root Access Flaw in IBM Verify Access

CVE-2023-31003 is a High (CVSS 8.4) local root flaw in IBM Security Verify Access up to 10.0.6.1. Apply fix pack 10.0.7 or the latest container.

Safeguard Security Team
3 min read

CVE-2023-31003 is a high severity (CVSS 8.4) improper link resolution flaw in IBM Security Verify Access, formerly Security Access Manager. A local user could obtain root access. 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. The record's wording narrows the Docker part of this entry to version 10.0.6.1, while IBM's table lists Docker 10.0.0.0 through 10.0.6.1. Use IBM's wider range. 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

  1. Identify every IBM Security Verify Access (formerly Security Access Manager) appliance and container you run, and record the version.
  2. Apply the fix IBM lists: pull the latest container tag, or install the fix pack for appliances.
  3. Treat IBM's bulletin as the source for the current fix, and check it for newer releases.

Why it matters

The record classifies this as CWE-59, improper link resolution before file access, often called link following. A privileged process opens a path, and a lower privileged user has arranged for that path to point somewhere else. The privileged process then reads or writes the wrong file.

IBM's text only says improper access controls, so the link detail comes from the weakness type in the record. The vector is local with no privileges and a high impact on confidentiality, integrity and availability, which is why the score is 8.4. The CVE is not on the CISA KEV list.

The same IBM bulletin covers many other CVEs for this product, including other local privilege and information disclosure issues. Patching for one entry closes the others in the bulletin, so do not read each CVE as a separate project. Group them under one change ticket and record the fixed version once.

Quick check

Is this remote?

No. The vector is local.

Which CWE applies?

CWE-59, improper link resolution before file access, per the record.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.