CVE-2025-36355 — IBM Security Verify Access code execution
IBM Security Verify Access and IBM Security Verify Access Docker 10.0.0.0 through 10.0.9.0 and 11.0.0.0 through 11.0.1.0 could allow a locally authenticated user to execute malicious scripts from outside of its control sphere.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.ibm.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ibm Security Verify Access, Ibm Security Verify Access Appliance, Ibm Security Verify Access Docker…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Ibm | Security Verify Access | ≥ 10.0.0.0 and < 10.0.9.0version 10.0.9.0version 10.0.9.0-interim_fix1version 10.0.9.0-interim_fix2 | Vulnerable | NIST National Vulnerability Database |
| Ibm | Security Verify Access Appliance | ≥ 10.0.0.0 and ≤ 10.0.9.0 IF2≥ 11.0.0.0 and ≤ 11.0.1.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Ibm | Security Verify Access Docker | ≥ 10.0.0.0 and < 10.0.9.0version 10.0.9.0version 10.0.9.0-interim_fix1version 10.0.9.0-interim_fix2 | Vulnerable | NIST National Vulnerability Database |
| Ibm | Security Verify Access Docker | ≥ 10.0.0.0 and ≤ 10.0.9.0 IF2≥ 11.0.0.0 and ≤ 11.0.1.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Ibm | Verify Identity Access | ≥ 11.0.0.0 and < 11.0.1.0version 11.0.1.0 | Vulnerable | NIST National Vulnerability Database |
| Ibm | Verify Identity Access Docker | ≥ 11.0.0.0 and < 11.0.1.0version 11.0.1.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.5 | CVSS 3.1 | High | 2.5 | 5.3 | psirt@us.ibm.com via NIST National Vulnerability Database |
| 8.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.5 | CVSS 3.1 | High | — | — | ibm via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L (score shown at the top: psirt@us.ibm.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 18, 2026 → Oct 19, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · ibm/security verify access appliance, ibm/security verify access docker
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · ibm/security verify access, ibm/security verify access docker, ibm/verify identity access, ibm/verify identity access do
- CVSS changed · 8.5
- Source status changed · → Analyzed
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 18, 2026 – Oct 18, 2026
- 1× Official description updated · Oct 18, 2026 – Oct 18, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-109126 IBM Verify Identity Access and IBM Security Verify Access Hard-coded Credentials 17h
- Critical CVE-2026-78401 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
- Critical CVE-2026-78406 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
- Medium CVE-2026-78407 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
- Medium CVE-2026-78399 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
- High CVE-2026-78388 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-36355 is "IBM Security Verify Access code execution", rated High. It affects Security Verify Access (Ibm); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.5 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.