Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Verify Identity Access portal
-
DeliverySend HTTP request with SSTI payload in vulnerable parameter
-
ExploitTemplate engine evaluates attacker expression server-side
-
ExecutionServer returns sensitive internal data in response
-
ImpactAttacker reads disclosed credentials or tokens
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V1 - Encoding and Sanitization Template injection prevention
|
| Exploitation Conditions | The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication is required and no special configuration is needed - exploitation targets a network-accessible endpoint of the IBM Verify Identity Access or Security Verify Access application in its default deployment state. IBM has not disclosed the specific endpoint, parameter, or template context involved. Exploitation is limited to confidentiality impact (C:H/I:N/A:N per IBM's assessment), meaning the template engine appears sandboxed against arbitrary command execution. The vulnerability applies equally to traditional appliance and container-based deployments. Limiting factors: the affected versions are specifically bounded (10.0.0-10.0.9.2 IF001 and 11.0.0-11.0.3 IF001), so organizations running patched or out-of-range versions are not affected. |
| Impact | CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) positions this as high-severity unauthenticated remote information disclosure with no special conditions. The EPSS score of 0.15% at the 5th percentile indicates very low current exploitation probability, and the vulnerability is not in CISA KEV, with no public PoC identified. However, SSTI vulnerabilities are well-understood by the offensive community, and a working proof-of-concept against a specific template engine is often achievable within days of disclosure once a researcher identifies the injection point. The confidentiality-only CVSS impact (C:H/I:N/A:N) - IBM's deliberate choice to omit integrity and availability - suggests the template sandbox prevents code execution, but data readable via SSTI in an IAM system (session tokens, LDAP bind credentials, policy rules, user attributes) can directly enable lateral movement or privilege escalation in ways that raw CVSS C:H does not capture. The gap between low EPSS and high potential business impact is the key tension here: this product is a security control plane, so even read-only disclosure of its internal state is a high-consequence event. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP request containing a template injection payload (e.g., a FreeMarker or Velocity expression) to a publicly accessible endpoint of the IBM Verify Identity Access portal. The server-side template engine evaluates the expression and returns internal data - such as environment variables, configuration values, or in-memory session state - in the response body. No public exploit code exists at time of analysis, but the well-documented SSTI technique class means a researcher familiar with the specific template engine could develop a working exploit relatively quickly. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Server-side template injection (SSTI) in IBM Verify Identity Access and Security Verify Access exposes sensitive information to unauthenticated remote attackers via a network-accessible endpoint. The vulnerability affects both traditional appliance deployments and container variants across IBM's IAM product family (versions 10.x and 11.x), and is particularly notable given that IAM platforms routinely handle authentication tokens, user credentials, and security policy configuration - data whose disclosure has outsized downstream impact. IBM has assessed the impact as confidentiality-only (I:N/A:N in the CVSS vector), suggesting the template injection is sandboxed against code execution, but no public exploit or active exploitation has been identified at time of analysis.
RemediationAI
The vendor-released patch is available from IBM; organizations should upgrade to a version beyond the affected range - specifically beyond 11.0.3 Interim Fix 001 for the 11.x line and beyond 10.0.9.2 Interim Fix 001 for the 10.x line, as documented in the IBM support advisory at https://www.ibm.com/support/pages/node/7286188. Exact fixed build numbers should be confirmed against that advisory, as IBM's interim-fix naming convention may introduce additional patch levels. As a compensating control prior to patching, restrict network access to the Verify Identity Access management and portal interfaces using perimeter firewalls or WAF rules to trusted client IP ranges, reducing the AV:N attack surface. Note that WAF-based SSTI filtering is unreliable given the variety of bypass techniques; network segmentation is more dependable but may impact legitimate user access to the authentication portal. Container deployments should also ensure Kubernetes NetworkPolicy restricts ingress to the affected pods.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine) describes a class of injection flaw where user-controlled input is embedded into a server-side template without sanitization, causing the template engine to evaluate attacker-supplied expressions as code. IBM has not disclosed which specific template engine (e.g., FreeMarker, Velocity, Jinja2-equivalent) is responsible, but the 'Ssti' tag in the vulnerability metadata confirms this is the root cause mechanism. IBM Verify Identity Access and Security Verify Access are enterprise Identity and Access Management (IAM) products - the traditional appliance form covers CPEs cpe:2.3:a:ibm:verify_identity_access:* and cpe:2.3:a:ibm:security_verify_access:*, while Kubernetes/container deployments are covered by cpe:2.3:a:ibm:verify_identity_access_container:* and cpe:2.3:a:ibm:security_verify_access_container:*. These products host public-facing authentication portals, making an unauthenticated network attack vector plausible if the vulnerable template is rendered in a pre-authentication context.
Know when Verify Identity 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:N/S:U/C:H/I:N/A:N
Network-accessible pre-auth endpoint with no complexity or interaction required; sandboxed SSTI limits impact to confidentiality only.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
Lifecycle Timeline
3DescriptionCVE.org
IBM Verify Identity Access Advanced Access Control may be vulnerable to an information disclosure attack.
Executive ViewAI
IBM Verify Identity Access and Security Verify Access (versions 10.x and 11.x) contain a server-side template injection vulnerability exposing sensitive information-including authentication tokens, user credentials, and security policies-to unauthenticated remote attackers. This directly undermines the IAM platform's integrity and creates downstream risk across all applications and systems that depend on it for access control.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Verify Identity Access
View allUnauthenticated 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
Hard-coded credentials in IBM Security Verify Access 10.0.0 through 10.0.9 and 11.0.0, and in Verify Identity Access Con
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
Local privilege escalation in IBM Security Verify Access and Verify Identity Access 10.0.x/11.0.x allows an authenticate
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
EUVD-2026-71493
GHSA-2f5f-57cv-q45j
NVD
CVE.org
EPSS
Exploit-DB