# CVE-2025-42971: Memory Corruption vulnerability in SAPCAR

> A memory corruption flaw in SAPCAR allows attackers to cause out-of-bounds reads and writes via malicious archives, leading to unauthorized file extraction or overwriting.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **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-vpw2-377f-3mm6

## What is CVE-2025-42971?

CVE-2025-42971 is a medium-severity memory corruption 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

A memory corruption vulnerability exists in SAPCAR allowing an attacker to craft malicious SAPCAR archives. When a high privileged victim extracts this malicious archive, it gets processed by SAPCAR on their system, resulting in out-of-bounds memory read and write. This could lead to file extraction and file overwrite outside the intended directories. This vulnerability has low impact on the confidentiality, integrity and availability of the application.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2025-42971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42971 is a medium-severity memory corruption 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-42971 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-42971/ (Markdown: https://insights.sbomify.com/CVE-2025-42971/index.md)
```

## Sources

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

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