← Back
CVE-2026-28231
Out-of-Bounds Read in pi-heif (CVE-2026-28231)
Summary
vulnerability in pi-heif (CVE-2026-28231). Confidential information can be exposed externally. Exploitable via ``_pillow_heif.c``. Mitigation: upgrade to `1.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-28231** has been found in pi-heif.
Attackers can target a specific entry point like ``_pillow_heif.c`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade pi-heif to **1.3.0** or later.
If unsure, ask your IT team or search "pi-heif CVE-2026-28231" on the vendor's site.
CVE-2026-28231 (pi-heif) — CWE-125 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `_pillow_heif.c`
Patched: `1.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 pi-heif. Attackers reach the vulnerable code path via ``_pillow_heif.c`` without authentication.
📍 Affected scope
pi-heif — . Attack surface: `_pillow_heif.c`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.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 'pi-heif' .` 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 'pi-heif' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pi-heif` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pi-heif to 1.3.0ステージング環境で 1.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
pi-heif
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]
pip
pillow-heif
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]
PyPI
pi-heif
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]
PyPI
pillow-heif
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]
References
- advisory https://github.com/bigcat88/pillow_heif/releases/tag/v1.3.0
- patch https://github.com/bigcat88/pillow_heif/commit/8305a15d3780c533b762578cbe987d27a2c59c7a
- report https://github.com/bigcat88/pillow_heif/security/advisories/GHSA-5gjj-6r7v-ph3x
- web https://nvd.nist.gov/vuln/detail/CVE-2026-28231
- web https://github.com/pypa/advisory-database/tree/main/vulns/pi-heif/PYSEC-2026-2248.yaml
- web https://github.com/pypa/advisory-database/tree/main/vulns/pillow-heif/PYSEC-2026-2258.yaml
- web https://github.com/advisories/GHSA-5gjj-6r7v-ph3x