CVE-2025-42877: SAP Web Dispatcher, Internet Communication Manager and SAP Content Server · Out-of-bounds Write
Affects SAP Web Dispatcher, Internet Communication Manager and SAP Content ServerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% 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 9 Dec 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SE SAP Web Dispatcher, Internet Communication Manager and SAP Content Server | Affected
| Fixed in– |
AI-suggested
Organizations should prioritize the following mitigations: 1) Monitor SAP security advisories closely and apply official patches or updates as soon as they become available for the affected SAP components and versions. 2) Restrict network access to SAP Web Dispatcher, ICM, and Content Server services by implementing strict firewall rules and network segmentation to limit exposure to trusted internal networks only. 3) Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous traffic patterns targeting SAP services. 4) Conduct regular security assessments and penetration testing focused on SAP environments to identify potential exposure and misconfigurations. 5) Harden SAP configurations by disabling unnecessary services and interfaces that could be exploited. 6) Implement robust monitoring and alerting for SAP service availability and unusual memory or process behavior indicative of exploitation attempts. 7) Educate IT and security teams about the vulnerability specifics to ensure rapid response and mitigation. These steps go beyond generic advice by focusing on network-level controls, proactive monitoring, and SAP-specific hardening tailored to the affected components.
Description
SAP Web Dispatcher, Internet Communication Manager (ICM), and SAP Content Server allow an unauthenticated user to exploit logical errors that lead to a memory corruption vulnerability. This results in high impact on the availability with no impact on confidentiality or integrity of the application.