{"answers":{"affected":"3 open source packages ship an affected version, including spdk.","exploited":"There is no known exploitation of CVE-2025-57275 in the wild and no public exploit code.","fix":"Upgrade spdk to 25.9 or later.","what":"CVE-2025-57275 is a medium-severity memory corruption vulnerability in n/a, published on 1 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-57275 and fix it if it is affected.\n\nWhat it is: CVE-2025-57275 is a medium-severity memory corruption vulnerability in n/a, published on 1 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-57275 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- spdk (PyPI): affected all versions; fixed in 25.9\n- spdk (PyPI): affected all versions; fixed in 25.9\n- spdk (PyPI): affected all versions; fixed in 25.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-57275/ (Markdown: https://insights.sbomify.com/CVE-2025-57275/index.md)","id":"CVE-2025-57275","markdown":"https://insights.sbomify.com/CVE-2025-57275/index.md","name":"CVE-2025-57275","record":{"aliases":["GHSA-5m5w-w2h2-fqgq","OESA-2025-2523","OESA-2025-2524","OESA-2025-2525","OESA-2025-2692","OESA-2025-2693","PYSEC-2026-1935"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SPDK NVMe-oF target","requires_auth":"high_privilege","summary":"A buffer overflow in the SPDK NVMe-oF target allows attackers to execute arbitrary code or cause denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Storage Performance Development Kit (SPDK) 25.05 is vulnerable to Buffer Overflow in the NVMe-oF target component in SPDK - lib/nvmf.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SPDK is vulnerable to buffer overflow in the NVMe-oF target component","id":"CVE-2025-57275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-57278"},"packages":[{"ecosystem":"PyPI","fixed":["25.9"],"introduced":["0"],"last_affected":[],"package":"spdk","purl":null,"source":"GHSA-5m5w-w2h2-fqgq"},{"ecosystem":"PyPI","fixed":["25.9"],"introduced":["0"],"last_affected":[],"package":"spdk","purl":"pkg:pypi/spdk","source":"GHSA-5m5w-w2h2-fqgq"},{"ecosystem":"PyPI","fixed":["25.9"],"introduced":["0"],"last_affected":[],"package":"spdk","purl":"pkg:pypi/spdk","source":"PYSEC-2026-1935"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-57266"},"products":["n/a"],"published":"2025-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"A buffer overflow in the SPDK NVMe-oF target allows attackers to execute arbitrary code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2025-57275/"}