dbcve.org
Security Verify AccessApplication · Ibm

CVE-2026-2862

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 11.0.2.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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 IBM Security Verify could allow a remote attacker to access sensitive information due to an inconsistent interpretation of an HTTP request by a 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 · high confidence

This is an HTTP request smuggling vulnerability where a reverse proxy and the backend server interpret HTTP requests inconsistently, allowing an attacker to bypass security controls and access sensitive information. The attacker crafts malformed HTTP requests that are interpreted differently by the reverse proxy versus the backend, potentially gaining unauthorized access to protected resources.

MitigationConfigure the reverse proxy to strictly validate and normalize incoming HTTP requests, ensuring consistent parsing between the proxy and backend. Apply vendor-provided patches for IBM Security Verify Access and ensure reverse proxy configurations are aligned with backend server expectations.

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.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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 IBM Security Verify Access version
    Run 'rpm -q isam' or 'dpkg -l | grep -i verify' or check /opt/ibm/isam/bin/version.sh. For container images, run 'docker inspect <image> | grep -i version' or check labels.
    Affected if Version falls within 10.0.0.0 to 10.0.9.1 (Security Verify Access) or 11.0.0.0 to 11.2.0 (Verify Identity Access)
  2. Identify installed IBM Verify Identity Access version
    Run 'rpm -q vii' or check /opt/ibm/vii/bin/version.sh. For container versions, inspect the image for product version labels.
    Affected if Version falls within 11.0.0.0 to 11.2.0 (Verify Identity Access container)
  3. Check if Web Reverse Proxy is configured
    Look for configuration files in /var/isd/wa or /opt/ibm/isam/var/ and check for reverse proxy definition XML files (typically in config/wa/rp*.xml or similar paths under the verify access installation directory).
    Affected if A Web Reverse Proxy instance is defined and enabled in the configuration
  4. Verify if reverse proxy is actively listening
    Run 'netstat -tlnp | grep -E "443|80|8443"' or 'ss -tlnp' to check for processes listening on HTTP/HTTPS ports. Check if the IBM Verify Access httpd or webseald process is running.
    Affected if The Web Reverse Proxy component (webseald or httpd) is running and accepting connections

You are affected if the installed version is within 10.0.0.0-10.0.9.1 or 11.0.0.0-11.2.0 AND the Web Reverse Proxy feature is configured and active.

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

Configure the reverse proxy to strictly validate and normalize incoming HTTP requests, ensuring consistent parsing between the proxy and backend. Apply vendor-provided patches for IBM Security Verify Access and ensure reverse proxy configurations are aligned with backend server expectations.

Recommended fix Moderate confidence

Security Verify Access 10.0.9.2 or later / Verify Identity Access 11.0.2.1 or later

  1. 1. Identify the current version of IBM Security Verify Access or IBM Verify Identity Access running in your environment
  2. 2. Plan for upgrade during a maintenance window
  3. 3. Backup current configuration and any critical data
  4. 4. For Security Verify Access: Upgrade from 10.0.0.0-10.0.9.1 to version 10.0.9.2 or later
  5. 5. For Security Verify Access Container: Upgrade from 10.0.0.0-10.0.9.1 to version 10.0.9.2 or later
  6. 6. For Verify Identity Access: Upgrade from 11.0.0.0-11.0.2.0 to version 11.0.2.1 or later
  7. 7. For Verify Identity Access Container: Upgrade from 11.0.0.0-11.0.2.0 to version 11.0.2.1 or later
  8. 8. After upgrade, verify the reverse proxy configuration is working correctly
Caveat Review release notes for any configuration changes between versions; test thoroughly in non-production environment first

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2862 — 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-2862 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