dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-42966

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Insecure Java deserialization vulnerability in SAP NetWeaver XML Data Archiving Service allows authenticated attackers with administrative privileges to execute arbitrary code via specially crafted serialized Java objects, leading to complete compromise of confidentiality, integrity, and availability.

MitigationApply SAP security patches for CVE-2025-42966 immediately; until patch is available, restrict administrative access strictly and monitor for suspicious serialized object traffic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP NetWeaver installation and version
    Check your SAP system for installed NetWeaver components. Use SAP transaction SM37 or check the SAP system landscape directory for NetWeaver version information. Query the SAP system for installed software components related to 'SAP NetWeaver' and 'XML Data Archiving Service'.
    Affected if SAP NetWeaver is installed and the version falls within unpatched releases containing the vulnerable XML Data Archiving Service component
  2. Verify XML Data Archiving Service is enabled
    Check SAP configuration for the XML Data Archiving Service module. Use SAP transaction SRT_UTIL or check the SAP Gateway service listings for 'XML Data Archiving' or 'XDAS' related services. Inspect the SAP system for active web services or RFC-enabled functions related to XML data archiving.
    Affected if The XML Data Archiving Service is active or exposed in the SAP environment
  3. Review administrative user privileges
    Audit administrative accounts with access to SAP NetWeaver administration. Use SAP transaction SUIM to query users with profiles such as SAP_ALL, SAP_NEW, or administrative roles. Check role assignments for users with privileges to manage archiving services or execute Java serialized objects.
    Affected if Multiple users or overly privileged administrative accounts exist with access to the vulnerable service
  4. Inspect logging for serialized object traffic
    Review SAP Gateway logs and system traces for incoming serialized Java object requests. Check SAP transaction SM37, ST03N, or the SAP logs directory for unusual serialized object traffic patterns targeting archiving services. Look for logs indicating deserialization of Java objects in XML Data Archiving Service endpoints.
    Affected if Log analysis reveals deserialization activity or serialized object traffic to archiving services from untrusted sources
  5. Check for applied security patches
    Query the SAP system for installed patches related to CVE-2025-42966. Use SAP transaction SPAM to review applied support packages. Check SAP note references for CVE-2025-42966 or the associated security patch in your system.
    Affected if No SAP security patch for CVE-2025-42966 has been applied to the NetWeaver installation

A user is affected if SAP NetWeaver with XML Data Archiving Service is present, the service is enabled, administrative access is not strictly controlled, and the CVE-2025-42966 security patch has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for CVE-2025-42966 immediately; until patch is available, restrict administrative access strictly and monitor for suspicious serialized object traffic.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
38.0 hours of engineering $6,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,368.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-42966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-42966 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data