# CVE-2025-42992: Multiple Privilege Escalation Vulnerabilities in SAPCAR

> A high-privilege attacker can exploit SAPCAR to escalate privileges by manipulating archive permissions, compromising system integrity.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:H/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:** 26 Feb 2026
- **Also known as:** GHSA-64gg-ww65-9f92

## What is CVE-2025-42992?

CVE-2025-42992 is a medium-severity 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 allows an attacker logged in with high privileges to create a malicious SAR archive in SAPCAR. This could enable the attacker to exploit critical files and directory permissions without breaking signature validation, resulting in potential privilege escalation. This has high impact on integrity, but low impact on confidentiality and availability of the system.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-42992 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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