CVE-2025-12902VulnerabilityPublished 7 Nov 2025

CVE-2025-12902: Solidigm™ D5-P5316, D5-P5430, D7-P5520/D7-P5620, D5-P5336 · Improper Initialization

Affects Solidigm™ D5-P5316, D5-P5430, D7-P5520/D7-P5620, D5-P5336Source CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately identify and inventory all affected Solidigm DC drives within the organization to assess exposure. 2. Apply the latest firmware updates from Solidigm that address CVE-2025-12902 as soon as they become available, ensuring all drives run versions equal to or later than ACV10360, 6DV10341, 6CV10241, 9CV10490, or 5CV10326 as applicable. 3. Strengthen physical security controls to prevent unauthorized local or physical access to storage devices, including secure data center access policies, surveillance, and tamper-evident measures. 4. Limit administrative privileges on systems interfacing with these drives to reduce the risk of privilege escalation and misuse. 5. Implement monitoring and logging for unusual access patterns or attempts to access locked storage devices. 6. Consider encryption at the file system or application level as an additional layer of data protection to mitigate risks from firmware-level vulnerabilities. 7. Conduct regular security audits and penetration tests focusing on physical and local access controls to identify potential weaknesses. 8. Educate staff about the risks of physical access attacks and enforce strict access policies.

Description

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 or create a Denial of Service.

Impact

For European organizations, the primary impact of CVE-2025-12902 is the potential unauthorized disclosure of sensitive data stored on affected Solidigm DC drives, especially in environments where physical or local access controls are insufficient. This could undermine data protection obligations under GDPR and other regulations. The denial of service aspect could disrupt critical storage availability, impacting business continuity. Organizations with data centers or critical infrastructure using these drives may face increased risk of insider threats or physical attacks leading to data breaches. The requirement for high privileges and local access somewhat limits remote exploitation but does not eliminate risk from malicious insiders or attackers with physical access. The confidentiality impact is high, while integrity and availability impacts are limited. Given the medium CVSS score, the threat is moderate but significant in environments with sensitive data and less stringent physical security.

CWE-665Improper Initialization (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
Implementation
Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

solidigm.com/support-page/support-security.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 7 Nov 2025, 21:06 UTC

WeaknessesCWE-665

Technical details

References

Community reviews

Related threats