CVE-2025-36356: IBM Security Verify Access privilege escalation

Published Oct 6, 2025
·
Updated

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 escalate their privileges to root due to execution with more privileges than required.

Affected Software

12 affected components
IBM Security Verify Access>=10.0.0.0<=10.0.9.0, >=11.0.0.0<=11.0.1.0
IBM Security Verify Access Docker>=10.0.0.0<=10.0.9.0, >=11.0.0.0<=11.0.1.0
IBM Security Verify Access>=10.0.0.0<10.0.9.0
IBM Security Verify Access=10.0.9.0
IBM Security Verify Access=10.0.9.0-interim_fix1
IBM Security Verify Access=10.0.9.0-interim_fix2
IBM Security Verify Access Docker>=10.0.0.0<10.0.9.0
IBM Security Verify Access Docker=10.0.9.0
IBM Security Verify Access Docker=10.0.9.0-interim_fix1
IBM Security Verify Access Docker=10.0.9.0-interim_fix2
IBM Verify Identity Access>=11.0.0.0<11.0.1.0
IBM Verify Identity Access=11.0.1.0

Event History

Oct 6, 2025
CVE Published
via MITRE·04:50 PM
Data Sourced
via MITRE·04:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-36356?

CVE-2025-36356 is classified as a high severity vulnerability due to its potential for privilege escalation.

2

How do I fix CVE-2025-36356?

To fix CVE-2025-36356, update your IBM Security Verify Access or IBM Security Verify Access Docker to versions beyond 10.0.9.0 and 11.0.1.0.

3

Who is affected by CVE-2025-36356?

CVE-2025-36356 affects users of IBM Security Verify Access and IBM Security Verify Access Docker within the specified version ranges.

4

What exploit does CVE-2025-36356 allow?

CVE-2025-36356 allows a locally authenticated user to escalate their privileges to root unintentionally.

5

Is there a workaround for CVE-2025-36356?

Currently, the recommended approach is to apply the appropriate software update as there are no officially documented workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203