dbcve.org
Security Verify AccessApplication · Ibm

CVE-2025-36087

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-13
Fix available
A fix is available. Upgrade to after 10.0.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Security Verify Access 10.0.0 through 10.0.9, 11.0.0, IBM Verify Identity Access Container 10.0.0 through 10.0.9, and 11.0.0, under certain configurations, contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Security Verify Access and IBM Verify Identity Access Container contain hard-coded credentials (passwords or cryptographic keys) embedded in the software. These credentials are used for inbound authentication, outbound communication to external systems, or encryption of internal data, creating critical vulnerabilities where attackers can gain unauthorized access or compromise encrypted data.

MitigationLocate and remove all hard-coded credentials from the affected products, replace them with dynamically generated or properly managed credentials, rotate any credentials that may have been exposed, and implement a secure credential management framework.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Security Verify AccessApplication
Affected:>= 10.0.0, <= 10.0.9
Verify Identity AccessApplication
Affected:= 11.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product and version
    Run 'rpm -qi ibm-secverify-access' or 'docker images' to find the installed version of IBM Security Verify Access or IBM Verify Identity Access. Check the version string against the affected ranges: 10.0.0 through 10.0.9 for Security Verify Access, or version 11.0.0 for Verify Identity Access.
    Affected if The installed version falls within the listed ranges.
  2. Locate configuration files that may contain hard-coded credentials
    Search the installation directory for XML, properties, or configuration files such as config.xml, application.properties, or similar. Use 'find /opt/ibm -name "*.xml" -o -name "*.properties" -o -name "*.conf"' to locate these files.
    Affected if Any configuration files contain embedded passwords, API keys, or cryptographic keys.
  3. Search for hard-coded passwords in Java or script files
    Use grep to search for patterns like 'password=', 'pwd=', 'passwd=', or string literals that resemble credentials within the product's installation directories: 'grep -r -E "(password|passwd|pwd)\s*[=:]\s*['\"]" /opt/ibm/'
    Affected if Hard-coded password strings are found in source code, scripts, or configuration files.
  4. Inspect for hard-coded cryptographic keys
    Search for PEM files, keystore files, or embedded encryption keys within the installation: 'find /opt/ibm -name "*.pem" -o -name "*.key" | xargs ls -la'. Also grep for base64-encoded strings that may represent keys.
    Affected if Embedded encryption keys or certificates with hard-coded private keys are present in the installation.
  5. Check default credential usage
    Review documentation or default configuration files for any documented default credentials. Attempt to identify if default accounts exist with hard-coded passwords that cannot be changed through normal administration.
    Affected if Default accounts exist with non-configurable, hard-coded passwords.

Your environment is affected if the installed version matches the affected ranges AND hard-coded credentials are found embedded in configuration files, scripts, application code, or certificate/key files within the product installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 10.0.9
Interim mitigation

Locate and remove all hard-coded credentials from the affected products, replace them with dynamically generated or properly managed credentials, rotate any credentials that may have been exposed, and implement a secure credential management framework.

Fix this in Security Verify Access Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36087 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data