# CVE-2025-42989: Missing Authorization check in SAP NetWeaver Application Server for ABAP

> An authenticated attacker can exploit missing authorization checks in RFC processing to escalate privileges and compromise integrity and availability.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-p85x-xv8x-v67q

## What is CVE-2025-42989?

CVE-2025-42989 is a critical missing authorization vulnerability in SAP_SE SAP NetWeaver Application Server for ABAP, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-42989?


## How do I fix CVE-2025-42989?

No fix has been published for CVE-2025-42989 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42989 being exploited?

There is no known exploitation of CVE-2025-42989 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42989 and fix it if it is affected.

What it is: CVE-2025-42989 is a critical missing authorization vulnerability in SAP_SE SAP NetWeaver Application Server for ABAP, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42989 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver Application Server for ABAP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42989/ (Markdown: https://insights.sbomify.com/CVE-2025-42989/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42989
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42989
- OSV: https://osv.dev/vulnerability/CVE-2025-42989

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42989/
Summaries are generated and may contain mistakes; the official description above is the record.