Skip to main content
CVE-2025-43001VulnerabilityPublished Updated

CVE-2025-43001: SAP_SE SAPCAR · Incorrect Privilege Assignment

Affects SAP_SE SAPCARSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2025-43001, organizations should implement the following specific measures: 1) Restrict SAPCAR usage to trusted administrators and minimize the number of users with high privileges to reduce the attack surface. 2) Monitor and audit the use of SAPCAR, especially archive extraction activities, to detect unusual permission changes or file modifications. 3) Employ file integrity monitoring solutions to alert on unauthorized changes to critical directories and files, particularly those involved in SAP deployments. 4) Enforce strict access controls on directories used by SAPCAR to prevent unauthorized permission overrides. 5) Validate the authenticity and integrity of SAPCAR archives through out-of-band mechanisms beyond signature verification, considering the vulnerability allows tampering without breaking signatures. 6) Stay alert for SAP patches or updates addressing this vulnerability and apply them promptly once available. 7) Conduct regular privilege reviews and enforce the principle of least privilege for all SAP system users. 8) Educate administrators about the risks of privilege escalation via archive extraction tools and encourage secure operational practices. These targeted actions go beyond generic advice by focusing on controlling SAPCAR usage, monitoring for suspicious activity, and preparing for patch deployment.

Description

SAPCAR allows an attacker logged in with high privileges to override the permissions of the current and parent directories of the user or process extracting the archive, leading to privilege escalation. On successful exploitation, an attacker could modify the critical files by tampering with signed archives without breaking the signature, but it has a low impact on the confidentiality and availability of the system.

References

Community reviews

Loading reviews…