CVE-2023-30998 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 because of improper access controls. IBM's bulletin points to release 10.0.8.0 and fix pack 10.0.8-ISS-ISVA-FP0000.
What's affected
The NVD record lists IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1. IBM's bulletin 7158790 says the product addressed multiple vulnerabilities in release 10.0.8.0, lists fix 10.0.8-ISS-ISVA-FP0000 for appliance versions 10.0.0.0 through 10.0.7.0, and tells container users to pull the latest published tag.
Source conflict: the record gives 7.8, IBM's bulletin gives 8.4 with the same vector as the sibling CVE-2023-30997. Both are High.
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
This entry has the same description as CVE-2023-30997, with a different IBM X-Force ID, 254649 instead of 254638. IBM files them as separate vulnerabilities, so both are listed. The class is CWE-250, execution with unnecessary privileges.
When two entries share wording, defenders sometimes assume one fix covers a duplicate. In this case IBM's bulletin lists both under the same fix, so one update closes both. Keep the pair together in your tracker so neither is marked done by mistake. The CVE is not on the CISA KEV list.
Quick check
Is this a duplicate of CVE-2023-30997?
IBM tracks it separately under a different X-Force ID, but the same release addresses both.
Does a workaround exist?
IBM lists none.
Sources
Last reviewed: 19 October 2026.