# CVE-2025-42902: Memory Corruption vulnerability in SAP Netweaver AS ABAP and ABAP Platform

> An unauthenticated attacker can crash the SAP application server by sending corrupted tickets, causing a denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-3hqp-8f7x-pr3q

## What is CVE-2025-42902?

CVE-2025-42902 is a medium-severity vulnerability in SAP_SE SAP Netweaver AS ABAP and ABAP Platform, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to the memory corruption vulnerability in SAP NetWeaver AS ABAP and ABAP Platform, an unauthenticated attacker can send a corrupted SAP Logon Ticket or SAP Assertion Ticket to the SAP application server. This leads to a dereference of NULL which makes the work process crash. As a result, it has a low impact on the availability but no impact on the confidentiality and integrity.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2025-42902 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42902 is a medium-severity vulnerability in SAP_SE SAP Netweaver AS ABAP and ABAP Platform, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42902 in the wild and no public exploit code.

Affected product: SAP_SE SAP Netweaver AS ABAP and ABAP Platform. 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-42902/ (Markdown: https://insights.sbomify.com/CVE-2025-42902/index.md)
```

## Sources

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

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