CVE Intelligence
Critical Authentication

CVE-2025-36087 — IBM Security Verify Access hard coded credentials

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.

Published Oct 12, 2025 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: ibm

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.29%
ahead of 20% of scored CVEs · Oct 19, 2026
Affects
Ibm
Security Verify Access and 2 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Ibm Security Verify Access, Ibm Verify Identity Access, Ibm Verify Identity Access Container).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Ibm Security Verify Access ≥ 10.0.0 and ≤ 10.0.9 Vulnerable NIST National Vulnerability Database
Ibm Security Verify Access ≥ 10.0.0 and ≤ 10.0.9version 11.0.0 Vulnerable CVE Program (cve.org) e CISA ADP
Ibm Verify Identity Access version 11.0.0 Vulnerable NIST National Vulnerability Database
Ibm Verify Identity Access Container ≥ 10.0.0 and ≤ 10.0.9version 11.0.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.1 CVSS 3.1 High 2.2 5.9 psirt@us.ibm.com via NIST National Vulnerability Database
8.1 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.1 CVSS 3.1 High — — ibm via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-798 · Use of Hard-coded Credentials

Other CVEs with this weakness →

EPSS over time FIRST

Oct 18, 2026 → Oct 19, 2026 · 2 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · ibm/security verify access, ibm/verify identity access container
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 18, 2026
  • Affected products added · ibm/security verify access, ibm/verify identity access
    Oct 18, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 18, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 18, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 18, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Oct 12, 2025 · ibm

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 18, 2026 – Oct 18, 2026
  • 1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

3 on the record

Elsewhere on this site

Ibm
every CVE for this vendor
Authentication
same class
CWE-798
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-109126 IBM Verify Identity Access and IBM Security Verify Access Hard-coded Credentials 5h
  • Critical CVE-2026-78401 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
  • Critical CVE-2026-78406 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
  • Medium CVE-2026-78407 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
  • Medium CVE-2026-78399 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d
  • High CVE-2026-78388 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access 11d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-36087 is "IBM Security Verify Access hard coded credentials", rated Critical. It affects Security Verify Access (Ibm); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.