CVE-2024-35140: IBM Security Verify Access Docker · Improper Certificate Validation
Affects IBM Security Verify Access DockerSource CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 31 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Security Verify Access Docker | Affected
| Fixed in– |
AI-suggested
1. Apply patches or updates from IBM as soon as they become available for Security Verify Access Docker versions 10.0.0 through 10.0.6. 2. Restrict local access to hosts running IBM Security Verify Access Docker containers by enforcing strict access controls, limiting user permissions, and using role-based access control (RBAC). 3. Implement host-level security measures such as endpoint detection and response (EDR) solutions to monitor for suspicious privilege escalation attempts. 4. Use container security best practices, including isolating containers, minimizing container privileges, and employing security profiles like AppArmor or SELinux. 5. Regularly audit and review local user accounts and permissions on hosts running the affected software to detect and remove unnecessary access. 6. Monitor logs and security alerts for anomalous activity related to certificate validation failures or privilege escalations. 7. Educate system administrators and security teams about the vulnerability and the importance of controlling local access to critical systems. 8. Consider network segmentation to limit the impact of a compromised host and reduce the risk of lateral movement.
Description
IBM Security Verify Access Docker 10.0.0 through 10.0.6 could allow a local user to escalate their privileges due to improper certificate validation. IBM X-Force ID: 292416.