How to Fix CVE-2026-28231: Out-of-bounds read in pillow_heif
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-28231 is a out-of-bounds read in bigcat88 pillow_heif. The fix is to apply the vendor patch noted below.
| Severity | 5.5 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | pillow_heif < 1.3.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-125: Out-of-bounds Read |
What is CVE-2026-28231?
pillow_heif is a Python library for working with HEIF images and plugin for Pillow. Prior to version 1.3.0, an integer overflow in the encode path buffer validation of _pillow_heif.c allows an attacker to bypass bounds checks by providing large image dimensions, resulting in a heap out-of-bounds read. This can lead to information disclosure (server heap memory leaking into encoded images) or denial of service (process crash). No special configuration is required — this triggers under default settings. Version 1.3.0 fixes the issue. The CVSS base score is 5.5 (Medium). The official advisory is at https://github.com/bigcat88/pillow_heif/security/advisories/GHSA-5gjj-6r7v-ph3x.
Am I affected?
Check the version of pillow_heif you are running and compare it against the Affected row above (pillow_heif < 1.3.0). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s pillow-heif 2>/dev/null | grep -i ^Version
rpm -q pillow-heif 2>/dev/null
command -v pillow-heif >/dev/null && pillow-heif --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*pillow_heif*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "pillow_heif" 2>$null
How to fix CVE-2026-28231
Upgrade pillow_heif to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade pillow-heif
dpkg -s pillow-heif | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh pillow-heif -y
# or for older releases:
sudo yum update pillow-heif -y
rpm -q pillow-heif
SUSE / openSUSE
sudo zypper refresh
sudo zypper update pillow-heif
rpm -q pillow-heif
Python / pip
pip install --upgrade pillow-heif
pip show pillow-heif | grep -i version
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-28231 affecting pillow_heif
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-28231-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detect installed version"
$pkg = Get-Package -Name "*pillow_heif*" -ErrorAction SilentlyContinue
if ($pkg) { $pkg | Format-Table Name, Version }
else { Write-Host "Not detected via Get-Package; try winget list" }
Write-Host "[2/4] Backup configuration"
$backup = "C:\Backup\pillow-heif-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\pillow_heif" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "pillow_heif" --silent --accept-source-agreements --accept-package-agreements
if ($LASTEXITCODE -ne 0) {
# Fallback: pull latest via OS update channel
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verify the patched build"
winget list --name "pillow_heif"
Write-Host "Patch applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-28231 affecting pillow_heif
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-28231-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
dpkg -s pillow-heif 2>/dev/null | grep -i ^Version || echo "pillow-heif not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q pillow-heif || echo "pillow-heif not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-28231-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/pillow-heif /etc/pillow-heif.d /etc/pillow-heif.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y pillow-heif
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y pillow-heif
elif command -v yum >/dev/null; then
yum update -y pillow-heif
elif command -v zypper >/dev/null; then
zypper --non-interactive update pillow-heif
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s pillow-heif 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q pillow-heif
fi
echo "Done. Restart any service that loaded the old library."
If you can't patch immediately
Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.
Restrict exposure with nftables (Linux)
# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Block at the host firewall (Windows)
New-NetFirewallRule -DisplayName "Block-CVE-2026-28231" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-28231"
Disable the affected service (Linux)
sudo systemctl stop pillow-heif 2>/dev/null || true
sudo systemctl disable pillow-heif 2>/dev/null || true
If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.
How to verify the fix worked
After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.
# Linux
dpkg -s pillow-heif 2>/dev/null | grep -i ^Version
rpm -q pillow-heif 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true
# Windows
Get-Package -Name "*pillow_heif*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-23966: Critical Vulnerability in sm-crypto — Critical Vulnerability in sm-crypto
- How to Fix CVE-2026-3240: Cross-site scripting in Concrete CMS , Cross-site scripting in Concrete CMS
- How to Fix CVE-2026-39857: Information disclosure in apostrophe , Information disclosure in apostrophe
- How to Fix CVE-2026-41219: Information Disclosure in BIG-IP , Information Disclosure in BIG-IP
- How to Fix CVE-2026-2274: Critical Vulnerability in AppSheet Web (Main Server) , Critical Vulnerability in AppSheet Web (Main Server)
Is CVE-2026-28231 actively exploited?
There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.
Do I need to reboot after patching CVE-2026-28231?
For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.
What is the CVSS score for CVE-2026-28231?
5.5 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P.
Where is the official advisory for CVE-2026-28231?
The vendor advisory is at https://github.com/bigcat88/pillow_heif/security/advisories/GHSA-5gjj-6r7v-ph3x. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28231.
References
- Official vendor advisory: https://github.com/bigcat88/pillow_heif/security/advisories/GHSA-5gjj-6r7v-ph3x
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28231
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/bigcat88/pillow_heif/commit/8305a15d3780c533b762578cbe987d27a2c59c7a
- Additional reference: https://github.com/bigcat88/pillow_heif/releases/tag/v1.3.0
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*