CVE-2025-42940: SAP CommonCryptoLib · Out-of-bounds Write
Affects SAP CommonCryptoLibSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 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 26 Oct 2026.
What to do
AI-suggested
- Apply SAP vendor patches or updates for CommonCryptoLib CRYPTOLIB 8 as soon as they become available to address the boundary check flaw.
- Implement network-level controls such as firewalls and intrusion prevention systems to restrict access to SAP CommonCryptoLib interfaces, limiting exposure to trusted internal networks or VPNs.
- Conduct regular vulnerability scanning and penetration testing focused on SAP environments to detect unpatched instances and potential attack vectors.
- Monitor network traffic for anomalous ASN.1 data patterns that could indicate exploitation attempts.
- Employ SAP security best practices, including minimizing the attack surface by disabling unnecessary services and interfaces.
- Establish incident response plans specific to SAP service disruptions to ensure rapid recovery in case of denial-of-service events.
- Collaborate with SAP support and security advisories to stay informed about updates and emerging threats related to this vulnerability.
Description
SAP CommonCryptoLib does not perform necessary boundary checks during pre-authentication parsing of manipulated ASN.1 data over the network. This may result in memory corruption followed by an application crash, hence leading to a high impact on availability. There is no impact on confidentiality or integrity.