CVE-2025-42928: SAP jConnect – SDK for ASE · Deserialization of Untrusted Data
Affects SAP jConnect – SDK for ASESource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 9.4% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.sap/sap-jconnect-sdk-asepkg:maven/com.sap/sap-jconnect-sdk-aseOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately inventory their SAP jConnect - SDK for ASE deployments to identify affected versions 16.0.4 and 16.1. Until official patches are released, apply the following mitigations: restrict high privileged user access to SAP jConnect components using strict role-based access controls and network segmentation to limit exposure; implement rigorous input validation and sanitization on all data entering the deserialization process; enable detailed logging and monitoring for unusual deserialization activities or unexpected remote code execution attempts; consider deploying application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block malicious payloads targeting deserialization; conduct regular security assessments and penetration testing focused on deserialization vectors; and prepare for rapid patch deployment once SAP releases official fixes. Additionally, educate development and operations teams about the risks of deserialization vulnerabilities and secure coding practices to prevent similar issues.
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.