Categories
CVE-2026-97711

Cross-Site Scripting (XSS) in serialize-javascript (CVE-2026-97711)

Summary

Cross-site scripting in serialize-javascript (CVE-2026-97711). Risk of unauthorized operations or information disclosure. Exploitable via SCRIPT_CLOSE_REGEXP. Mitigation: upgrade to 7.1.2 or later.

Original description

The description as published by the source.

Impact

serialize-javascript escapes its output so it is safe to embed inside a
element. In 7.1.1 that guarantee does not hold for **function values**: a crafted function body can carry a literal, unescaped
into the output, terminating the script element early so the remainder is
parsed as HTML.

SCRIPT_CLOSE_REGEXP used <\/script[^>]*> as its first alternative. The
character class excludes only >, so a single match could run from one
anywhere in the source — swallowing a second, complete 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 `' }";
const out = serialize({ h: new Function('return ' + src)() });
// {"h":function f(x){ return x< /script=+/ + '' }}


Embedded as the README documents (`window.S = <%= serialize(state) %>`)
and parsed by Chromium, the script element ends at the injected tag and the
`` becomes a live DOM node with its `onerror` handler executing in the
page origin.

Only the function path is affected. The same payload passed as **data** is
escaped correctly, and `options.isJSON` / non-function values are unaffected.

### Patches

Fixed in **7.1.2**. The wildcard now excludes `<` as well as `>`
(`[^<>]*`), so a match can never reach past a second `<`. Every ``, and emits anything
else as text.

### Workarounds

Upgrade to **7.1.2**. If you cannot upgrade, 7.1.0…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-97711 has been found in serialize-javascript.
Attackers can target a specific entry point like SCRIPT_CLOSE_REGEXP over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade serialize-javascript to 7.1.2 or later.
If unsure, ask your IT team or search "serialize-javascript CVE-2026-97711" on the vendor's site.

CVE-2026-97711 (serialize-javascript) — CWE-79
Attack surface: SCRIPT_CLOSE_REGEXP / onerror / options.isJSON
Patched: 7.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in serialize-javascript. Attackers reach the vulnerable code path via SCRIPT_CLOSE_REGEXP.

📍 Affected scope

Check the vendor advisory for the affected versions of serialize-javascript. Attack surface: SCRIPT_CLOSE_REGEXP / onerror / options.isJSON.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'serialize-javascript' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'serialize-javascript' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で serialize-javascript を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade serialize-javascript to 7.1.2

    ステージング環境で 7.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm serialize-javascript
[{"type":"SEMVER","events":[{"introduced":"7.1.1"},{"fixed":"7.1.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details