# CVE-2025-42928: Deserialization Vulnerability in SAP jConnect - SDK for ASE

> A high-privileged user can exploit a deserialization flaw in SAP jConnect to achieve remote code execution, impacting system 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:** 9 Dec 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-fmh5-rjfp-6qvq

## What is CVE-2025-42928?

CVE-2025-42928 is a critical unsafe deserialization vulnerability in SAP_SE SAP jConnect - SDK for ASE, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Under certain conditions, a high privileged user could exploit a deserialization vulnerability in SAP jConnect to launch remote code execution. The system may be vulnerable when specially crafted input is used to exploit the vulnerability resulting in high impact on confidentiality, integrity and availability of the system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-42928 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42928 is a critical unsafe deserialization vulnerability in SAP_SE SAP jConnect - SDK for ASE, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42928 in the wild and no public exploit code.

Affected product: SAP_SE SAP jConnect - SDK for ASE. 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-42928/ (Markdown: https://insights.sbomify.com/CVE-2025-42928/index.md)
```

## Sources

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

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