Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious CSRF page/email
-
DeliveryLure authenticated admin to visit
-
ExploitBrowser auto-submits forged request
-
ExecutionAppliance executes action in admin's session
-
ImpactUnauthorized configuration/account change
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial 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 an active, authenticated session to the IBM Security Verify Access / Verify Identity Access web/management interface AND user interaction (UI:R): a logged-in user - most impactfully an administrator - must be tricked into loading attacker-controlled web content (malicious link, email, or page) while that session is valid. The attacker needs no credentials of their own (PR:N) and no special appliance configuration is named in the description; the limiting factors are the need for a concurrently authenticated victim, the social-engineering/user-interaction step, and network reachability of the targeted management endpoint (highest risk where that interface is internet-exposed). The high impact presumes the forged request targets privileged state-changing actions. |
| Impact | The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) rates this CSRF (CWE-352) as High, but several signals temper the real-world urgency. No EPSS score, no KEV listing, and no public POC were provided in the input, so by precision rules this is 'no public exploit identified at time of analysis' - there is no evidence of active or automated exploitation. The CVSS vector's PR:N reflects that the ATTACKER needs no credentials, but the UI:R requirement plus the inherent nature of CSRF means success depends entirely on luring an already-authenticated administrator/user of the appliance into visiting a malicious page while their session is live - a meaningful real-world limiter. The C:H/I:H/A:H impacts appear to assume the forged request triggers high-privilege administrative actions; the terse description ('malicious and unauthorized actions') does not itself confirm full CIA compromise, so these impact ratings are vendor-assigned and should be treated as the worst case rather than verified fact. Net: this is a genuine, patch-worthy flaw in an enterprise IAM product, but it is a user-interaction-gated CSRF with no exploitation evidence - prioritize patching of internet-exposed management interfaces, but it is not an emergency on the level of an unauthenticated RCE. |
| Exploit ScenarioDerived | An attacker crafts a web page or email containing a hidden, auto-submitting form (or image/script request) targeting a state-changing endpoint of the IBM Security Verify Access / Verify Identity Access management interface. While an administrator is authenticated to the appliance, they are socially engineered into visiting the attacker's page, and their browser silently submits the forged request with their valid session cookies, performing an unauthorized administrative action. No public exploit code was identified at time of analysis, and success requires the victim to be logged in and to interact with attacker-controlled content. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 09, 2026
Cross-site request forgery in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container editions) lets a remote attacker who lures a logged-in user into loading attacker-controlled content submit unauthorized, privileged state-changing requests through that victim's authenticated session; CVSS 3.1 rates it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no credentials of their own, but successful abuse depends on a concurrently authenticated victim - most damagingly an administrator - plus a social-engineering/user-interaction step, so exposure is greatest where the management interface is internet-reachable. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a vendor patch is available per IBM's advisory.
Earlier versions of this analysis (1)
Cross-site request forgery 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 attacker (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) to cause a logged-in administrator or user to submit a forged request that the appliance treats as trusted, resulting in limited unauthorized integrity changes (I:L) with no confidentiality or availability impact. Exploitation is not server-to-server and depends on social-engineering an authenticated victim with an active session into visiting attacker-controlled content that auto-submits the crafted request, which is the sole reason the base score stays at 4.3 despite the unauthenticated network attack vector. At time of analysis there is no public exploit identified, and no evidence of confirmed active exploitation (no CISA KEV listing); the primary risk driver is the large number of internet-facing Verify Access deployments in identity-federation roles.
RemediationAI
Patch available per vendor advisory - apply the fixed release from IBM's Security Verify Access / Verify Identity Access bulletin at https://www.ibm.com/support/pages/node/7291628; the exact fixed build numbers are not enumerated in the available data, so consult the advisory for the precise upgrade target for each 10.0.x and 11.0.x (and container image) branch. Until patched, the highest-value compensating control is to remove the management interface from untrusted networks: restrict it to a dedicated administrative VLAN or jump host, block external reachability with firewall/ACL rules, and terminate remote administrative access through a VPN or bastion (trade-off: added operational friction and a single choke point that must itself be hardened). Shorten administrative session lifetimes and idle timeouts, and require re-authentication before sensitive changes, which reduces but does not eliminate the window for a forged request (trade-off: more frequent logins for administrators). Where supported, enforce strict SameSite cookie attributes and require browsers used for administration to be dedicated and not used for general web browsing or email, lowering the chance an administrator loads attacker-controlled content while authenticated (trade-off: policy and user-training overhead, not a code-level fix). Because exploitation requires user interaction, alerting on unusual state-changing administrative requests originating shortly after a user clicks external links can provide detective coverage, but logging is a compensating measure and not a substitute for the vendor patch.
Affected VersionsENISA
Affected Packages
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 issue is a classic cross-site request forgery (CWE-352) affecting the web/management interface of IBM Security Verify Access and its successor branding IBM Verify Identity Access, in both appliance and container form factors (CPE: cpe:2.3:a:ibm:security_verify_access, cpe:2.3:a:ibm:verify_identity_access, plus the corresponding *_container entries). In CSRF, the browser automatically attaches the victim's still-valid session cookie to a forged request, so the server cannot distinguish the attacker's crafted request from a legitimate user action unless it validates a per-request anti-CSRF token and/or relies on strict SameSite cookie scoping. The weakness here indicates that state-changing operations in the administrative interface are reachable without adequate token validation or origin verification, and the CVSS vector's PR:N/UI:R combination confirms the attacker supplies no credentials while the victim supplies the authenticated context and the interaction. Because the affected versions span two product generations (10.0 through 10.0.9.2 and 11.0 through 11.0.3), the same interface code path is likely shared across the Security Verify Access and Verify Identity Access lines and their containers; EUVD tracks it as EUVD-2026-95271.
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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CSRF needs no attacker privileges (PR:N) but requires a logged-in victim to interact (UI:R) over the network (AV:N); high CIA retained per vendor, assuming forged privileged admin actions.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.
Executive ViewAI
IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including their container editions, contain a cross-site request forgery flaw rated CVSS 8.8 that lets an attacker ride an already-authenticated session to push through privileged configuration changes. Because the affected systems are the identity and access management tier, a successful attack against an administrator's session could let an outsider alter authentication policy, add credentials, or weaken controls that the rest of the enterprise depends on. Leadership should care most if the administrative interface is reachable from the internet, since exploitation requires no attacker credentials and only a single user-interaction step.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Security Verify Access
View allIBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct ph
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
Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity A
Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 1
An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus bot
IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto
IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto
IBM Security Access Manager 9.0.7 and IBM Security Verify Access 10.0.0 could allow an unauthorized public Oauth client
IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fai
Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.
Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 thro
Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0
EUVD-2026-95271
GHSA-jjmx-x2x9-rhq6
NVD
CVE.org
EPSS
Exploit-DB