CVE-2025-57275: n/a
Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 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-25.
What to do
AI-suggested
1. Monitor for official patches or updates from the SPDK project and apply them promptly once released. 2. Restrict network access to NVMe-oF target services using firewalls or network segmentation to limit exposure to trusted hosts only. 3. Implement strict access controls and ensure that only authorized, high-privilege users can interact with the NVMe-oF target component. 4. Conduct thorough input validation and fuzz testing on custom SPDK deployments to identify potential buffer overflow risks. 5. Deploy runtime protections such as Address Space Layout Randomization (ASLR) and stack canaries on systems running SPDK to mitigate exploitation impact. 6. Monitor logs and network traffic for unusual activity targeting NVMe-oF services to detect potential exploitation attempts early. 7. Engage in regular security audits of storage infrastructure components, focusing on third-party libraries like SPDK. 8. Prepare incident response plans specifically addressing storage service disruptions to minimize downtime if exploitation occurs.
Description
Storage Performance Development Kit (SPDK) 25.05 is vulnerable to Buffer Overflow in the NVMe-oF target component in SPDK - lib/nvmf.