Skip to main content
Mallory
CriticalVulnerability

CVE-2025-42963: Unsafe Java Deserialization in SAP NetWeaver Log Viewer

Published Jul 8, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.1Critical · v3.1
EPSS0.75%56th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2025-42963CWE-502 · Deserialization of Untrusted Data

CVE-2025-42963 is an unsafe Java object deserialization vulnerability in the SAP NetWeaver Application Server for Java Log Viewer component. An authenticated administrator can upload a malicious serialized object through the diagnostic interface. Inadequate validation allows deserialization to trigger attacker-controlled gadget chains that use Java reflection to invoke java.lang.Runtime.exec(), executing arbitrary operating system commands with sapadm privileges. Successful exploitation can result in full operating system compromise and compromise the confidentiality, integrity, and availability of the application and host environment. Specific affected versions are not available.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary operating system command execution with sapadm privileges and can lead to complete control of the affected host. Both the SAP application and its host environment can suffer loss of confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to SAP applications, particularly Internet exposure, and monitor for unexpected uploads and unusual processes. These measures reduce exposure and support detection but do not replace the security update.

Remediation

Patch, then assume compromise.

Apply the SAP updates associated with Security Note 3621771, issued as part of the July 2025 security updates. Consult the note for applicable releases and installation requirements; specific fixed versions are not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-42963 exploited in the wild?
Yes. As of Oct 10, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-42963?
As of Oct 10, 2026, Mallory has found no public exploit for CVE-2025-42963.
Is there a patch for CVE-2025-42963?
Apply the SAP updates associated with Security Note 3621771, issued as part of the July 2025 security updates. Consult the note for applicable releases and installation requirements; specific fixed versions are not available.
How severe is CVE-2025-42963?
CVE-2025-42963 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.75% (56th percentile) as of Oct 10, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.