LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24006: Seroval affected by Denial of Service via Deeply Nested Objects

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, serialization of objects with extreme depth can exceed the maximum call stack limit. In version 1.4.1, Seroval introduces a `depthLimit` parameter in serialization/deserialization methods. An error will be thrown if the depth limit is reached.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24006 is a denial-of-service issue in Seroval, a JavaScript serialization library. Applications using Seroval versions before 1.4.1 may crash or fail when processing extremely deeply nested objects. The business impact is service availability, not data theft or data modification based on the available sources.

Executive priority

Prioritize remediation for internet-facing or API-heavy services that use Seroval with user-controlled data. This is a high availability risk, but current sources do not indicate data compromise or active exploitation.

Technical view

Seroval 1.4.0 and earlier can exceed the JavaScript maximum call stack while serializing objects with extreme depth. The CVSS 3.1 score is 7.5, with network attack vector, low complexity, no privileges, no user interaction, and high availability impact. Version 1.4.1 adds a depthLimit parameter for serialization and deserialization methods.

Likely exposure

Exposure is most relevant where an application accepts or constructs untrusted, deeply nested object structures and passes them to Seroval serialization or deserialization. Confirm whether Seroval is present directly or transitively in JavaScript dependency trees and whether affected code paths process externally influenced data.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is plausible to trigger remotely where attacker-controlled nested objects reach Seroval, but available sources do not provide exploit-in-the-wild evidence.

Researcher notes

The issue maps to CWE-770 and appears to be uncontrolled resource consumption through recursive depth. The fix introduces configurable depth limiting. Avoid assuming broad reach without confirming whether nested attacker-influenced objects actually flow into Seroval in the target application.

Mitigation direction

  • Upgrade Seroval to version 1.4.1 or later.
  • Review vendor advisory guidance before changing serialization behavior.
  • Use the new depthLimit parameter where appropriate.
  • Reduce acceptance of excessively nested untrusted input where feasible.
  • Rebuild and redeploy affected applications after dependency updates.

Validation and detection

  • Identify direct and transitive Seroval dependencies in application manifests and lockfiles.
  • Confirm deployed versions are 1.4.1 or later.
  • Review code paths using Seroval serialization or deserialization on untrusted data.
  • Check whether depth limits are configured after upgrade.
  • Monitor application errors for stack exhaustion or serialization failures.
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-24006 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-24006Attack 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.