Heap disclosure or crash via integer-overflowed bounds check
Published Feb 27, 2026 · Updated Feb 27, 2026
Out-of-bounds read in pillow-heif before 1.3.0 allows attackers to disclose heap data or crash an encoding process via large image dimensions. Three plane-writing functions multiply 32-bit stride and height values before comparing the result with a 64-bit buffer length, so overflow lets an undersized buffer pass validation and reach memcpy. The encode path is exposed when an application accepts attacker-influenced dimensions or stride values; no non-default security setting is required.
Summary
What happened
Out-of-bounds read in pillow-heif before 1.3.0 allows attackers to disclose heap data or crash an encoding process via large image dimensions. Three plane-writing functions multiply 32-bit stride and height values before comparing the result with a 64-bit buffer length, so overflow lets an undersized buffer pass validation and reach memcpy. The encode path is exposed when an application accepts attacker-influenced dimensions or stride values; no non-default security setting is required.
The record
- CVE
- CVE-2026-28231
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- Alexander Piskun
- Product
- pillow-heif
- Classifications
- CWE-190, CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Maintainer advisory encode-path PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo