CVE-2025-42992: SAP_SE SAPCAR · Incorrect Privilege Assignment
Affects SAP_SE SAPCARSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% 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:LExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-42992, organizations should implement strict access controls limiting SAPCAR usage to only trusted administrators and monitor usage logs for suspicious activity. Until SAP releases official patches, consider restricting SAPCAR execution to dedicated, isolated environments with minimal user access. Employ rigorous privilege management to ensure only necessary users have high-level privileges capable of exploiting this vulnerability. Regularly audit SAR archives and verify their integrity beyond signature validation, using additional file integrity monitoring tools. Implement network segmentation to isolate SAP systems and reduce the risk of lateral movement. Educate administrators about the risks of creating or deploying unverified SAR archives. Once SAP patches are available, apply them promptly. Additionally, maintain up-to-date backups and incident response plans tailored for SAP environments to quickly recover from potential exploitation.
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.