dbcve.org
Security Verify AccessApplication · Ibm

CVE-2026-1343

HIGH · 7.2 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to after 11.0.2.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
IBM 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 allows an attacker to contact internal authentication endpoints which are protected by the Reverse Proxy.

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 · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability where the reverse proxy protection in IBM Verify Identity Access and IBM Security Verify Access is being bypassed, allowing attackers to directly access internal authentication endpoints that should be protected by the reverse proxy.

MitigationApply vendor patches for the affected versions (11.0 through 11.0.2 for v11, 10.0 through 10.0.9.1 for v10) and review reverse proxy configuration to ensure internal authentication endpoints cannot be directly accessed.

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
Security Verify AccessApplication
Affected:>= 10.0.0, <= 10.0.9.1
Security Verify Access ContainerApplication
Affected:>= 10.0.0.0, <= 10.0.9.1
Verify Identity AccessApplication
Affected:>= 11.0.0.0, <= 11.0.2.0
Verify Identity Access ContainerApplication
Affected:>= 11.0.0.0, <= 11.0.2.0

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product version
    Use the product's administrative interface or run the product's version command to determine the exact installed version of IBM Security Verify Access or IBM Verify Identity Access (container or non-container)
    Affected if The installed version falls within 10.0.0 to 10.0.9.1 for Security Verify Access, or 11.0.0.0 to 11.0.2.0 for Verify Identity Access
  2. Confirm reverse proxy configuration is in use
    Review the product configuration to verify that reverse proxy protection is enabled and configured for the authentication endpoints
    Affected if Reverse proxy is configured and the product version is within the affected range
  3. Check network exposure of internal endpoints
    Test access to internal authentication endpoints from an untrusted network perspective to determine if they are directly accessible without going through the reverse proxy
    Affected if Internal authentication endpoints are reachable directly without reverse proxy authentication and the product version is within the affected range

You are affected if your installed version falls within the listed ranges AND reverse proxy protection is in use, as the vulnerability allows bypassing that protection to access internal authentication endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.0.2.0
Interim mitigation

Apply vendor patches for the affected versions (11.0 through 11.0.2 for v11, 10.0 through 10.0.9.1 for v10) and review reverse proxy configuration to ensure internal authentication endpoints cannot be directly accessed.

Recommended fix Moderate confidence

IBM Security Verify Access 10.0.10+ or IBM Verify Identity Access 11.0.3+ (or latest available stable release)

  1. 1. Identify the current installed version of IBM Security Verify Access or IBM Verify Identity Access using the product's administration console or command-line interface
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up all current configuration files, certificates, and user data according to IBM's backup documentation
  4. 4. Download the latest available version of IBM Security Verify Access (10.0.10 or later) or IBM Verify Identity Access (11.0.3 or later) from IBM Fix Central or the IBM entitlement website
  5. 5. Follow IBM's official installation and upgrade documentation for your specific deployment type (container or traditional)
  6. 6. After upgrade, verify that the SSRF vulnerability is resolved by testing that internal endpoints are no longer accessible through the reverse proxy
  7. 7. Validate that all existing authentication policies and reverse proxy configurations work correctly post-upgrade
Caveat Review IBM's release notes for breaking changes between your current version and the target version; major version upgrades may require configuration migration or compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Verify Access Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1343 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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