# CVE-2026-130593: Scalar scalar-ninja 0.1.0 before 0.3.3 XSS via Inline Configuration Script


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-8p3f-3g49-2935, GHSA-qcqh-p9f6-q4wm

## What is CVE-2026-130593?

CVE-2026-130593 is a medium-severity vulnerability in scalar-ninja, published on 17 Nov 2026. 

### Official description

Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site scripting vulnerability in get_scalar_api_reference() that embeds unescaped OpenAPI content inside an inline script element. Attackers can supply an OpenAPI document containing a </script><script> sequence in content or sources to execute scripts in the documentation origin for every user viewing the API reference.

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

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

1 open source package ship an affected version, including scalar-ninja.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `scalar-ninja` | PyPI | `pkg:pypi/scalar-ninja` | From 0.1.0 | 0.3.3 |

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

Upgrade scalar-ninja to 0.3.3 or later.

## Is CVE-2026-130593 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130593 is a medium-severity vulnerability in scalar-ninja, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130593 in the wild and no public exploit code.

Affected packages and fixed versions:
- scalar-ninja (PyPI): affected from 0.1.0; fixed in 0.3.3

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-130593/ (Markdown: https://insights.sbomify.com/CVE-2026-130593/index.md)
```

## Sources

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

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