CVE Intelligence
Skip to main content
MEDIUM

CVE-2025-12896

CVE-2025-12896 Vulnerability Analysis & Exploit Intelligence

Improper resource management in firmware of some Solidigm DC Products may allow an attacker with local or physical access to gain un-authorized access to a locked storage device.

Published Updated Sources: cvelistV5, Solidigm

Triage

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

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

solidigm

d5_p5316_d7_p5510_d7_p5520_d7_p5620_d5_p5430_d5_p5336

CVSS base

4.4

MEDIUM

CISA SSVC assessment

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

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

solidigm

Products (1)

d5 p5316 d7 p5510 d7 p5520 d7 p5620 d5 p5430 d5 p5336

Every base score collected

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

ScoreVersionSeverityExpl.ImpactSource
4.4CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-307

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1110.001Brute Force: Password Guessing
  • T1078Valid Accounts
  • T1110.003Brute Force: Password Spraying

References

1 on the record

Elsewhere on this site

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