CVE-2026-115897 — 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+4
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Npm Serialize-javascript: fixed in version 7.1.3 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Yahoo Serialize-javascript, Npm Serialize-javascript).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Yahoo | Serialize-javascript | version < 7.1.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Npm | Serialize-javascript | < 7.1.3 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.1 | CVSS 4.0 | Low | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 2.1 | CVSS 4.0 | Low | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.39%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Awaiting Analysis
- Fix documented
- Affected products added · npm/serialize-javascript
- Affected products added · yahoo/serialize-javascript
- Record published
- CVSS changed · 2.1
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 23, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
5 on the record
- github.com/yahoo/serialize-javascript/security/advisories/GHSA-m5mm-p8h7-m29v
- github.com/yahoo/serialize-javascript/pull/235
- github.com/yahoo/serialize-javascript/releases/tag/v7.1.3
- github.com/yahoo/serialize-javascript/commit/2864b3c6260a3bfd52d2db3e70d1a079de1
- github.com/advisories/GHSA-m5mm-p8h7-m29v
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-115754 serialize-javascript 7.0.1 before 7.1.3 XSS via unescaped </script in function body 6d
- Low CVE-2026-97711 Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script> in serialized function bodies Sep 29, 2026
- High CVE-2026-34043 Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects Mar 31, 2026
- Medium CVE-2024-11831 Npm-serialize-javascript: cross-site scripting (xss) in serialize-javascript Feb 10, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-115897 is "Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body", rated Low. It affects Serialize-javascript (Yahoo); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.1 describes technical severity. EPSS 0.31% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.