CVE-2026-1345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow an unauthenticated user to execute arbitrary commands as lower user privileges on the system due to improper validation of user supplied input.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Verify Identity Access and Security Verify Access contain a command injection vulnerability due to improper validation of user-supplied input. Unauthenticated attackers can execute arbitrary commands on the underlying system with lower-privileged user access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0.0, <= 10.0.9.1>= 10.0.0.0, <= 10.0.9.1>= 11.0.0.0, <= 11.0.2.0>= 11.0.0.0, <= 11.0.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Security Verify Access versionRun the command 'docker ps' for container deployments or check the product version via the admin console or CLI tool. For non-container installations, use 'iamVerifyAccess --version' or check the /opt/ibm/verifyaccess directory for version files.Affected if The installed version falls within 10.0.0.0 to 10.0.9.1 OR 11.0.0.0 to 11.0.2.0.
-
Determine deployment typeCheck whether the deployment is container-based (IBM Security Verify Access Container or IBM Verify Identity Access Container) or traditional installation. Inspect running containers with 'docker ps' or check system services with 'systemctl list-units | grep verify'.Affected if The deployment uses any affected container or non-container version listed in the affected ranges.
-
Verify network exposure of admin interfacesCheck listening network ports and exposed interfaces. Run 'netstat -tlnp' or 'ss -tlnp' to list all listening services. Inspect firewall rules with 'iptables -L' or 'ufw status' to determine if the admin ports are externally accessible.Affected if The admin or management interface (typically ports 443, 9443, or custom Verify Access ports) is bound to a public or unrestricted network interface and reachable from untrusted networks.
-
Inspect authentication configurationReview the Verify Access configuration file (typically ivmgrd.conf or webseald.conf in /opt/ibm/verifyaccess) to confirm whether unauthenticated or lower-privileged user access is permitted on the management interfaces.Affected if Unauthenticated access is allowed or the default authentication policy permits lower-privileged user sessions without restriction.
The environment is affected if the installed IBM Security Verify Access or IBM Verify Identity Access version falls within 10.0.0.0-10.0.9.1 or 11.0.0.0-11.0.2.0 AND the admin interface is network-accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied patches for the affected versions (11.0-11.0.2 for v11, 10.0-10.0.9.1 for v10). As a temporary mitigation, restrict network access to the affected interfaces and implement strict input validation on all user-facing inputs.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data