CVE-2026-104845: Seroval Memory Exhaustion Vulnerability

HIGH
Advisory Identifier: GHSA-jp82-f5mq-hwhp
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2026-104845 is a HIGH (CVSS 7.5) memory exhaustion vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Seroval libraries in the npm ecosystem. The issue involves memory exhaustion via unchecked typedarray length in json deserialization. Remediation is available by upgrading affected packages to version 1.6.3.

CVE-2026-104845 at a Glance

CVE Identifier CVE-2026-104845
GHSA Identifier GHSA-jp82-f5mq-hwhp
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Seroval
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-104845

To remediate this vulnerability, upgrade all affected Seroval dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

seroval fixed: 1.6.3
npm install seroval@1.6.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls seroval

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-104845, inspect your project dependencies using npm:

npm ls seroval

Analyze the terminal output to locate any version of Seroval in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.6.3), your application is affected.

Note: The npm ls seroval command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Seroval, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# 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.

CVE-2026-104845 Affected Seroval Versions

1 component(s)
Fixed Versions:
1.6.3
Product / Package Ecosystem Affected Versions Fixed Version
seroval
npm
< 1.6.3
1.6.3

References

Frequently Asked Questions

What is CVE-2026-104845?
CVE-2026-104845 is a security vulnerability in Seroval involving Memory exhaustion via unchecked TypedArray length in JSON deserialization under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Seroval versions are affected?
Affected versions include releases prior to 1.6.3 across affected packages: seroval.
What version fixes CVE-2026-104845?
Upgrading to 1.6.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is seroval affected?
Yes, seroval is affected in releases prior to 1.6.3. Upgrade your dependency to 1.6.3 or later.
What is the CVSS score of CVE-2026-104845?
CVE-2026-104845 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-104845?
CVE-2026-104845 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check npm dependencies for CVE-2026-104845?
Run the dependency tree command: 'npm ls seroval'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jp82-f5mq-hwhp",
  "modified" : "2026-10-05T23:40:41Z",
  "published" : "2026-10-05T23:40:40Z",
  "aliases" : [ "CVE-2026-104845" ],
  "summary" : "Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization",
  "details" : "# Summary\n\ndeserializeTypedArray 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.\n\nThe 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.\n\nImpact 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "seroval"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.6.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.6.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lxsmnsyc/seroval/security/advisories/GHSA-jp82-f5mq-hwhp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-104845"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lxsmnsyc/seroval/commit/ac0163e420ac7dcbbefac4d069bcefad300a4851"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lxsmnsyc/seroval/commit/e54a6f62784b9e48e3a5fa2ab4089ca69fb8996e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lxsmnsyc/seroval"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-05T23:40:40Z",
    "nvd_published_at" : "2026-10-02T16:16:47Z"
  }
}