← Back
CVE-2026-59198
medium
CVSS 6.5
Out-of-Bounds Read in Pillow (CVE-2026-59198)
Summary
vulnerability in Pillow (CVE-2026-59198). Confidential information can be exposed externally. Exploitable via ``tga_rle``. Mitigation: upgrade to `12.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59198** has been found in Pillow.
Attackers can target a specific entry point like ``tga_rle`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade Pillow to **12.3.0** or later.
If unsure, ask your IT team or search "Pillow CVE-2026-59198" on the vendor's site.
CVE-2026-59198 (Pillow) — CWE-125 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `tga_rle`
Patched: `12.3.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.
❓ What is the problem
**out-of-bounds read** (CWE-125) exists in Pillow. Attackers reach the vulnerable code path via ``tga_rle`` without authentication.
📍 Affected scope
Pillow — . Attack surface: `tga_rle`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **12.3.0**.
🛡️ 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 'Pillow' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Pillow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Pillow` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Pillow to 12.3.0ステージング環境で 12.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
Pillow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.3.0"}]}]
References
- web https://github.com/python-pillow/Pillow/commit/eada3cbd7fb9963ee90673fb7b5270124a0d5f4b
- web https://github.com/python-pillow/Pillow/pull/9709
- web https://github.com/python-pillow/Pillow/releases/tag/12.3.0
- web https://github.com/python-pillow/Pillow/security/advisories/GHSA-fj7v-r99m-22gq
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59198
- web https://github.com/advisories/GHSA-fj7v-r99m-22gq