Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | CVSS 5.4 (Low-to-Medium) reflects network-accessible attack vector with low complexity, but authentication requirement (PR:L) and user interaction requirement (UI:R) substantially limit real-world impact. EPSS data not provided, but exploitation probability is moderate given that Content-Type misconfigurations are common and well-understood attack surface. No CISA KEV confirmation or public POC identified in provided data, suggesting active exploitation is not confirmed. The combination of authentication + UI requirement + limited blast radius (session-scoped XSS) means this is a lower-priority fix compared to unauthenticated or network-without-auth vulnerabilities, though it still poses risk in environments where certificate listing is accessed by privileged users or federated identity scenarios. Risk assessment: moderate priority for patching, particularly in environments handling sensitive identity data. |
| Exploit ScenarioDerived | An authenticated user with access to the IBM Verify Identity Access certificate listing interface is redirected or socially engineered to click a malicious link injecting JavaScript into the certificate list response. Because the response is labeled as text/html despite containing JSON, the browser executes embedded JavaScript in the user's security context, allowing an attacker to steal session cookies, modify certificate trust settings, or perform actions on behalf of the authenticated user. Exploitation requires both authentication and user interaction (clicking a link or visiting an attacker-controlled page), reducing opportunistic exploitation likelihood. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 01, 2026
IBM Verify Identity Access Container and IBM Security Verify Access versions 10.0-10.0.9.1 and 11.0-11.0.2 return JSON payloads with incorrect Content-Type headers (text/html instead of application/json) when listing certificates via browser sessions, enabling stored or reflected cross-site scripting attacks when browsers interpret the JSON data as executable script. Authenticated users with UI interaction can trigger JavaScript injection affecting confidentiality and integrity of user sessions.
RemediationAI
Patch available per vendor advisory: update IBM Verify Identity Access Container to version 11.0.3 or later and IBM Security Verify Access Container to version 10.0.10 or later; similarly, update non-containerized deployments of IBM Verify Identity Access to 11.0.3 or later and IBM Security Verify Access to 10.0.10 or later. The fix involves correcting the Content-Type header from text/html to application/json for certificate listing endpoints. Consult the vendor advisory at https://www.ibm.com/support/pages/node/7268253 for detailed patch availability and deployment guidance. As a temporary workaround pending patching, restrict access to certificate listing endpoints to trusted networks or implement web application firewall rules to enforce correct Content-Type headers on responses from affected endpoints.
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 vulnerability stems from Content-Type header mismatch (CWE-79: Improper Neutralization of Input During Web Page Generation), a subset of XSS. IBM's identity and access management products expose a certificate listing endpoint that generates valid JSON responses but labels them with the HTML MIME type. Modern browsers apply content-sniffing heuristics and MIME-type-based script execution policies; when JSON containing untrusted or user-controlled data is served as text/html, the JSON structure itself can be interpreted as JavaScript (particularly in older browsers or those with permissive parsing). The affected products span both containerized (Container) and traditional deployment models (non-Container) of IBM Verify Identity Access (versions 11.0-11.0.2) and IBM Security Verify Access (versions 10.0-10.0.9.1), as indicated by the four CPE strings covering both product lines and version ranges.
Know when Verify Identity Access Container 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:L/UI:R/S:C/C:L/I:L/A:N
Primary rating from Vendor (ibm) · only source for this CVE.
CVSS VectorVendor: ibm
Lifecycle Timeline
2DescriptionCVE.org
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 allows certificate listings retrieved via a browser session to return a JSON payload while incorrectly specifying the response Content-Type as text/html. Because the content is delivered with an HTML MIME type, browsers may interpret the JSON data as executable script under certain conditions. This creates an opportunity for JavaScript injection, potentially leading to cross-site scripting (XSS).
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 Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
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
Authentication bypass in IBM Verify Identity Access and IBM Security Verify Access (versions 10.0-10.0.9.1 and 11.0-11.0
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
Cross-site request forgery in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 throu
Format string injection in IBM Security Verify Access (10.0-10.0.9.2) and IBM Verify Identity Access (11.0-11.0.3, inclu
Authentication bypass in IBM Security Verify Access and IBM Verify Identity Access exposes protected resources to unauth
Privilege escalation in IBM Security Verify Access and IBM Verify Identity Access allows an authenticated low-privilege
EUVD-2026-18067
GHSA-crwf-9ph9-47f8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB