Serialize Javascript
Approved changes feed: RSS · Atom
cpe:2.3:a:yahoo:serialize-javascript:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Yahoo (0dc01c4f-a37d-56de-8e72-74e1c6cb3fab) |
|---|---|
| Product | Serialize Javascript (5a8663ab-9972-51ca-af74-1023529827ce) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-115754 |
vulnerable | 2026-11-03 10:15:37.770492 |
serialize-javascript 7.0.1 before 7.1.3 XSS via unescaped </script in function body
MEDIUM (4.7)
serialize-javascript from 7.0.1 before 7.1.3 contains a cross-site scripting vulnerability that allows attackers to break out of HTML script elements by ending serialized function source text with an unescaped </script. Attackers controlling a function's source via a spoofed toString() can combine surrounding output delimiters and later values to inject live markup such as img onerror handlers.
Published: 2026-10-23T13:20:43.932Z
Updated: 2026-10-23T14:58:11.402Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-115897 |
vulnerable | 2026-11-03 10:15:37.502710 |
Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body
Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.
Published: 2026-10-23T21:37:41.097Z
Updated: 2026-10-26T17:41:50.594Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34043 |
vulnerable | 2026-06-08 07:59:11.701597 |
Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects
MEDIUM (5.9)
Serialize JavaScript to a superset of JSON that includes regular expressions and functions. Prior to version 7.0.5, there is a Denial of Service (DoS) vulnerability caused by CPU exhaustion. When serializing a specially crafted "array-like" object (an object that inherits from Array.prototype but has a very large length property), the process enters an intensive loop that consumes 100% CPU and hangs indefinitely. This issue has been patched in version 7.0.5.
Published: 2026-03-31T01:48:45.759Z
Updated: 2026-03-31T13:55:54.998Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-16769 |
vulnerable | 2026-06-08 05:13:09.357222 |
Affected versions of serialize-javascript are vulnerable to Cross-site Scripting (XSS)
MEDIUM (4.2)
The serialize-javascript npm package before version 2.1.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.
Published: 2019-12-05T18:55:15.000Z
Updated: 2024-08-05T01:24:47.226Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.