Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-m5mm-p8h7-m29v

Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body

CVSS 2.3 LowEPSS 0.0031 · 23rd percentile

Published by the GitHub Advisory Database at 23 Oct 2026, 22:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
serialize-javascriptnpm<7.1.37.1.3
Identifiers
GHSA-m5mm-p8h7-m29v · CVE-2026-115754 · CVE-2026-115897
Weakness (CWE)
CWE-79
Tags
Published
23 Oct 2026
Updated
24 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The serialize-javascript npm package, versions before 7.1.3, can emit a function value's source unescaped when that source ends in a bare "</script" with nothing after it in the same body, so output embedded in a script element can break out of it. An attacker would need to control the source text of a serialized function, for example through a spoofed toString(), and could then inject markup such as an image element into the page. Upgrade to serialize-javascript 7.1.3, which escapes this form at the end of a function body.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 23rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.