/

CVE-2026-75987

Severity:

HIGH RISK

(7.3)

Unsafe Deserialization (CWE-502) in SPLWare esProc

CVE-2026-75987

Deferred

Vulnerability type

Category:

Unsafe Deserialization

CWE:

CWE-20, CWE-502

Impact:

Potential Remote Code Execution

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

SPLWare esProc contains a deserialization vulnerability in the ObjectInputStream.readUnshared handling within SocketData.java. Under conditions where an attacker can reach the affected communication path and provide crafted serialized data, the issue may enable unauthorized object deserialization and potentially remote code execution.

Affected context

The vulnerability affects SPLWare esProc deployments using the parallel socket communication functionality implemented in src/main/java/com/scudata/parallel/SocketData.java. Risk depends on whether the affected service is remotely reachable and accepts attacker-influenced serialized input without adequate authentication, validation, or trust-boundary controls. The reported affected range includes versions up to 20260507.

Exploit preconditions

  • Attack surface: The esProc parallel socket communication interface
  • Required access: Network reachability to an exposed affected service; authentication requirements depend on deployment configuration
  • Trigger point: Processing of serialized data through ObjectInputStream.readUnshared
  • Why exploitation is possible: Serialized input may be deserialized without sufficiently restricting the classes or object structures that can be processed

Why this happens

The underlying issue is the use of Java native object deserialization on data that may cross a remote trust boundary. ObjectInputStream.readUnshared can reconstruct object graphs from serialized input, and unrestricted deserialization may invoke dangerous classes or behaviors available in the runtime environment. This maps primarily to CWE-502: Deserialization of Untrusted Data; insufficient validation of the received data also relates to CWE-20: Improper Input Validation.

Potential impact

  • An attacker may execute code within the esProc service process
  • The affected service could be compromised or disrupted
  • Confidential data accessible to the service may be exposed
  • An attacker could use the compromised process for further movement within the network
  • Serialized input processing could cause resource exhaustion or denial of service

General mitigation guidance

Mitigation generally focuses on removing native deserialization from remotely reachable interfaces or strictly constraining what can be deserialized.

Common defensive patterns include:

  • Prefer explicit, schema-based data formats and allowlisted message types over native Java object serialization
  • Apply strict class filtering and object input filters when deserialization cannot be removed
  • Treat network-provided serialized data as untrusted regardless of its source
  • Require authentication and authorization before reaching deserialization code
  • Limit service-account permissions, filesystem access, and network privileges
  • Isolate the processing service and use resource limits to reduce blast radius
  • Avoid exposing parallel communication endpoints directly to untrusted networks

How teams detect issues like this

Detection approaches may include:

  • Static analysis searches for ObjectInputStream, readObject, and readUnshared on network-derived streams
  • Code review checks for deserialization before authentication, authorization, or class filtering
  • Dependency and runtime inventory reviews identifying services that expose Java serialization endpoints
  • Network monitoring for unexpected connections to parallel or socket service ports
  • Policy enforcement requiring approved serialization formats and object-input filtering
  • Automated security scanners and code-review tools can help identify unsafe deserialization patterns

Sources

SourceLink
github.comgithub.com/SPLWare/esProc/
github.comgithub.com/SPLWare/esProc/issues/67
vuldb.comvuldb.com/cve/CVE-2026-75987
vuldb.comvuldb.com/submit/877849
vuldb.comvuldb.com/vuln/391906
vuldb.comvuldb.com/vuln/391906/cti

Frequently asked

questions

Yes, the report indicates that remote exploitation is possible when an attacker can reach the affected communication path and submit data that the service processes.

The available information does not establish a universal authentication requirement. Exploitability depends on whether the endpoint is exposed and what authentication and authorization controls the deployment applies.

The safest pattern is to replace native Java deserialization with an explicit, schema-based format. If deserialization must remain, use strict class allowlisting and object-input filtering before processing untrusted data.

Track all deserialization boundaries, enforce secure serialization policies in code review and CI, restrict network exposure, require authentication, and run services with least privilege.

Find out what's already
exploitable in your codebase.