# CVE-2026-9318: tablib versions prior to 3.10.0 Stored XSS via HTML Export Dataset Title

> Attackers can execute arbitrary JavaScript via stored XSS in tablib HTML exports by embedding malicious payloads in dataset titles, leading to session hijacking and data exposure.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-9318, ECHO-5ee8-23ed-cfb4, GHSA-gqgw-jghv-mxwx, PYSEC-2026-3702, UBUNTU-CVE-2026-9318, openSUSE-SU-2026:11533-1

## What is CVE-2026-9318?

CVE-2026-9318 is a medium-severity cross-site scripting vulnerability in Jazzband tablib, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

tablib prior to 3.10.0 contains a stored cross-site scripting vulnerability in the HTML export functionality that allows attackers to execute arbitrary JavaScript by embedding malicious payloads in dataset titles, which are interpolated unsanitized into HTML output via the export_book method in the _html.py format handler. Attackers can rename worksheet sheets in imported files such as XLSX, ODS, XLS, or YAML with script payloads that are assigned to the Dataset title attribute and rendered unescaped inside an HTML h3 tag, leading to session hijacking, unauthorized administrative actions, and sensitive data exposure when the output is rendered in a browser.

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

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

3 open source packages ship an affected version, including tablib.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tablib` | PyPI | All versions | 3.10.0 |
| `tablib` | PyPI | All versions | 3.10.0 |
| `tablib` | PyPI | All versions | 3.10.0 |
| `python-tablib` | openSUSE:Tumbleweed | All versions | 3.10.0-1.1 |

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

Upgrade tablib to 3.10.0 or later.

## Is CVE-2026-9318 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9318 is a medium-severity cross-site scripting vulnerability in Jazzband tablib, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9318 in the wild and no public exploit code.

Affected packages and fixed versions:
- tablib (PyPI): affected all versions; fixed in 3.10.0
- tablib (PyPI): affected all versions; fixed in 3.10.0
- tablib (PyPI): affected all versions; fixed in 3.10.0

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

## Sources

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

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