# CVE-2025-42970: Directory Traversal vulnerability in SAPCAR

> An attacker can overwrite arbitrary files by tricking a privileged user into extracting a malicious SAPCAR archive, compromising system integrity and availability.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-3ccj-82gj-65cg

## What is CVE-2025-42970?

CVE-2025-42970 is a medium-severity path traversal vulnerability in SAP_SE SAPCAR, published on 8 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SAPCAR improperly sanitizes the file paths while extracting SAPCAR archives. Due to this, an attacker could craft a malicious SAPCAR archive containing directory traversal sequences. When a high privileged victim extracts this malicious archive, it is then processed by SAPCAR on their system, causing files to be extracted outside the intended directory and overwriting files in arbitrary locations. This vulnerability has a high impact on the integrity and availability of the application with no impact on confidentiality.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-42970?


## How do I fix CVE-2025-42970?

No fix has been published for CVE-2025-42970 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42970 being exploited?

There is no known exploitation of CVE-2025-42970 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42970 and fix it if it is affected.

What it is: CVE-2025-42970 is a medium-severity path traversal vulnerability in SAP_SE SAPCAR, published on 8 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-42970 in the wild and no public exploit code.

Affected product: SAP_SE SAPCAR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42970/ (Markdown: https://insights.sbomify.com/CVE-2025-42970/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42970
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42970
- OSV: https://osv.dev/vulnerability/CVE-2025-42970

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42970/
Summaries are generated and may contain mistakes; the official description above is the record.