Vulnerability in python-tablib (DEBIAN-CVE-2026-9318)

Summary

Vulnerability in python-tablib (DEBIAN-CVE-2026-9318). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.10.0-1 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: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-9318 has been found in python-tablib.
Risk of unauthorized operations or information disclosure.
What to do: upgrade python-tablib to 3.10.0-1 or later.
If unsure, ask your IT team or search "python-tablib DEBIAN-CVE-2026-9318" on the vendor's site.

DEBIAN-CVE-2026-9318 (python-tablib)
Patched: 3.10.0-1 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in python-tablib.

📍 Affected scope

Check the vendor advisory for the affected versions of python-tablib.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.10.0-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'python-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

1
Identify exposure identify
```
grep -r 'python-tablib' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で python-tablib を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade python-tablib to 3.10.0-1
```
ステージング環境で 3.10.0-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 python-tablib

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:13 python-tablib

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 python-tablib

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1"}]}]

References

advisory security-tracker.debian.org