CVE-2025-36354: IBM Security Verify Access command execution
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 an unauthenticated user to execute arbitrary commands with lower user privileges on the system due to improper validation of user supplied input.
- Published
- Oct 6, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-78
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · ibm
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibm | security verify access | cpe:2.3:a:ibm:security_verify_access |
| ibm | security verify access docker | cpe:2.3:a:ibm:security_verify_access_docker |
| ibm | verify identity access | cpe:2.3:a:ibm:verify_identity_access |
| ibm | verify identity access docker | cpe:2.3:a:ibm:verify_identity_access_docker |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Security Verify Access Appliance
- 10.0.0.0 and later · up to and including 10.0.9.0 IF2affected · semver
- 11.0.0.0 and later · up to and including 11.0.1.0affected · semver
IBM Security Verify Access Docker
- 10.0.0.0 and later · up to and including 10.0.9.0 IF2affected · semver
- 11.0.0.0 and later · up to and including 11.0.1.0affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm security verify access10.0.0.0 and later · before 10.0.9.0
- ibm security verify access10.0.9.0
- ibm security verify access docker10.0.0.0 and later · before 10.0.9.0
- ibm security verify access docker10.0.9.0
- ibm verify identity access11.0.0.0 and later · before 11.0.1.0
- ibm verify identity access11.0.1.0
- ibm verify identity access docker11.0.0.0 and later · before 11.0.1.0
- ibm verify identity access docker11.0.1.0
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-39070IBM Security Verify Access 10.0.0.0, 10.0.1.0 and 10.0.2.0 with the advanced access control authentication service enabled could allow an…40Plan
- CVE-2026-78406Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access39Monitor
- CVE-2026-78401Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-0161Feb 20, 2025 · IBM Security Verify Access Appliance code injection31Monitor
- ← EarlierCVE-2025-0163Jun 11, 2025 · IBM Security Verify Access information disclosure21Monitor
- Later →CVE-2025-36355Oct 6, 2025 · IBM Security Verify Access code execution34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-49803311 days apartIBM Security Verify Access Appliance command execution35Monitor
- CVE-2026-1345177 days apartSecurity Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access29Monitor
- CVE-2026-12005310 days apartSecurity vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access28Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.