Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:github/lxsmnsyc/seroval

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. From 0.12.0 until 1.6.2, fromJSON deserialization of a fulfilled Promise control node can pass a plugin-produced callable-bearing thenable to a native Promise resolver. ECMAScript thenable assimilation then invokes the callable unexpectedly, allowing attacker-controlled JSON to trigger code in applications using plugin-capable Seroval releases. This path bypasses the Promise resolver type-confusion remediation in version 1.5.3 for CVE-2026-59940 because the unexpected invocation occurs through native Promise settlement after the referenced value is deserialized. This issue is fixed in version 1.6.2.

Join the discussion

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.6.3, deserializeTypedArray in fromJSON and fromCrossJSON trusts a deserialized source value as an ArrayBuffer and does not bound the serialized element count. An attacker can provide a small untrusted JSON object with a large length value, causing the array-like TypedArray constructor to synchronously allocate the selected number of elements and exhaust CPU or memory while starving the event loop. The offset check does not reject the crafted source because source.byteLength is undefined. DataView reaches a similar unchecked cast but throws rather than allocating, and the issue has no identified confidentiality or integrity impact. This issue is fixed in version 1.6.3.

Join the discussion

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.5.3, seroval.fromJSON() allows attacker-controlled JSON Promise control nodes to operate on values from the general deserialization reference table without verifying genuine internal Promise resolver records, causing deserialization side effects with plugins enabled and potentially unintended server-side invocation or remote code execution when downstream frameworks register callable wrappers. This issue is fixed in version 1.5.3.

Join the discussion

CVE-2026-24006 is a high-severity vulnerability in the lxsmnsyc seroval library versions prior to 1.4.1. The issue arises from the lack of limits on resource allocation during serialization of deeply nested JavaScript objects, leading to potential stack overflow and denial of service. The vulnerability does not impact confidentiality or integrity but can cause application crashes, affecting availability. Exploitation requires no privileges or user interaction and can be triggered remotely by processing crafted input. The vulnerability was addressed in version 1.4.1 by introducing a depthLimit parameter that throws an error when exceeded. European organizations using vulnerable versions of seroval in their software stacks, especially those handling complex data serialization, are at risk.

Join the discussion

CVE-2026-23957 is a high-severity vulnerability in the lxsmnsyc seroval library versions prior to 1.4.1. The flaw arises from the allocation of resources without limits or throttling during the deserialization process when an attacker manipulates encoded array lengths to excessively large values. This causes a significant increase in processing time, leading to a denial-of-service (DoS) condition. The vulnerability does not impact confidentiality or integrity but severely affects availability. Exploitation requires no authentication or user interaction and can be triggered remotely over the network. The issue has been resolved in version 1.4.1.

Join the discussion

Showing 1 to 5 of 5 results

Filters:Package: pkg:github/lxsmnsyc/seroval
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses