Skip to main content

IBM Verify Access CVE-2026-19493

| EUVDEUVD-2026-95274 HIGH
Path Traversal (CWE-22)
2026-10-08 ibm GHSA-77j9-888p-hm26
7.5
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed VIA/ISVA endpoint
  2. Delivery
    Send request with path-traversal payload
  3. Exploit
    Trigger arbitrary file write outside root
  4. Execution
    Plant web shell or config
  5. Impact
    Execute code on appliance

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no special conditions are required beyond network reachability to an affected IBM Security Verify Access (10.0-10.0.9.2) or IBM Verify Identity Access (11.0-11.0.3) instance, including their container editions - exploitation is remote and unauthenticated against the shipped management/runtime interface. The limiting factor is network exposure: these appliances are often placed behind reverse proxies or on internal/DMZ segments, so instances not reachable from attacker-controlled networks are not exposed. The advisory does not name the exact vulnerable endpoint, parameter, or whether a non-default feature must be enabled, so defenders should treat any reachable instance as potentially affected until IBM's node/7291628 guidance is reviewed.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a remotely exploitable, unauthenticated, low-complexity flaw with high integrity impact (C:N/I:H/A:N), consistent with an arbitrary file write via path traversal (CWE-22). The 7.5 base score reflects integrity-only impact; however, arbitrary file write on an access-management product frequently escalates to code execution or authentication bypass, so real-world impact may exceed the raw score. No EPSS probability, KEV entry, POC, or SSVC decision data was provided in the input, so exploitation likelihood cannot be quantified from the available signals - this is currently a theoretical-but-high-potential issue rather than a confirmed active threat. The product class (identity/access gateway, often internet-facing) raises practical concern despite the absence of exploitation evidence: an unauthenticated network-reachable file-write on a security appliance is exactly the profile attackers prioritize once a POC surfaces. Patch availability from IBM makes remediation straightforward, which should drive prioritization upward for internet-exposed deployments. Key missing data: EPSS and POC status are unknown, so urgency is inferred from vector and product exposure, not from observed exploitation.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request containing directory-traversal sequences to an exposed IBM Security Verify Access / Verify Identity Access endpoint, causing a file to be written outside the intended directory. By writing to a web-accessible or startup location, the attacker can plant a web shell or malicious configuration, potentially converting the file write into remote code execution on the appliance. No public exploit was identified in the provided data, and no user interaction is required per the CVSS vector.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Path traversal (CWE-22) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote, unauthenticated attacker to write arbitrary files on the affected appliance or container by supplying crafted path components. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5) exploitation is network-reachable, low-complexity and unauthenticated, with high integrity impact and no confirmed confidentiality or availability impact - a file-write primitive rather than a file-read or denial-of-service bug. No public exploit identified at time of analysis and the CVE is not listed in CISA KEV; the vendor has released a patch and the sole reference is IBM's advisory at https://www.ibm.com/support/pages/node/7291628. Exposure is bounded by network reachability: instances sitting behind reverse proxies or confined to internal/DMZ segments that attackers cannot reach are not directly exploitable.

RemediationAI

Patch status is 'Patch available per vendor advisory' - IBM has published remediation guidance at https://www.ibm.com/support/pages/node/7291628, and the supplied data does not include specific fix version numbers, so obtain the exact patched build for your product line (Security Verify Access 10.x or Verify Identity Access 11.x) and the matching container image tag directly from that advisory and apply it before re-exposing the interface. For container deployments, rebuild from the fixed image rather than patching in place, and note that base-image refresh cycles mean the container line may lag the appliance line. If immediate patching is not possible, the effective compensating control is network exposure reduction, which directly addresses the AV:N/PR:N nature of the flaw: place the instance behind a reverse proxy or WAF with path-canonicalization and traversal-pattern filtering, restrict management and runtime interfaces to trusted administrative networks via firewall or allowlist rules, and remove any internet-facing or DMZ listener that is not strictly required - the trade-off is reduced remote-administration convenience and possible breakage of legitimate federation or SSO callbacks if filtering is too aggressive. Additionally, enable file-integrity monitoring on the appliance or container filesystem to detect unauthorized writes in configuration and web-content directories, accepting that monitoring is detective rather than preventive and may generate noise on servers with legitimate high-churn file activity. Because the advisory does not identify the vulnerable endpoint or any optional feature that must be enabled, do not assume a specific feature can simply be disabled; treat every reachable instance as potentially exploitable until IBM's node/7291628 guidance has been reviewed and the fix applied.

Affected VersionsENISA

Security Verify Access 10.0 ≤10.0.9.2
Verify Identity Access 11.0 ≤11.0.3
Verify Identity Access Container 11.0 ≤11.0.3
Security Verify Access Container 10.0 ≤10.0.9.2

Affected Packages

euvd security_verify_access no fix
euvd security_verify_access_container no fix
euvd verify_identity_access no fix
euvd verify_identity_access_container no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-22, improper limitation of a pathname to a restricted directory ('path traversal'): user-controllable input used in a filesystem path is not canonicalized or validated, so sequences such as ../ escape the intended write directory and let the attacker place files elsewhere on the host. Because the assessment scores C:N/I:H/A:N, the flaw is characterized as a write primitive on resources the attacker should not control, not a disclosure or crash issue; IBM describes the outcome specifically as arbitrary file write. CPE data shows the scope covers both product lines and their containerized editions - cpe:2.3:a:ibm:security_verify_access, ibm:verify_identity_access, ibm:security_verify_access_container and ibm:verify_identity_access_container - so the same vulnerable code path appears in the traditional appliance builds and in container images, which matters for image-pinning and rebuild workflows. IBM Security Verify Access (the 10.x lineage, formerly ISAM) and IBM Verify Identity Access (11.x) are access-management/identity-provider platforms built on a hardened Linux base with an embedded web/management interface; an arbitrary file write against such a platform can tamper with configuration, web content, or scripts that are later consumed by privileged processes, so the integrity-only score should not be read as low consequence. The vendor advisory does not name the vulnerable endpoint, parameter, or any non-default feature prerequisite, so the exact preconditions for the write path are not independently confirmed.

Know when Security Verify Access gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

Path traversal file write is remotely reachable and unauthenticated (AV:N/AC:L/PR:N/UI:N) with high integrity impact; no stated confidentiality or availability effect, so C:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

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 perform an arbitrary file write due to path traversal.

Executive ViewAI

Why It Matters

IBM Security Verify Access and IBM Verify Identity Access are affected by a high-severity flaw that permits unauthenticated remote attackers to write arbitrary files, potentially leading to system compromise or unauthorized changes to critical identity infrastructure. Because these platforms underpin authentication and access control for many organizations, a successful exploit could disrupt business operations and weaken security posture. No public exploit identified at time of analysis; patch available per vendor advisory. Security leadership should ensure remediation is prioritized given the systems' strategic importance.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 72% exploitable
Prevalence
Medium
enterprise identity/access gateway, common in large orgs but not universal
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

CVE-2024-35133 HIGH POC
8.2 Aug 29

IBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct ph

CVE-2024-28787 CRITICAL
10.0 Apr 04

IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote at

CVE-2026-78401 CRITICAL
9.8 Oct 08

Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity A

CVE-2026-78406 CRITICAL
9.8 Oct 08

Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 1

CVE-2026-11928 CRITICAL
9.8 Sep 15

An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus bot

CVE-2024-49806 CRITICAL
9.8 Nov 29

IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto

CVE-2024-49805 CRITICAL
9.8 Nov 29

IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto

CVE-2020-4499 CRITICAL
9.8 Oct 15

IBM Security Access Manager 9.0.7 and IBM Security Verify Access 10.0.0 could allow an unauthorized public Oauth client

CVE-2026-11921 CRITICAL
9.1 Sep 15

IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fai

CVE-2026-16916 HIGH
8.8 Oct 08

Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.

CVE-2026-19482 HIGH
8.8 Oct 08

Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 thro

CVE-2026-18740 HIGH
8.8 Oct 08

Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy