Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization

CVE-2026-104845GHSA-jp82-f5mq-hwhp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (seroval 1.6.3), 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.2
    Fixed in
    1.6.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-104845: 0.43% estimated exploitation activity in the next 30 days; percentile 36.94 (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 deserializeTypedArray casts the source node to ArrayBuffer without checking it and never bounds the element count. Pass a plain object with a length property and it hits the array-like TypedArray constructor, allocating that many elements. The offset guard above it can't stop this: source.byteLength is undefined, so the comparison is always false. The length is one integer in the JSON, so a tiny payload can name any allocation size, and it runs synchronously inside fromJSON, starving the event loop instead of just slowing one request. fromCrossJSON is the same. Impact is unauthenticated CPU/memory exhaustion for any service deserializing untrusted Seroval JSON: same profile as the array-length and nested-depth DoS issues already fixed here. No confidentiality or integrity impact. DataView has the same unchecked cast but throws instead of allocating. A runtime instanceof ArrayBuffer check plus a size cap should fix it.

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

    Amended from ghsa record GHSA-jp82-f5mq-hwhp

  2. Revision 2 · amended ·

    Amended from osv record GHSA-jp82-f5mq-hwhp

  3. Revision 1 · created ·

    Published from ghsa record GHSA-jp82-f5mq-hwhp

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-104845

Advisory: Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization
IDs: CVE-2026-104845, GHSA-jp82-f5mq-hwhp
Record: https://patchnext.com/advisories/cve-2026-104845 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm seroval: affected <= 1.6.2; fixed in 1.6.3

## 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-jp82-f5mq-hwhp (GitHub-reviewed advisory GHSA-jp82-f5mq-hwhp lists affected ranges: npm seroval >=0 <=1.6.2)
- Verified: https://osv.dev/vulnerability/GHSA-jp82-f5mq-hwhp (OSV record GHSA-jp82-f5mq-hwhp lists affected ranges: npm seroval >=0 <1.6.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…