CVE Watch14 jul 2026

CVE-2026-26210

KTransformers through 0.5.3 contains an unsafe deserialization vulnerability in the balance_serve backend mode where the scheduler RPC serve

CVSS

9.8

Crítico

EPSS

0.7%

p49

KEV

—

Exploit Today

0-100

Publicado: 23 abr 2026 · Última mod.: 14 jul 2026 · CWE-502

EPSS · 30d

0.7%EPSS · 30 días0.7%

2026-06-302026-07-17

Descripción técnica

KTransformers through 0.5.3 contains an unsafe deserialization vulnerability in the balance_serve backend mode where the scheduler RPC server binds a ZMQ ROUTER socket to all interfaces with no authentication and deserializes incoming messages using pickle.loads() without validation. Attackers can send a crafted pickle payload to the exposed ZMQ socket to execute arbitrary code on the server with the privileges of the ktransformers process.

Referencias oficiales

CVEs relacionados

CVECVSSEPSSKEVRExplotTítuloVis.

CVE-2021-422379.8 CRÍ

99.9%

KEV—80Sitecore XP Remote Command Execution Vulnerability8d CVE-2026-456598.8 ALT

86.8%

KEV—76Microsoft SharePoint Server Deserialization of Untrusted Data Vulnerability15d CVE-2026-586449.8 CRÍ

70.7%

KEV—71Microsoft SharePoint Deserialization of Untrusted Data Vulnerability17h CVE-2026-125699.8 CRÍ

66.0%

KEV—70PTC Windchill and FlexPLM Improper Input Validation Vulnerability17d CVE-2026-505229.8 CRÍ

97.2%

——29Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a network.2d CVE-2025-560059.8 CRÍ

96.7%

——29An undocumented and unsafe feature in the PLY (Python Lex-Yacc) library 3.11 allows Remote Code Execution (RCE) via the `picklefile` parameter in the `yacc()` function. This parameter accepts a `.pkl` file that is deserialized with `pickle.load()` without validation. Because `pickle` allows execution of embedded code via `__reduce__()`, an attacker can achieve code execution by passing a malicious pickle file. The parameter is not mentioned in official documentation or the GitHub repository, yet it is active in the PyPI version. This introduces a stealthy backdoor and persistence risk. NOTE: A third-party states that this vulnerability should be rejected because the proof of concept does not demonstrate arbitrary code execution and fails to complete successfully.3d