An issue was discovered in Pillow before 8.2.0.
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.73% (FIRST EPSS); higher than 53.7% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: python3-pillow (AlmaLinux:8) 5.1.1-16.el8; py3-pillow (Alpine:v3.14) 8.2.0-r0; pillow (Debian:12) 8.1.2+dfsg-0.2.
Low priority for now. Upgrade to python3-pillow (AlmaLinux:8) 5.1.1-16.el8; py3-pillow (Alpine:v3.14) 8.2.0-r0; pillow (Debian:12) 8.1.2+dfsg-0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in Pillow before 8.2.0. For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run a large number of times on empty data.
- Published
- Jun 2, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-345
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| python | pillow | cpe:2.3:a:python:pillow |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora33
- python pillowbefore 8.2.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | python3-pillow | before 5.1.1-16.el8 | 5.1.1-16.el8 |
| Alpine:v3.14 | py3-pillow | before 8.2.0-r0 | 8.2.0-r0 |
| Debian:12 | pillow | before 8.1.2+dfsg-0.2 | 8.1.2+dfsg-0.2 |
| openSUSE:Leap 15.5 | python-Pillow | before 7.2.0-150300.3.12.1 | 7.2.0-150300.3.12.1 |
| PyPI | pillow | from 5.1.0 · before 8.2.0 | 8.2.0 |
| PyPI | pillow | before 8.2.0 | 8.2.0 |
| Red Hat:enterprise_linux:8::appstream | python-pillow | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Red Hat:enterprise_linux:8::appstream | python-pillow-debuginfo | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Red Hat:enterprise_linux:8::appstream | python-pillow-debugsource | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Red Hat:enterprise_linux:8::appstream | python3-pillow | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Red Hat:enterprise_linux:8::appstream | python3-pillow-debuginfo | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Red Hat:enterprise_linux:8::appstream | python3-pillow-tk-debuginfo | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| Rocky Linux:8 | python-pillow | before 0:5.1.1-16.el8 | 0:5.1.1-16.el8 |
| SUSE:OpenStack Cloud 9 | python-Pillow | before 5.2.0-3.8.1 | 5.2.0-3.8.1 |
Same product
python: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-3007Python Image Library (PIL) 1.1.7 and earlier and Pillow 2.3 might allow remote attackers to execute arbitrary commands via shell metacharact43Plan
- CVE-2016-4009Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have u41Plan
- CVE-2022-30595libImaging/TgaRleDecode.c in Pillow 9.1.0 has a heap buffer overflow in the processing of invalid TGA image files.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-28676Jun 2, 2021 · An issue was discovered in Pillow before 8.2.0.31Monitor
- ← EarlierCVE-2021-28677Jun 2, 2021 · An issue was discovered in Pillow before 8.2.0.31Monitor
- Later →CVE-2021-34552Jul 13, 2021 · Pillow through 8.2.0 and PIL (aka Python Imaging Library) through 1.1.7 allow an attacker to pass controlled parameters directly into a conv40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:python3-pillow | 5.1.1-16.el8 · AlmaLinux:8 | Package registry (OSV) |
| alpine:py3-pillow | 8.2.0-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:pillow | 8.1.2+dfsg-0.2 · Debian:12 | Package registry (OSV) |
| opensuse:python-Pillow | 7.2.0-150300.3.12.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| PyPI:pillow | 8.2.0 | Package registry (OSV) |
| red hat:python-pillow | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python-pillow-debuginfo | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python-pillow-debugsource | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-pillow | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-pillow-debuginfo | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-pillow-tk-debuginfo | 0:5.1.1-16.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:python-pillow | 0:5.1.1-16.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:python-Pillow | 5.2.0-3.8.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.