Loading vulnerability…
CVE-2025-13425 is an out-of-bounds slice access in OSV-SCALIBR's filesystem traversal fallback path. The directory-iteration Next() method assumes that a directory-entry slice contains an element after ReadDir returns nil for an empty directory. It indexes the empty slice, causing a Go runtime panic with an index-out-of-range condition.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) exploit for CVE-2025-13425, a vulnerability in Google's osv-scalibr project. The vulnerability is triggered when the application processes a VMDK (Virtual Machine Disk) file containing at least one empty directory, leading to a segmentation fault (nil pointer dereference) and application crash. The repository contains four files: a LICENSE, a README.md with detailed exploitation instructions, a bash script (gen_malicious_vmdk.sh) to generate a malicious VMDK file, and a Go patch (vmdk.go.patch) to modify the osv-scalibr source code for demonstration purposes. The exploit is local in nature, requiring the attacker to supply a crafted VMDK file to the vulnerable application. No network endpoints or remote services are involved. The main exploit capability is denial of service via application crash, but the underlying bug could potentially be leveraged for further exploitation depending on the application's context and privileges. The repository is structured to guide the user through reproducing the vulnerability, including patching the source, building the binary, generating the payload, and triggering the crash.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.