LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23957: seroval is vulnerable to Denial of Service via array serialization

seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, overriding encoded array lengths by replacing them with an excessively large value causes the deserialization process to significantly increase processing time. This issue has been fixed in version 1.4.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-23957 affects seroval, a JavaScript serialization library. Versions 1.4.0 and earlier can spend excessive time deserializing manipulated array length data, causing denial of service. The issue is fixed in 1.4.1. Business urgency is highest for internet-facing services that deserialize untrusted seroval data.

Executive priority

Prioritize remediation for public-facing or multi-tenant systems using seroval to process untrusted input. For internal-only uses with trusted data, urgency is lower but still warrants routine dependency update.

Technical view

seroval before 1.4.1 allows encoded array lengths to be overridden with excessively large values. During deserialization, this can significantly increase processing time. The CVSS 3.1 score is 7.5, reflecting network exploitability, low complexity, no privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure depends on whether applications use seroval versions below 1.4.1 and deserialize attacker-controlled or untrusted serialized values. Dependency use may be direct or transitive in JavaScript projects.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The vulnerability is remotely triggerable under the CVSS assessment when an attacker can supply crafted serialized input to a vulnerable deserialization path.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and fixing commit. No public exploit status is provided. Focus assessment on dependency reachability: vulnerable version presence plus reachable deserialization of attacker-influenced seroval payloads.

Mitigation direction

  • Upgrade seroval to version 1.4.1 or later.
  • Identify direct and transitive seroval dependencies below 1.4.1.
  • Review vendor advisory and commit for update details.
  • Limit deserialization of untrusted seroval data where feasible.

Validation and detection

  • Check package manifests and lockfiles for seroval versions below 1.4.1.
  • Use software composition analysis to find transitive vulnerable dependencies.
  • Confirm deployed builds include seroval 1.4.1 or later.
  • Review application paths that deserialize externally supplied seroval data.
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-770: 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-23957 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.5 (3.1)
Known Exploited
No
Published

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

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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.