Skip to main content

Verify Identity Access EUVDEUVD-2026-104674

| CVE-2026-109126 HIGH
Use of Hard-coded Credentials (CWE-798)
2026-10-20 psirt@us.ibm.com GHSA-35w7-m95r-vv83
8.8
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

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

  1. Access
    Reach appliance via adjacent network/physical proximity
  2. Exploit
    Authenticate with hard-coded credentials
  3. Execution
    Gain elevated privileges on appliance
  4. Impact
    Full compromise of IAM gateway

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

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

Exploitation Conditions

Exploitation requires the attacker to be in adjacent-network or physical proximity to the appliance (per the AV:A vector and IBM's 'physically proximate' wording - these disagree and should be verified) and to use credentials hard-coded into IBM Verify Identity Access 11.0.3.1 or IBM Security Verify Access 10.0.9.3. No authentication is required beyond the embedded credentials and no user interaction is needed (PR:N/UI:N). The principal limiting factor is lack of remote/internet reachability: an attacker cannot exploit this from an arbitrary remote network, which materially reduces exposure for appliances deployed on segmented or physically restricted management networks. Only the specified appliance versions are affected.

Impact

This is a serious but access-constrained flaw. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes low-complexity exploitation requiring no privileges or user interaction and yielding full confidentiality, integrity and availability impact - consistent with CWE-798 hard-coded credentials that act as an always-valid backdoor. The critical limiter is the attack vector: the CVSS encodes AV:A (adjacent network), yet the IBM description states a 'physically proximate attacker,' which maps more naturally to AV:P (physical). This is a direct conflict between two authoritative signals and should be verified with IBM - if the true vector is physical, real-world risk drops substantially versus an adjacent-network reading. No exploitation-probability or exploitation-status signals are available: there is no EPSS score, no CISA KEV listing, and no public POC in the provided data, so there is no public exploit identified at time of analysis. Net: the high base score reflects impact and ease once an attacker is in position, but the physical/adjacent access requirement makes this a lower real-world priority than a remotely exploitable 8.8 - patch on normal cycles unless the appliances sit in low-trust physical/network zones.

Exploit ScenarioDerived

An attacker with adjacent-network or physical proximity to an affected IBM Verify Identity Access 11.0.3.1 or IBM Security Verify Access 10.0.9.3 appliance connects to a management or service interface and authenticates using credentials hard-coded into the product, obtaining elevated privileges on the device. No prior account or user interaction is needed, and attack complexity is low. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 20, 2026

Hard-coded credentials in IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 appliances can let an attacker in physical or adjacent-network proximity gain elevated privileges, with CVSS 3.1 score 8.8 reflecting high confidentiality, integrity, and availability impact. The CVSS vector indicates no privileges or user interaction are required (PR:N/UI:N), but the adjacent-network attack vector limits exposure to attackers who can reach the appliance locally or on an adjacent segment. No public exploit code or confirmed active exploitation was identified at time of analysis.

RemediationAI

No vendor-released patch with an exact fixed version was identified in the available data; consult IBM's advisory at https://www.ibm.com/support/pages/node/7292606 for updated appliance firmware and vendor remediation guidance. Until a fix is applied, reduce exposure by placing the appliance management interface behind strict network segmentation and ACLs that permit only trusted administrative hosts, disabling unused management services, and physically securing the appliance and its management ports; these controls can block legitimate administration if ACLs are too narrow, so validate access paths first. Because the credentials are hard-coded, changing default passwords alone may not remove the risk; follow IBM guidance for any credential-rotation or configuration workaround, and monitor authentication logs for unexpected logins from adjacent networks.

Affected VersionsENISA

Security Verify Access 10.0.9.3
Verify Identity Access 11.0.3.1

Affected Packages

euvd security_verify_access no fix
euvd verify_identity_access no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 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 flaw is CWE-798 (Use of Hard-Coded Credentials) in the IBM Verify Identity Access and IBM Security Verify Access appliance software. Hard-coded credentials are static secrets embedded in the product build; when shared across deployments or not uniquely provisioned, an attacker who obtains or guesses them can authenticate without normal credential management and then escalate privileges. The CVSS vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H describes an adjacent-network attack requiring low complexity and no user interaction, with high impact across confidentiality, integrity, and availability. IBM's description says 'physically proximate' while the vector is AV:A, so the exact access path should be verified; either way, exposure is constrained by the need for local or adjacent-network reachability rather than arbitrary internet access. No CPE strings were provided, but the affected versions are IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 Appliance.

Know when the next one hits your stack

  • 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 (us) PRIMARY 8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Hard-coded credentials give no-privilege, low-complexity access with full C/I/A impact; AV:A retained per vendor vector though description's 'physically proximate' could justify AV:P.

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

Primary rating from Vendor (us).

CVSS VectorVendor: us

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

DescriptionCVE.org

IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 Appliance could allow a physically proximate attacker to gain elevated privileges due to the use of hard-coded credentials.

Executive ViewAI

Why It Matters

IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 contain hard-coded credentials that could let an attacker with physical or adjacent-network access gain elevated privileges, affecting the confidentiality, integrity, and availability of identity infrastructure. Because these appliances are often central to authentication and access control, leadership should prioritize containment and monitoring even though no public exploit was identified at time of analysis.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting physical access, segmenting and firewalling adjacent-network paths, limiting access to trusted administrative hosts, monitoring privileged and authentication logs for anomalous activity, disabling unused accounts or services where supported, and engaging IBM for mitigation guidance and patch timing.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
enterprise IBM IAM access appliance, common in large orgs not everywhere
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.2%
Patch available No
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
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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