cve.bz

CVE-2026-59940 lxsmnsyc seroval: Deserialization of Untrusted Data

9.8 criticalEPSS 0.8%Fix available

Critical (9.8) in lxsmnsyc seroval. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in seroval 1.5.3.

On this page
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.5.3, seroval.fromJSON() allows attacker-controlled JSON Promise control nodes to operate on values from the general deserialization reference table without verifying genuine internal Promise resolver records, causing deserialization side effects with plugins enabled and potentially unintended server-side invocation or remote code execution when downstream frameworks register callable wrappers. This issue is fixed in version 1.5.3.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-08-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-502 Deserialization of Untrusted Data
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-59940 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59940?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59940?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59940 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
lxsmnsyc seroval< 1.5.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mv8w-475r-vwqwnpmseroval<1.5.31.5.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedopencode1.18.26-1.1openSUSE-SU-2026:11673-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

This vulnerability is rated as Critical due to the potential for unauthenticated remote code execution with complete system compromise if an application exposes deserialization routines to untrusted network input. Within Red Hat environments, core platforms do not expose Seroval deserialization endpoints by default, significantly limiting widespread exposure across enterprise deployments. Exploitation specifically requires downstream services to parse untrusted user input using Seroval with callable plugins enabled.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-ui-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59940.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON