# CVE-2025-42966: Insecure Deserialization vulnerability in SAP NetWeaver (XML Data Archiving Service)

> An authenticated administrator can exploit insecure Java deserialization in SAP NetWeaver XML Data Archiving Service to compromise confidentiality, integrity, and availability.

- **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:** 8 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-h8pf-m8cc-p8xp

## What is CVE-2025-42966?

CVE-2025-42966 is a critical unsafe deserialization vulnerability in SAP_SE SAP NetWeaver (XML Data Archiving Service), published on 8 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP NetWeaver XML Data Archiving Service allows an authenticated attacker with administrative privileges to exploit an insecure Java deserialization vulnerability by sending a specially crafted serialized Java object. This could lead to high impact on confidentiality, integrity, and availability of the application.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-42966 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42966 is a critical unsafe deserialization vulnerability in SAP_SE SAP NetWeaver (XML Data Archiving Service), published on 8 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42966 in the wild and no public exploit code.

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

## Sources

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

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