CVE Tools

CVE-2026-19491

Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access

No known exploitation. EPSS puts it in the 25th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • IBM Security Verify AccessAffected: ≥ 10.0, ≤ 10.0.9.2Upgrade to: after 10.0.9.2Stated by: CVE record
  • IBM Verify Identity AccessAffected: ≥ 11.0, ≤ 11.0.3Upgrade to: after 11.0.3Stated by: CVE record
  • IBM Security Verify Access ContainerAffected: ≥ 10.0, ≤ 10.0.9.2Upgrade to: after 10.0.9.2Stated by: CVE record
  • IBM Verify Identity Access ContainerAffected: ≥ 11.0, ≤ 11.0.3Upgrade to: after 11.0.3Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run IBM Security Verify Access or IBM Verify Identity Access (including container deployments) and note the installed version.
  2. If running Security Verify Access, upgrade to version 10.0.9.3 or later.
  3. If running Verify Identity Access, upgrade to version 11.0.3.1 or later.
  4. Restrict network access to the admin/login interface until the update is applied.
  5. Confirm with your IT provider or vendor contact that the patch has been installed and verified.

What it is

From the CVE record

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote attacker to bypass authentication due to improper authentication.

In plain language

Written by AI from the record

A serious flaw in IBM Verify Identity Access and IBM Security Verify Access lets an outside attacker skip the login screen entirely and get full administrator control, so if you run this software you should update it right away.

Improper authentication (CWE-287) in IBM Security Verify Access and IBM Verify Identity Access allows a remote, unauthenticated network attacker to bypass login checks and obtain administrative control over the system.

If you're affected

  • Full system takeover
  • Unauthorized access to sensitive data
  • Identity and access management compromised
  • Operational disruption
  • Regulatory/compliance exposure

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS25th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 25th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Rising, driven by in-the-wild reports.

Lifecycle

12 events over 14 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablepatch available, record updated, record updated
  3. Patch availablerecord updated
  4. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 9.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Security Verify Access, not every advisory.