NVD / CVE Program· CNA ibm

CVE-2026-19494: Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Auth bypass

EUVD-2026-95276

Published: Oct 8, 2026
Updated: Oct 10, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.5
CNA · ibm: 8.1; 1.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
ibm	security verify access	cpe:2.3:a:ibm:security_verify_access
ibm	security verify access container	cpe:2.3:a:ibm:security_verify_access_container
ibm	verify identity access	cpe:2.3:a:ibm:verify_identity_access
ibm	verify identity access container	cpe:2.3:a:ibm:verify_identity_access_container

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

ibm security verify access10.0.0 and later · before 10.0.9.3
ibm security verify access container10.0.0.0 and later · up to 10.0.9.2 inclusive
ibm verify identity access11.0 and later · before 11.0.3.1
ibm verify identity access container11.0.0.0 and later · up to 11.0.3.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.

IBM Security Verify Access
- 10.0 and later · up to and including 10.0.9.2affected · semver
IBM Security Verify Access Container
- 10.0 and later · up to and including 10.0.9.2affected · semver
IBM Verify Identity Access
- 11.0 and later · up to and including 11.0.3affected · semver
IBM Verify Identity Access Container
- 11.0 and later · up to and including 11.0.3affected · semver

Same product

ibm: all records

Other highest-scoring records for the same primary product.

CVE-2021-39070IBM Security Verify Access 10.0.0.0, 10.0.1.0 and 10.0.2.0 with the advanced access control authentication service enabled could allow an at
40Plan
CVE-2026-78406Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
39Monitor
CVE-2026-78401Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-19491Oct 8, 2026 · Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
30Monitor
← EarlierCVE-2026-19493Oct 8, 2026 · Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
30Monitor
Later →CVE-2026-19498Oct 8, 2026 · Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-4101190 days apartSecurity Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
39Monitor
CVE-2026-1235957 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
32Monitor
CVE-2026-168230 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
30Monitor
CVE-2026-194910 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
30Monitor
CVE-2026-1192357 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
29Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-169160 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
35Monitor
CVE-2026-194820 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
35Monitor
CVE-2026-121090 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
28Monitor
CVE-2026-168300 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access
21Monitor

Bug bounty scope

IBMHackerOne · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

SSVC exploitation— → noneOct 10, 2026, 5:07 AM UTC
CVSS8.1 → 6.5Oct 9, 2026, 3:07 PM UTC
Severityhigh → mediumOct 9, 2026, 3:07 PM UTC
Exploit maturity— → noneOct 8, 2026, 10:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.ibm.com/support/pages/node/7291628

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records