Cross-Site Scripting (XSS) in tablib (CVE-2026-9318)
Summary
Cross-site scripting in tablib (CVE-2026-9318). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.10.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9318 has been found in tablib.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade tablib to 3.10.0 or later.
If unsure, ask your IT team or search "tablib CVE-2026-9318" on the vendor's site.
CVE-2026-9318 (tablib) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 3.10.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in tablib.
Check the vendor advisory for the affected versions of tablib.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.10.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tablib' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tablib' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tablibを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tablib to 3.10.0ステージング環境で 3.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-9318 python-tablib
- Ubuntu UBUNTU-CVE-2026-9318 python-tablib
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web vulncheck.com