GHSA-7RV5-MRXV-XCR9
Vulnerability from github – Published: 2026-10-28 21:17 – Updated: 2026-10-28 21:17Summary
When fromJSON rebuilt an async iterator, it called on() on the iterator's source without checking that the source was a seroval stream. A crafted payload could pick another value as the source, such as a function returned by an application plugin. The deserializer then called that value's on method.
This is a variant of GHSA-mv8w-475r-vwqw. That fix covered the promise and stream control nodes but not the async iterator node.
Impact
An application that passes untrusted input to fromJSON with plugins that return callable values can have those callables invoked during deserialization. What this allows depends on what the plugin's values do.
Affected versions
- Versions up to 1.6.3 accept any value as the source.
- 1.6.4 rejects the reported payload.
- 1.6.5 to 1.6.7 check the source by node type, which a payload can get around by reusing a node id.
- All versions up to 1.6.7 should be treated as affected.
Patches
Fixed in seroval@1.6.8. Streams and sequences are now internal class instances. The deserializer checks the source value with instanceof, so plain data and plugin values are rejected no matter which node id they use.
Workarounds
Avoid plugins whose deserialize returns functions or objects with an on method when decoding untrusted input. Upgrading to 1.6.8 is recommended.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.6.7"
},
"package": {
"ecosystem": "npm",
"name": "seroval"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.6.8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-116580"
],
"database_specific": {
"cwe_ids": [
"CWE-502"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-28T21:17:15Z",
"nvd_published_at": "2026-10-26T21:18:15Z",
"severity": "HIGH"
},
"details": "### Summary\n\nWhen `fromJSON` rebuilt an async iterator, it called `on()` on the iterator\u0027s source without checking that the source was a seroval stream. A crafted payload could pick another value as the source, such as a function returned by an application plugin. The deserializer then called that value\u0027s `on` method.\n\nThis is a variant of GHSA-mv8w-475r-vwqw. That fix covered the promise and stream control nodes but not the async iterator node.\n\n### Impact\n\nAn application that passes untrusted input to `fromJSON` with plugins that return callable values can have those callables invoked during deserialization. What this allows depends on what the plugin\u0027s values do.\n\n### Affected versions\n\n- Versions up to 1.6.3 accept any value as the source.\n- 1.6.4 rejects the reported payload.\n- 1.6.5 to 1.6.7 check the source by node type, which a payload can get around by reusing a node id.\n- All versions up to 1.6.7 should be treated as affected.\n\n### Patches\n\nFixed in `seroval@1.6.8`. Streams and sequences are now internal class instances. The deserializer checks the source value with `instanceof`, so plain data and plugin values are rejected no matter which node id they use.\n\n### Workarounds\n\nAvoid plugins whose `deserialize` returns functions or objects with an `on` method when decoding untrusted input. Upgrading to 1.6.8 is recommended.",
"id": "GHSA-7rv5-mrxv-xcr9",
"modified": "2026-10-28T21:17:15Z",
"published": "2026-10-28T21:17:15Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/lxsmnsyc/seroval/security/advisories/GHSA-7rv5-mrxv-xcr9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116580"
},
{
"type": "WEB",
"url": "https://github.com/lxsmnsyc/seroval/commit/3edc78b495ea0d6bd498143e5b3e56996607c5f2"
},
{
"type": "WEB",
"url": "https://github.com/lxsmnsyc/seroval/commit/50926b3ee198fb757e6ce3aa70efeed38d931c8d"
},
{
"type": "PACKAGE",
"url": "https://github.com/lxsmnsyc/seroval"
},
{
"type": "WEB",
"url": "https://github.com/lxsmnsyc/seroval/releases/tag/seroval@1.6.8"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.