# CVE-2025-42994: Multiple vulnerabilities in SAP MDM Server

> An attacker can cause a denial of service in SAP MDM Server by sending crafted packets that trigger a memory access violation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-2wc8-2pc2-v659

## What is CVE-2025-42994?

CVE-2025-42994 is a high-severity denial of service vulnerability in SAP_SE SAP MDM Server, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP MDM Server ReadString function allows an attacker to send specially crafted packets which could trigger a memory read access violation in the server process that would then fail and exit unexpectedly causing high impact on availability with no impact on confidentiality and integrity of the application.

Weakness: CWE-590 (Free of Memory not on the Heap)

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


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

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

## Is CVE-2025-42994 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42994 is a high-severity denial of service vulnerability in SAP_SE SAP MDM Server, published on 10 Jun 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-42994 in the wild and no public exploit code.

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

## Sources

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

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