High Input validation

CVE-2025-36254 — DS8900F and DS8A00 Authentication Bypass

IBM System Storage DS8A00 10.1.3.0 through 10.11.35.0 and IBM DS8900F 89.40.83.0 through 89.44.25.0 could allow an attacker to bypass security authentication due to improperly encoding of DSCLI command output to obtain sensitive information or cause a denial of service.

Published Aug 19, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: ibm

Low

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.5% (30-day exploitation probability)+6
Technical severity (high)+6

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.46%

ahead of 39% of scored CVEs · Oct 15, 2026

Affects

Ibm

DS8900F ( R9.4) and 3 more

CVSS base

7.4

High · 2 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

can an attacker script the kill-chain steps

Technical impact

Partial

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.

Identify exposed assets running the affected vendor/product/version combinations (Ibm DS8900F ( R9.4), Ibm Ds8900f Firmware, Ibm DS8A00 (R10.0 - R10.1)…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Ibm	DS8900F ( R9.4)	≥ 89.40.83.0 and ≤ 89.44.25.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Ibm	Ds8900f Firmware	≥ 89.40.83.0 and ≤ 89.44.25.0	Vulnerable	NIST National Vulnerability Database
Ibm	DS8A00 (R10.0 - R10.1)	≥ 10.1.3.0 and ≤ 10.11.35.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Ibm	Ds8a00 Firmware	≥ 10.1.3.0 and ≤ 10.11.35.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

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

Attack vector

Network

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Scored by
7.4	CVSS 3.1	High	2.2	5.2	psirt@us.ibm.com via NIST National Vulnerability Database
7.4	CVSS 3.1	High	—	—	ibm via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H (score shown at the top: psirt@us.ibm.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-116 · Improper Encoding or Escaping of Output

Other CVEs with this weakness →

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).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · ibm/ds8a00 (r10.0 - r10.1), ibm/ds8900f (r9.4)
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 7.4
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 19, 2026 · ibm

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

www.ibm.com/support/pages/node/7284322
Vendor Advisory, vendor-advisory, patch, NIST National Vulnerability Database

Elsewhere on this site

Ibm
every CVE for this vendor

Input validation
same class

CWE-116
other pages naming this weakness

Related CVEs (same products)

High CVE-2025-36255 DS8900F and DS8A00 Privilege Escalation Aug 19, 2026
Medium CVE-2025-36398 DS8900F and DS8A00 Information Disclosure Aug 19, 2026
High CVE-2025-36192 Missing Authorization with the DS8900F and DS8A00 Hardware Management Console Dec 26, 2025

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-36254 is "DS8900F and DS8A00 Authentication Bypass", rated High. It affects DS8900F ( R9.4) (Ibm); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.46% 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.