Security fix · CVE-2026-115897
Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body
Published Oct 23, 2026 · catalog updated Oct 23, 2026 · Red Hat Red Hat Enterprise Linux
Last checked Oct 25, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-115897. EPSS is 0.31%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-57845 · High
- CVE-2026-115754 · Medium
- CVE-2026-115730 · Low
- CVE-2026-55888 · High
- CVE-2026-55889 · Medium
- Severity
- Medium4.4
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.31%
- Remediation
- Version ranges on file
- Affected products
- npm serialize-javascript
### Impact escapes its output so it is safe to embed inside a element. Before 7.1.3 that guarantee did not hold for a **function value whose source ends in a bare **. Each function body is escaped on its own, and a bare 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 has no following character, so it was emitted unescaped. The delimiter is then supplied by the surrounding output (for example the newline the option emits after the value), and a later serialized value can supply the closing followed by markup: Embedded in a element, the script ends at the injected tag and the 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 . Real functions always end in , so ordinary function values are not affected, and non-function values (including strings containing ) are escaped correctly. ### Patches Fixed in **7.1.3** (#235). The bare 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 ) can be influenced by an attacker. ### Credits Reported by **ha_kr25** via the Yahoo bug bounty program.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- npm serialize-javascript0 → 7.1.3
- npm serialize-javascript< 7.1.3
How to fix CVE-2026-115897
Upgrade
CVE-2026-115897 lists a fix boundary at 7.1.3. Compare the installed build with that boundary before you change production.
Version check
Affected < 7.1.3
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-115897. EPSS is 0.31%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.
Which versions are affected?
Compare what you have installed with 0 → 7.1.3, < 7.1.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-79: Cross-site Scripting (XSS). EPSS 0.31%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · GitHub Advisory Database
Detected
### Impact escapes its output so it is safe to embed inside a element. Before 7.1.3 that guarantee did not hold for a **function value whose source ends in a bare **. Each function body is escaped on its own, and a bare 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
Oct 23, 2026 · GitHub Advisory Database
Fix available
serialize-javascript fixed in 7.1.3
Oct 23, 2026 · GitHub Advisory Database
Fix available
serialize-javascript fixed in 7.1.3
Oct 23, 2026 · GitHub Advisory Database
Updated
### Impact escapes its output so it is safe to embed inside a element. Before 7.1.3 that guarantee did not hold for a **function value whose source ends in a bare **. Each function body is escaped on its own, and a bare 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
Sources
- CVE.orgVulnerability recordCVE-2026-115897
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-115897
30-day exploitation probability 0.31%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-m5mm-p8h7-m29v
Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-115897
serialize-javascript escapes its output so it is safe to embed inside a 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, …
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-m5mm-p8h7-m29v
Serialize JavaScript: Cross-site scripting (XSS) via unescaped </script at the end of a serialized function body
osv.dev - Red Hat Security DataVendor advisoryCVE-2026-115897
serialize-javascript: serialize-javascript: Cross-Site Scripting via improper function escaping
access.redhat.com
References
Freshness
Last verified in this catalog Oct 25, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitLab Advisory DatabaseOct 25, 2026
- FIRST EPSSOct 25, 2026
- CVE.orgOct 24, 2026
- GitHub Advisory DatabaseOct 24, 2026
- Red Hat Security DataOct 24, 2026
- OpenSSF OSV / OSV ScannerOct 24, 2026