CVE-2023-32327 is a high severity XML external entity (XXE) flaw, scored 7.1, in IBM Security Verify Access appliance and Docker 10.0.0.0 through 10.0.6.1. A remote attacker with a low privilege account could expose sensitive information or use up memory. IBM lists fix pack 10.0.7-ISS-ISVA-FP0000.
What's affected
IBM says the Security Access Manager Container, meaning the Verify Access appliance and the Verify Access Docker image from 10.0.0.0 through 10.0.6.1, is vulnerable to XML external entity injection when processing XML data, and a remote attacker could expose sensitive information or consume memory resources. The weakness is CWE-611 (XML external entity reference). The record is dated 2024-02-03, scored 7.1 with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L. IBM tracks it as X-Force ID 254783.
IBM's bulletin lists one remedy for every issue in it: IBM Security Verify Access 10.0.0.0 through 10.0.6.1 should move to fix pack 10.0.7-ISS-ISVA-FP0000. For the Docker container, IBM says to pull the latest published tag of icr.io/isva/verify-access. The bulletin lists no workarounds or mitigations. Its initial publication date is 09 Jan 2024.
The IBM bulletin and the NVD record agree on the score and the affected range, 10.0.0.0 through 10.0.6.1. IBM's bulletin lists the vector with CVSS 3.0 where the record uses 3.1, and the values match.
No source says this flaw is exploited in the wild, and it is not in the CISA Known Exploited Vulnerabilities catalog.
How to check if you're exposed
For the appliance, open the administration console and read the firmware or fix pack level, then compare it with 10.0.7-ISS-ISVA-FP0000. Anything from 10.0.0.0 through 10.0.6.1 is in the affected range.
For containers, list the image tags you run:
docker images icr.io/isva/verify-access
Compare each tag with IBM's latest published tag. Also check Kubernetes manifests and compose files for pinned old tags, since a pinned tag keeps running the old code after a new one is published.
Include test and disaster recovery copies. Identity systems are often cloned for staging and then forgotten.
What to do now
- Inventory every IBM Security Verify Access appliance and container, with versions.
- Plan the move to 10.0.7-ISS-ISVA-FP0000 for appliances and the latest published tag for containers.
- Snapshot or back up configuration first. Access management is on the login path for other systems, so schedule a maintenance window.
- Restrict network access to management interfaces to an admin network.
- After updating, confirm the version in the console and record the change.
Why it matters
CWE-611 happens when an XML parser is allowed to resolve external references that the document itself names. A crafted document can then make the server read local files or contact other systems, and a document that expands into huge data can use up memory. The usual defence is to turn external entity processing off in the parser.
The impact numbers in the vector are high for confidentiality, none for integrity and low for availability, which matches that pattern: data exposure first, resource use second. The attacker needs a low privilege account and no user interaction. For an access management product, whatever files the process can read may include configuration data, so patch promptly. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect commercial appliances or enterprise suites, so those need a vendor driven inventory.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
What does XXE let an attacker do?
Per IBM, expose sensitive information or consume memory resources. The score is 7.1 with high confidentiality impact.
Is a workaround available?
IBM lists none. Update to fix pack 10.0.7-ISS-ISVA-FP0000, or the latest container tag.
Sources
- IBM security bulletin: multiple vulnerabilities in IBM Security Verify Access
- IBM X-Force Exchange entry (page loads by script, text not readable)
Last reviewed: 19 October 2026.