cve.bz

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

7.3 highEPSS 0.3%Fix available

High (7.3) in lxsmnsyc seroval. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in seroval 1.6.8.

On this page
Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.6.8, fromJSON rebuilds an AsyncIteratorFactoryInstance by calling source.on(listener) without requiring source to be a genuine internal stream. With untrusted Seroval input and an application plugin that returns a callable value or an object exposing an on method, a crafted node can reuse an identifier so the deserializer invokes the plugin-produced value. This is an incomplete-fix variant of CVE-2026-59940. The resulting confidentiality, integrity, or availability impact depends on the behavior exposed by the application plugin. This issue is fixed in version 1.6.8.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-502 Deserialization of Untrusted Data
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

  • seroval (npm): fixed in 1.6.8

Ask an AI about this CVE

Show the promptExplain CVE-2026-116580 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116580?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116580?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-116580 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.6.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7rv5-mrxv-xcr9npmseroval<1.6.81.6.8

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because it enables unauthenticated network attackers to invoke arbitrary application-level callback methods without requiring special privileges. In Red Hat environments such as the Automation Orchestrator web interface, Seroval operates as an internal serialization utility, where exposure requires an endpoint to ingest untrusted serialized structures alongside plugins that register callable objects. The scope of impact is governed by the specific actions performed by those registered plugins, which may result in data modification, information disclosure, or service interruption.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to validate deserialized stream sources directly at the fromJSON deserialization boundary rather than trusting recorded node identifiers: upgrade to seroval 1.6.8 (or the fixed Ansible Automation Platform/Automation Orchestrator Ui Rhel/Forgejo builds), which validate deserialized source objects directly using runtime isSequence and isStream checks rather than trusting recorded node IDs, throwing SerovalMalformedNodeError if validation fails, closing all 2 injection vectors (crafted serialized payload reusing unrecorded node IDs, forged stream or sequence node identifiers). Until patched, this is a concern on applications accepting untrusted Seroval serialized data via fromJSON with plugins returning callables or objects with an on method, so avoid registering Seroval plugins whose deserialize functions return callables or objects with an on method when processing untrusted input. As a compensating measure, enforce strict positive schema validation on incoming serialized structures to reject unexpected node IDs and malformed object graphs. These controls limit blast radius and contain exploitation, but they do not fix the underlying insecure deserialization defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)

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

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-116580.

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