Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

Serialize JavaScript: Cross-site scripting (XSS) via unescaped in serialized function bodies

CVE-2026-97711GHSA-gfhx-hw2g-v5hg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (serialize-javascript 7.1.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.3 · 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 · score source
EPSS
  • CVE-2026-97711: 0.32% estimated exploitation activity in the next 30 days; percentile 24.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact serialize-javascript escapes its output so it is safe to embed inside a <script element. In 7.1.1 that guarantee does not hold for function values: a crafted function body can carry a literal, unescaped </script into the output, terminating the script element early so the remainder is parsed as HTML. SCRIPTCLOSEREGEXP used <\/script[^] as its first alternative. The character class excludes only , so a single match could run from one </script all the way to the next anywhere in the source — swallowing a second, complete </script along the way. Only one replacement is emitted per match, and the plain-code branch neutralizes just the leading < ('< ' + match.slice(1)), so the swallowed tag was re-emitted verbatim. Reaching that shape requires </script in code position, which is legal JavaScript: x</script=+/ parses as x < /script=+/, a comparison against a regex literal. Embedded as the README documents (<scriptwindow.S = <%= serialize(state) %</script) and parsed by Chromium, the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-gfhx-hw2g-v5hg

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-gfhx-hw2g-v5hg

  4. Revision 1 · created ·

    Published from ghsa record GHSA-gfhx-hw2g-v5hg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-97711

Advisory: Serialize JavaScript: Cross-site scripting (XSS) via unescaped in serialized function bodies
IDs: CVE-2026-97711, GHSA-gfhx-hw2g-v5hg
Record: https://patchnext.com/advisories/cve-2026-97711 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: serialize-javascript 7.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm serialize-javascript: affected >= 7.1.1, < 7.1.2; fixed in 7.1.2

## Suggested inspection (read-only)
- `npm ls serialize-javascript --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on serialize-javascript.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gfhx-hw2g-v5hg (GitHub-reviewed advisory GHSA-gfhx-hw2g-v5hg lists affected ranges: npm serialize-javascript >=7.1.1 <7.1.2)
- Verified: https://osv.dev/vulnerability/GHSA-gfhx-hw2g-v5hg (OSV record GHSA-gfhx-hw2g-v5hg lists affected ranges: npm serialize-javascript >=7.1.1 <7.1.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…