CVE-2023-30997 is a high severity flaw (CVSS 8.4 per IBM, 7.8 in the NVD record) in IBM Security Verify Access, formerly IBM Security Access Manager. A local user could obtain root access in the container because of improper access controls. IBM's bulletin points to the 10.0.8.0 release and fix pack 10.0.8-ISS-ISVA-FP0000.
What's affected
The NVD record and IBM both list IBM Security Verify Access Docker 10.0.0.0 through 10.0.7.1. IBM's bulletin 7158790 says the issues were addressed in release 10.0.8.0. For appliances the bulletin lists fix 10.0.8-ISS-ISVA-FP0000 for versions 10.0.0.0 through 10.0.7.0. For the container, IBM says to pull the latest published image tag.
Source conflict: the NVD record scores this 7.8, while IBM's bulletin gives a CVSS base score of 8.4 with vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Both fall in the High band. IBM also notes the affected range table for the appliance stops at 10.0.7.0, while the Docker range in the same bulletin runs to 10.0.7.1.
IBM says there are no workarounds or mitigations, so the fix pack and container update are the only remedy listed.
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
IBM maps this to CWE-250, execution with unnecessary privileges. Software that runs with more rights than it needs turns any small local foothold into a larger one. In a container it means a process that should be confined is able to act as root. IBM's description is brief, so the bulletin gives no mechanism beyond improper access controls.
The attack is local, so an attacker needs a way onto the system first. That keeps the real world risk lower than the score suggests, but multi tenant hosts and shared admin access change the picture. The CVE is not on the CISA KEV list. A sibling entry, CVE-2023-30998, uses the same description with a different X-Force ID.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why do the scores differ?
The record says 7.8 and IBM's bulletin says 8.4. Both are High, and IBM's own figure is the one to cite.
How do I update the container?
Pull the latest published tag from icr.io/isva/verify-access and redeploy.
Sources
Last reviewed: 19 October 2026.