dbcve.org
SerovalApplication · Lxsmnsyc

CVE-2026-23736

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-21
Fix available
A fix is available. Upgrade to 1.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. This vulnerability affects only JSON deserialization functionality. This issue is fixed in version 1.4.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The seroval library versions 1.4.0 and below contain a prototype pollution vulnerability in its JSON deserialization functionality due to improper input validation. Malicious object keys can be crafted to modify JavaScript object prototypes, potentially leading to code execution or denial of service. The vulnerability is fixed in version 1.4.1.

MitigationUpgrade seroval to version 1.4.1 or later. Review existing code that uses seroval's JSON deserialization to ensure no vulnerable versions are in dependency chains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SerovalApplication
Affected:< 1.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Find installed seroval version
    Run 'npm list seroval' or check package.json/package-lock.json for the seroval version entry under dependencies or devDependencies
    Affected if The listed version is 1.4.0 or lower, or no version is shown but seroval exists in the dependency tree
  2. Identify all seroval occurrences in dependency tree
    Run 'npm ls seroval' to see if seroval appears as a direct or transitive dependency, and note the version resolved for each occurrence
    Affected if Any instance of seroval in the tree is version 1.4.0 or below, including transitive dependencies
  3. Check for seroval parse usage in code
    Search codebase for imports of seroval (import { parse } from 'seroval' or require('seroval')) and usages of the parse method on untrusted input
    Affected if Code uses seroval's parse method to deserialize JSON from untrusted or user-controlled sources
  4. Inspect package-lock.json for pinned vulnerable version
    Search package-lock.json for 'seroval' and locate the 'version' field in its package entry
    Affected if The version field shows 1.4.0 or below for the seroval package entry
  5. Verify seroval is used in runtime environment
    If deploying via Docker or containers, run 'npm list seroval' inside the container or check the installed node_modules in the deployed artifact
    Affected if The runtime environment contains seroval version 1.4.0 or below

You are affected if any seroval instance in your dependency tree is version 1.4.0 or lower and your code passes untrusted input to seroval's parse method for JSON deserialization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.1 or later
Fixed in 1.4.1
Vendor patch github.com →
Interim mitigation

Upgrade seroval to version 1.4.1 or later. Review existing code that uses seroval's JSON deserialization to ensure no vulnerable versions are in dependency chains.

Recommended fix High confidence

seroval 1.4.1

  1. Update seroval to version 1.4.1 or later using your package manager (e.g., npm install [email protected], yarn add [email protected], or pnpm add [email protected])
  2. Verify the installed version matches 1.4.1 or higher (npm list seroval)
  3. Test your application's JSON deserialization functionality to confirm the prototype pollution vulnerability is resolved
  4. Ensure any dependent projects or monorepo packages also receive the updated seroval version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seroval Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,740
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,784.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23736 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data