CVSS 3.1
7.3 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LHigh (7.3) in lxsmnsyc seroval. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in seroval 1.6.8.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lseroval (npm): fixed in 1.6.8Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| lxsmnsyc seroval | < 1.6.8 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-7rv5-mrxv-xcr9 | npm | seroval | <1.6.8 | 1.6.8 |
Red Hat rates this Important.
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.
--- 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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Ansible Automation Orchestrator 2026 | ansible-automation-platform/automation-orchestrator-ui-rhel9 | 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-116580.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.