Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3amended

Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check

CVE-2026-116580GHSA-7rv5-mrxv-xcr9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (seroval 1.6.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm seroval

    Affected
    < 1.6.8
    Fixed in
    1.6.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2026-116580: 0.34% estimated exploitation activity in the next 30 days; percentile 27.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-7rv5-mrxv-xcr9

  2. Revision 1 · created ·

    Published from ghsa record GHSA-7rv5-mrxv-xcr9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-116580

Advisory: Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check
IDs: CVE-2026-116580, GHSA-7rv5-mrxv-xcr9
Record: https://patchnext.com/advisories/cve-2026-116580 (revision 2, source checked 29 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: seroval 1.6.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm seroval: affected < 1.6.8; fixed in 1.6.8

## Suggested inspection (read-only)
- `npm ls seroval --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on seroval.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7rv5-mrxv-xcr9 (GitHub-reviewed advisory GHSA-7rv5-mrxv-xcr9 lists affected ranges: npm seroval >=0 <=1.6.7)
- Verified: https://osv.dev/vulnerability/GHSA-7rv5-mrxv-xcr9 (OSV record GHSA-7rv5-mrxv-xcr9 lists affected ranges: npm seroval >=0 <1.6.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…