# tablib: Stored XSS in the HTML export via unescaped dataset title

Advisory record · `GHSA-gqgw-jghv-mxwx`

- **Identifiers:** `GHSA-gqgw-jghv-mxwx` · `CVE-2026-9318` · `PYSEC-2026-3702`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 12 Aug 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Aug 2026, 03:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `tablib` (PyPI): affected `<3.10.0`; fixed in `3.10.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> tablib versions before 3.10.0 have a stored cross-site scripting flaw in the HTML export: dataset titles are inserted unescaped into the HTML output. An attacker can supply a file, such as an XLSX, ODS, XLS, or YAML file, with a malicious worksheet name that is carried into the title. When the exported HTML is viewed in a browser, the script can run, enabling session hijacking and unauthorized actions. Upgrade to tablib 3.10.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.8 Medium, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 22nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 12 Aug 2026, 02:20 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-9318)
- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gqgw-jghv-mxwx)

## Sources

- [GitHub Advisory Database: GHSA-gqgw-jghv-mxwx](https://github.com/advisories/GHSA-gqgw-jghv-mxwx)
- [OSV: GHSA-gqgw-jghv-mxwx](https://osv.dev/vulnerability/GHSA-gqgw-jghv-mxwx)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-9318>
- <https://github.com/jazzband/tablib/pull/668>
- <https://github.com/jazzband/tablib>
- <https://github.com/jazzband/tablib/releases/tag/v3.10.0>
- <https://www.vulncheck.com/advisories/tablib-versions-prior-to-stored-xss-via-html-export-dataset-title>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gqgw-jghv-mxwx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gqgw-jghv-mxwx/>. Everything for agents: <https://agentprime.io/llms.txt>.
