cve.bz

CVE-2026-116584 lxsmnsyc seroval

7.5 highEPSS 0.4%Fix available

High (7.5) in lxsmnsyc seroval. EPSS 0.4% 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. From 1.4.1 until 1.6.8, fromJSON and fromCrossJSON do not require an array node's element list to be an actual array. A small crafted payload can supply an attacker-controlled length that determines memory allocation and decoder iterations independently of payload size, allowing an unauthenticated request to exhaust the process or block its thread. This issue is a residual bypass of the remediation for CVE-2026-23957. This issue is fixed in version 1.6.8.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
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-116584 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116584?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116584?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-116584 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.4.1, < 1.6.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wp97-x4hv-qvhpnpmseroval>=1.4.1 <1.6.81.6.8

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity for Red Hat environments because unauthenticated remote network access can be leveraged to exhaust application memory or hang execution threads with negligible attacker effort. In Red Hat products utilizing seroval within web application interfaces, the issue affects endpoints that accept and decode untrusted serialized requests prior to authentication or input validation. The impact is strictly confined to service availability, with no compromise of system confidentiality or data integrity.

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 enforce genuine array type validation and length bounds on deserialized node element lists prior to memory allocation or loop processing: upgrade to seroval 1.6.8 (or the fixed Ansible Automation Platform/Automation Orchestrator Ui Rhel/Forgejo builds), which validate node element lists with Array.isArray and throw SerovalMalformedNodeError if validation fails, closing crafted serialized payload with an array-like object containing an arbitrary length property. Until patched, this is a concern on Applications exposing endpoints that decode untrusted seroval serialized data via fromJSON or fromCrossJSON on any platform, so Restrict network exposure of endpoints invoking fromJSON or fromCrossJSON on untrusted input, or require authentication and input filtering prior to deserialization. As a compensating measure, Cap per-process address space and CPU execution time using ulimit or prlimit to contain unbounded memory allocation and thread lockup, Configure service watchdogs and automatic restarts with systemd WatchdogSec and Restart to recover responsive execution when the process exhausts memory or hangs, Restrict deserialization and validate object structures to enforce that array nodes must be true arrays rather than arbitrary objects, Enforce strict type and object graph validation during deserialization to reject non-array nodes declaring arbitrary length properties, and Bound CPU and memory consumption per container or process group using cgroups v2 resource limits to prevent host-wide impact. These controls limit blast radius and contain exploitation, but they do not fix the underlying unvalidated array length deserialization defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (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-116584.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON