Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-30595

python-pillow: heap buffer overflow in crafted TGA file

Overview

Published
25 May 2022
Modified
17 Jun 2026
Critical CVE
2 Registry packages
14 OS packages
4 Linux distributions
Yes Fix available

Description

libImaging/TgaRleDecode.c in Pillow 9.1.0 has a heap buffer overflow in the processing of invalid TGA image files.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-787

Affected packages · 2

Packages affected by CVE-2022-30595
EcosystemPackageVulnerableFixed in
Bitnami pillow >=9.1.0, <9.1.1 9.1.1
PyPI pillow >=9.1.0, <9.1.1 9.1.1

Open a package to see all its vulnerabilities.

Operating systems · 10 fixes

alpine 4 releases · 1 package

fixed 4
py3-pillow
alpine fixes for CVE-2022-30595
ReleasePackageFixed in
3.22 py3-pillow 9.1.1-r0
3.23 py3-pillow 9.1.1-r0
3.24 py3-pillow 9.1.1-r0
edge py3-pillow 9.1.1-r0

debian 3 releases · 1 package

fixed 3
pillow
debian fixes for CVE-2022-30595
ReleasePackageFixed in
12 pillow 9.1.1-1
13 pillow 9.1.1-1
14 pillow 9.1.1-1

echo 1 release · 1 package

fixed 1
pillow
echo fixes for CVE-2022-30595
ReleasePackageFixed in
pillow 9.1.1-1

openSUSE 1 release · 2 packages

fixed 2
python311-pillow python310-pillow
openSUSE fixes for CVE-2022-30595
ReleasePackageFixed inAdvisory
Tumbleweed python311-pillow +5 11.1.0-1.1 openSUSE-SU-2025:14645-1
Tumbleweed python310-pillow +5 9.1.1-1.1 openSUSE-SU-2024:12111-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.