Skip to main content
CVE-2025-42989VulnerabilityPublished Updated

CVE-2025-42989: SAP NetWeaver Application Server for ABAP · Missing Authorization

Affects SAP NetWeaver Application Server for ABAPSource CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:C/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 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-25.

What to do

Affected software

ProductAffectedFixed in
SAP_SE SAP NetWeaver Application Server for ABAPAffected
  • =7.93
  • =9.14
  • =9.15
Fixed in–

AI-suggested

To mitigate CVE-2025-42989, organizations should prioritize the following actions: 1) Monitor SAP Security Notes and apply official patches from SAP as soon as they become available for the affected kernel versions. 2) Restrict and tightly control access to SAP RFC interfaces by implementing strict network segmentation and firewall rules to limit inbound RFC traffic to trusted sources only. 3) Enforce strong authentication mechanisms, including multi-factor authentication (MFA), for all SAP users to reduce the risk of credential compromise. 4) Conduct thorough reviews and audits of user roles and authorizations within SAP to minimize excessive privileges and ensure the principle of least privilege is applied. 5) Implement continuous monitoring and anomaly detection on SAP systems to identify unusual RFC activity or privilege escalations promptly. 6) Consider deploying SAP's security tools and logging capabilities to enhance visibility into RFC calls and user actions. 7) Educate SAP administrators and security teams about this vulnerability and the importance of rapid response to suspicious activities. These targeted measures go beyond generic advice by focusing on controlling the specific attack vector and limiting the impact of potential exploitation.

Description

RFC inbound processing�does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. On successful exploitation the attacker could critically impact both integrity and availability of the application.

References

Community reviews

Loading reviews…