LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23736: seroval Affected by Prototype Pollution via JSON Deserialization

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.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-23736 affects seroval, a JavaScript serialization library. Versions 1.4.0 and below can allow prototype pollution when using JSON deserialization with malicious object keys. The issue is fixed in version 1.4.1. Business urgency is highest for applications that deserialize untrusted or user-controlled JSON through seroval.

Executive priority

Treat as a high-priority dependency update for JavaScript applications that process external JSON. The fix is available, and validation should focus on whether affected seroval versions are present in production and whether JSON deserialization is reachable from untrusted input.

Technical view

The vulnerability is improper input validation in seroval JSON deserialization, classified as CWE-1321 prototype pollution. The CVSS 3.1 score is 7.3, with network attack vector, low complexity, no privileges, and no user interaction. The advisory states only JSON deserialization functionality is affected. A fixing commit and version 1.4.1 are referenced.

Likely exposure

Exposure is likely where applications or dependencies use seroval versions below 1.4.1 and invoke its JSON deserialization functionality on untrusted input. Projects using seroval only for other functionality may have lower exposure, based on the advisory’s scope statement.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not marked as CISA KEV in the bundle. The risk comes from attacker-controlled keys causing prototype pollution during deserialization, which can affect confidentiality, integrity, and availability at low impact levels per CVSS.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and fixing commit. The advisory narrows impact to JSON deserialization. No public source in the bundle indicates exploitation in the wild. Further triage should examine dependency reachability and whether polluted prototypes can influence application security decisions.

Mitigation direction

  • Upgrade seroval to version 1.4.1 or later.
  • Prioritize services that deserialize untrusted JSON with seroval.
  • If upgrade timing is constrained, review vendor advisory for supported guidance.
  • Avoid passing untrusted JSON into affected deserialization paths until remediated.

Validation and detection

  • Inventory direct and transitive seroval dependencies.
  • Confirm deployed versions are 1.4.1 or later.
  • Identify code paths using seroval JSON deserialization.
  • Check whether those paths accept user-controlled or external JSON.
  • Review the referenced fixing commit and advisory for implementation details.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23736 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-23736Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
lxsmnsycseroval< 1.4.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.