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


- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111404, CLSA-2026-1793180818, CLSA-2026-1793183866, CLSA-2026-1793187934, CLSA-2026-1793207115, CLSA-2026-1793209309, MINI-2vjf-2j3w-vqp3, MINI-6cxw-hpcm-65m5, MINI-7557-qw6m-7292, MINI-9p5j-3f6p-fc9c, MINI-qvgc-hw6f-r9xj, MINI-v2rc-3q4w-wg74

## What is CVE-2026-115897?

CVE-2026-115897 is a low-severity vulnerability in yahoo serialize-javascript, published on 23 Oct 2026. 

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-115897?


## How do I fix CVE-2026-115897?

Upgrade to a fixed version.

## Is CVE-2026-115897 being exploited?

There is no known exploitation of CVE-2026-115897 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115897 and fix it if it is affected.

What it is: CVE-2026-115897 is a low-severity vulnerability in yahoo serialize-javascript, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115897 in the wild and no public exploit code.

Affected product: yahoo serialize-javascript. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115897/ (Markdown: https://insights.sbomify.com/CVE-2026-115897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115897
- OSV: https://osv.dev/vulnerability/CVE-2026-115897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115897/
Summaries are generated and may contain mistakes; the official description above is the record.