[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
serialize-javascript	7.0.5 → 7.1.3

---

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

CVE-2026-115897 / GHSA-m5mm-p8h7-m29v

More information

Details

Impact

serialize-javascript escapes its output so it is safe to embed inside a
<script> element. Before 7.1.3 that guarantee did not hold for a function
value whose source ends in a bare </script.

Each function body is escaped on its own, and a bare </script was only
neutralized when followed — within the same body — by a character the HTML
tokenizer treats as ending the tag name (TAB, LF, FF, CR, SPACE, / or >).
A body ending exactly at </script has no following character, so it was
emitted unescaped. The delimiter is then supplied by the surrounding output
(for example the newline the space option emits after the value), and a
later serialized value can supply the closing > followed by markup:

const serialize = require('serialize-javascript');
function f() {} f.toString = () => 'function f(){ return 1 }//</script';
function g() {} g.toString = () => 'function g(x){ return x } > <img src=x onerror=alert(1)>';
serialize({ a: { f }, g }, { space: 2 });
// {
//   "a": {
//     "f": function f(){ return 1 }//</script
//   },
//   "g": function g(x){ return x } > <img src=x onerror=alert(1)>
// }

Embedded in a <script> element, the script ends at the injected tag and the
<img> becomes a live element in the page.

Exploitation requires an attacker to control the source text of a
serialized function, in practice through a spoofed toString(). Real
functions always end in }, so ordinary function values are not affected,
and non-function values (including strings containing </script) are
escaped correctly.

Patches

Fixed in 7.1.3 (#​235). The bare </script form is now also matched at
the end of the function body, so it is escaped regardless of what follows it
in the output.

Workarounds

Upgrade to 7.1.3. If you cannot upgrade, do not serialize function values
whose source text (or toString()) can be influenced by an attacker.

Credits

Reported by ha_kr25 via the Yahoo bug bounty program.

Severity

• CVSS Score: 2.1 / 10 (Low)
• Vector String: 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

References

• https://github.com/yahoo/serialize-javascript/security/advisories/GHSA-m5mm-p8h7-m29v
• https://github.com/yahoo/serialize-javascript/pull/235
• https://github.com/yahoo/serialize-javascript/commit/2864b3c6260a3bfd52d2db3e70d1a079de108a61
• https://github.com/yahoo/serialize-javascript/releases/tag/v7.1.3
• https://github.com/advisories/GHSA-m5mm-p8h7-m29v

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

yahoo/serialize-javascript (serialize-javascript)

v7.1.3

Compare Source

See: GHSA-m5mm-p8h7-m29v

What's Changed

• fix: escape </script at the end of a serialized function body by @​redonkulus in #​235
• Fix serialization of Dates with expanded ISO years by @​Shubham-Padkonde in #​232
• fix: ignore functions without mutating input objects by @​Shubham-Padkonde in #​233
• release: v7.1.3 by @​redonkulus in #​236

Note on ignoreFunction

With ignoreFunction: true, function values are now omitted the same way JSON.stringify omits them, without deleting them from the input object. Functions inside arrays are emitted as null (previously this produced Array.prototype.slice.call(...) output).

New Contributors

• @​Shubham-Padkonde made their first contribution in #​232

Full Changelog: yahoo/serialize-javascript@v7.1.2...v7.1.3

v7.1.2

Compare Source

See: GHSA-gfhx-hw2g-v5hg

v7.1.1

Compare Source

What's Changed

• fix: fix XSS bypass via split </script payload across function bodies by @​okuryu in #​226
• release: v7.1.1 by @​okuryu in #​227

Full Changelog: yahoo/serialize-javascript@v7.1.0...v7.1.1

v7.1.0

Compare Source

What's Changed

• feat: add Node.js 26 to test matrix by @​okuryu in #​224
• release: v7.1.0 by @​okuryu in #​225

Full Changelog: yahoo/serialize-javascript@v7.0.7...v7.1.0

v7.0.7

Compare Source

What's Changed

• fix: reject spoofed RegExp objects with non-string source property by @​redonkulus in #​222
• release: v7.0.7 by @​okuryu in #​223

Full Changelog: yahoo/serialize-javascript@v7.0.6...v7.0.7

v7.0.6

Compare Source

What's Changed

• build(deps-dev): bump lodash from 4.17.23 to 4.18.1 by @​dependabot[bot] in #​215
• fix: reject spoofed URL objects with non-string toString() result by @​redonkulus in #​217
• release: v7.0.6 by @​okuryu in #​221

Full Changelog: yahoo/serialize-javascript@v7.0.5...v7.0.6

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: fb413311-f2fc-4f91-a68c-71b56e80b048

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

📊 Benchmark results

Comparing with 4d59b5c

• Dependency count: 968 (no change)
• Package size: 337 MB (no change)
• Number of ts-expect-error directives: 280 (no change)

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/netlify-cli@8714

commit: 1217be7