CVE Tools

CVE-2026-16823

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 which product and version you run: IBM Security Verify Access or IBM Verify Identity Access, including the appliance/container editions.
  2. If you run IBM Security Verify Access 10.0 through 10.0.9.2, upgrade to 10.0.9.3.
  3. If you run IBM Verify Identity Access 11.0 through 11.0.3, upgrade to 11.0.3.1.
  4. Download the fix from IBM's support page and apply it to any container deployments as well as the appliance.
  5. Confirm with your IT provider that the update was applied and the system now reports the fixed version.

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 security restrictions due to improper authentication.

In plain language

Written by AI from the record

A critical flaw lets an attacker log into IBM's access-control software without a valid password, so if you run IBM Verify Identity Access or IBM Security Verify Access, you should update to the fixed version now.

CVE-2026-16823 is a remote, unauthenticated security-restriction bypass (CWE-287, improper authentication) in IBM Security Verify Access 10.0–10.0.9.2 and IBM Verify Identity Access 11.0–11.0.3, scoring 9.1 (critical) with no user interaction required.

If you're affected

  • Unauthorized access to protected systems
  • Bypass of login/access controls
  • Exposure of data behind this gateway
  • Compromise of identity infrastructure

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 availablerecord updated
  3. Patch availablepatch available, record updated, record 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.