# CVE-2025-42958: Missing Authentication check in SAP NetWeaver

> Unauthorized users can read, modify, or delete sensitive data and access privileged functions due to missing authentication checks in SAP NetWeaver.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-r2xh-ghmw-jjjw

## What is CVE-2025-42958?

CVE-2025-42958 is a critical missing authorization vulnerability in SAP_SE SAP NetWeaver, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to a missing authentication check in the SAP NetWeaver application on IBM i-series, the application allows high privileged unauthorized users to read, modify, or delete sensitive information, as well as access administrative or privileged functionalities. This results in a high impact on the confidentiality, integrity, and availability of the application.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2025-42958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42958 is a critical missing authorization vulnerability in SAP_SE SAP NetWeaver, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42958 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver. 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-42958/ (Markdown: https://insights.sbomify.com/CVE-2025-42958/index.md)
```

## Sources

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

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