Skip to main content
CVE-2025-42971VulnerabilityPublished

CVE-2025-42971: SAP_SE SAPCAR · Out-of-bounds Write

Affects SAP_SE SAPCARSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.0Medium
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:U/C:L/I:L/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

European organizations should implement strict controls on the sources of SAPCAR archives, ensuring only trusted and verified archives are extracted by privileged users. Employing application whitelisting and integrity monitoring on SAPCAR executable and critical system files can help detect unauthorized modifications. Restrict SAPCAR usage to minimal necessary personnel and enforce the principle of least privilege to reduce the risk of exploitation. Monitoring and logging extraction activities can provide early detection of suspicious archive processing. Until an official patch is released, consider sandboxing SAPCAR extraction processes or using virtualized environments to isolate the impact of potential exploitation. Additionally, educating privileged users about the risks of extracting untrusted archives is essential. Organizations should maintain close communication with SAP for timely patch deployment once available.

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.

References

Community reviews

Loading reviews…