CVE-2025-42876: SAP S/4 HANA Private Cloud (Financials General Ledger) · Asymmetric Resource Consumption
Affects SAP S/4 HANA Private Cloud (Financials General Ledger)Source CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SE SAP S/4 HANA Private Cloud (Financials General Ledger) | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-42876, European organizations should immediately review and tighten role-based access controls within SAP S/4 HANA Private Cloud, ensuring that users are restricted strictly to their authorized company codes. Conduct thorough audits of user permissions and cross-company code access rights to detect and remediate any over-privileged accounts. Implement continuous monitoring and alerting for unusual access patterns or document modifications across company codes. Apply SAP-provided patches or security updates as soon as they become available, even if no exploits are currently known. Consider deploying additional compensating controls such as SAP Security Audit Logs and SAP Enterprise Threat Detection to identify suspicious activities early. Educate SAP administrators and users about the risks of privilege escalation and enforce the principle of least privilege. Regularly test and validate authorization configurations in non-production environments to prevent similar authorization bypass issues. Finally, coordinate with SAP support and security teams to stay informed about updates and advisories related to this vulnerability.
Description
Due to a Missing Authorization Check vulnerability in SAP S/4 HANA Private Cloud (Financials General Ledger), an authenticated attacker with authorization limited to a single company code could read sensitive data and post or modify documents across all company codes. Successful exploitation could result in a high impact to confidentiality and a low impact to integrity, while availability remains unaffected.