Skip to content
Fencer Intel
low 2.1

CVE-2026-115897 json

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

published 17d ago modified 14d ago also EUVD-2026-109190

cvss
2.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.

Patch / fix

  • verizon serialize-javascript 7.1.3
  • agama-web-ui openSUSE Tumbleweed 25+475.275dd4727-56.1

opensuse advisories openSUSE-SU-2026:12424-1

Is CVE-2026-115897 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-115897 updated cvss 4.4

serialize-javascript: serialize-javascript: Cross-Site Scripting via improper function escaping

  • Red Hat Hardened Images grafana12.4 12.4.13-0.6.hum1
    fixed: vendor fix RHSA-2026:93601
  • Red Hat Hardened Images dotnet10.0 10.0.113-1.hum1, dotnet8.0 8.0.132-0.1.hum1, dotnet9.0 9.0.122-0.1.hum1, grafana13.1 13.1.8-0.4.hum1, grafana13.2 13.2.4-0.3.hum1, prometheus3.13 3.13.5-0.1.hum1
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
14d ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 2.1 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
CNA 4.0 2.1 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • yahoo serialize-javascript

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.