cve.bz

CVE-2026-116581 lxsmnsyc seroval: Infinite Loop

7.5 highEPSS 0.5%Fix available

High (7.5) in lxsmnsyc seroval. EPSS 0.5% 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 and fromCrossJSON do not validate a sequence node's done index. A crafted done index can create an iterator that never finishes when application code consumes it to completion. An unauthenticated request to a service that deserializes untrusted input can therefore block the event loop, exhaust process memory, or make the service unavailable. 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.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th 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: partial, assessed 2026-10-31. 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-835 Loop with Unreachable Exit Condition (Infinite Loop)
CWE-1284 Improper Validation of Specified Quantity in Input
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-116581 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116581?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116581?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-116581 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-97r2-qh9m-474hnpmseroval<1.6.81.6.8

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is classified as Important because remote, unauthenticated attackers can trigger complete process hangs and memory exhaustion without needing prior permissions or user assistance. In Red Hat products incorporating affected components, exposed endpoints that parse client-supplied serialized structures can be rendered entirely unresponsive. Environments isolating these interfaces behind access control proxies or restricting reachability to trusted private networks significantly reduce the practical likelihood of unauthorized disruption.

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 strict integer and bounds validation on sequence done and throw indices during seroval deserialization before iterator consumption: upgrade to seroval 1.6.8 (or the fixed Ansible Automation Platform/Automation Orchestrator Ui Rhel/Forgejo builds), which validate sequence node throw and done indices as integers within element array bounds using isSequenceIndex and throw SerovalMalformedNodeError on malformed nodes, closing all 3 injection vectors (crafted sequence done index in serialized payload, crafted sequence throw index in serialized payload, unvalidated array node element lists in serialized payload). Until patched, this is a concern on applications deserializing untrusted input using serovals fromJSON or fromCrossJSON APIs and consuming sequence iterators to completion, so isolate affected deserialization endpoints behind access control proxies, restrict network access to trusted private networks, and avoid consuming untrusted serialized sequence iterators to completion. As a compensating measure, impose process-level address space and CPU limits using ulimit or prlimit to bound resource exhaustion from unbounded sequence iterators and configure service watchdogs and automatic restarts via systemd WatchdogSec and Restart directives to recover from event loop hangs. These controls limit blast radius and contain exploitation, but they do not fix the underlying unvalidated sequence index 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-116581.

References

Check your stackJSON