Skip to main content

IBM Security Verify Access EUVDEUVD-2026-95284

| CVE-2026-11930 HIGH
Improper Authorization (CWE-285)
2026-10-08 ibm GHSA-fpg9-wj5q-fhvg
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Identify Verify Access-protected web server
  2. Exploit
    Send request to protected resource
  3. Execution
    Authorization check not enforced
  4. Impact
    Gain unauthorized access/modification

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization verification
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

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

Exploitation Conditions

Exploitation requires that IBM Security Verify Access / Verify Identity Access be deployed in front of one of the 'some web servers' for which authorization is not correctly enforced - i.e., the flaw is tied to specific protected web-server configurations rather than all deployments, as reflected by the AC:H rating. The attacker needs network access to the reachable protected resource (AV:N) and no authentication (PR:N) or user interaction (UI:N). Limiting factors: the high attack complexity and the description's scoping to 'some' web servers mean default or unaffected configurations are not exploitable; organizations must confirm whether their specific policy/web-server setup is among the affected ones per IBM advisory node/7291628.

Impact

This is a moderate-severity improper authorization flaw (CWE-285) scored CVSS 5.9 by IBM. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N indicates a network-reachable, unauthenticated (PR:N) weakness but with high attack complexity (AC:H), meaning successful exploitation depends on conditions outside the attacker's control - consistent with the description's qualifier that authorization 'may not' be enforced correctly for 'some' web servers, implying specific configurations are affected rather than all deployments. Impact is integrity-only (I:H, C:N, A:N), so this permits unauthorized modification/access-control bypass but is not scored as directly exposing data or causing outages. No EPSS score, KEV listing, or POC was provided in the input, so exploitation likelihood signals are absent; there is no public exploit identified at time of analysis and it is not in CISA KEV. Net assessment: this is a legitimate patch-worthy authorization bypass in a security product (IAM gateway), which raises its practical importance, but the AC:H rating, config-dependent scope, and absence of any exploitation evidence place it below the urgency of high-EPSS or KEV-listed flaws. Note the vagueness of the vendor description ('may not enforce authorization correctly for some web servers') limits precise scoping - verify exact affected configurations with IBM advisory node/7291628.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends requests to a reverse-proxied or protected web server fronted by IBM Verify Access in an affected configuration, where the access-control policy fails to be enforced, allowing them to reach or modify a resource that should have required authorization. Because attack complexity is high, the attacker likely must target a specific vulnerable web-server configuration or race/condition rather than any default deployment. No public exploit code was identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 08, 2026

Improper authorization enforcement in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can allow unauthenticated remote attackers (PR:N, UI:N) to bypass access controls and alter protected content or state (I:H, C:N, A:N) when the product is deployed in front of certain web servers. The flaw, however, is configuration-dependent: as reflected by the AV:N/AC:H vector and IBM's scoping to 'some' web servers, only specific protected web-server integrations are exposed, and default or unaffected setups are not exploitable. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM rates the issue 5.9 (moderate); the affected deployments also include the containerized editions of both products.

RemediationAI

Vendor-released patch: available per IBM advisory https://www.ibm.com/support/pages/node/7291628 - apply the fixed maintenance level IBM publishes there for IBM Security Verify Access 10.0 (10.0.9.2 and earlier) and IBM Verify Identity Access 11.0 (11.0.3 and earlier), including the corresponding container images, and note that the provided intelligence does not specify the exact fix version string, so the advisory (not this analysis) must be used to confirm the target build. Until patching is complete, the most effective compensating control is to constrain exposure of the affected integration rather than rely on generic hardening: place the Verify Access front end behind network segmentation or a firewall/ACL that only permits expected client networks to reach the protected resources, since the flaw is unauthenticated and network-reachable (AV:N, PR:N) - the trade-off is reduced accessibility for legitimate external users. Where the affected web server type is not operationally required, temporarily removing that server from the protected set or routing it through an alternative enforcement point eliminates the bypass path at the cost of functionality. Because the flaw only manifests for specific web-server configurations, confirm against the advisory whether your deployment is in scope before assuming protection, and re-verify authorization policy behavior for each protected backend after upgrading; if any exposure window occurred, review logs for policy-bypassing requests to protected resources given the integrity-only (I:H) impact.

Affected VersionsENISA

Verify Identity Access 11.0 ≤11.0.3
Security Verify Access 10.0 ≤10.0.9.2
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-285 (Improper Authorization): IBM Security Verify Access and Verify Identity Access - web access management and identity/access proxy platforms that sit in front of protected HTTP resources and enforce policy decisions - fail to correctly apply authorization decisions for particular protected web-server configurations. Normally these products act as a policy enforcement point, evaluating authenticated identity and policy to grant or deny access to backend web servers; here, the enforcement step is skipped or misapplied for certain web-server types, so a request can reach a resource that policy should have denied. The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N indicates the flaw is reachable over the network without credentials or user interaction, but that exploitation depends on a specific, non-default deployment context (hence AC:H), and that the demonstrated impact is integrity-only - modification of protected data or actions - with no direct confidentiality or availability loss. CPE data lists four affected artifacts: Security Verify Access, Verify Identity Access, Security Verify Access Container, and Verify Identity Access Container, indicating both appliance/software and container-based deployments share the same authorization defect. The CWE class matters because authorization bugs are not memory-safety issues; they cannot be detected by exploit mitigations and must be fixed by correcting the policy-enforcement logic itself.

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 MEDIUM
NVD 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 5.9 MEDIUM

Network-reachable and unauthenticated (AV:N/PR:N), but config-dependent 'some web servers' and vague trigger justify AC:H; authorization bypass affects integrity (I:H) with no stated confidentiality or availability impact.

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

Primary rating from Vendor (ibm).

CVSS VectorNVD

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

Lifecycle Timeline

2
Severity Changed
Oct 09, 2026 - 14:22 NVD
MEDIUM HIGH
CVSS changed
Oct 09, 2026 - 14:22 NVD
5.9 (MEDIUM) 7.5 (HIGH)

DescriptionNVD

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 may not enforce authorization correctly for some web servers.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
enterprise IAM access gateway, common in large orgs but not ubiquitous
Data Quality
5 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 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
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

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

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

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