Process memory exhaustion via unreleased GIF frame buffers
Published Feb 23, 2026 · Updated Feb 23, 2026
Memory leak in libsixel before 1.8.7 allows local users to exhaust process memory by converting a crafted GIF with img2sixel. In gif_init_frame, the non-palette GIF path replaces frame->pixels with a new allocation without first releasing the previous buffer. Repeated processing of such frames consumes memory and can interrupt the invoking process; no confidentiality or integrity impact is reported.
Summary
What happened
Memory leak in libsixel before 1.8.7 allows local users to exhaust process memory by converting a crafted GIF with img2sixel. In gif_init_frame, the non-palette GIF path replaces frame->pixels with a new allocation without first releasing the previous buffer. Repeated processing of such frames consumes memory and can interrupt the invoking process; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2025-61146
- Published
- Feb 23, 2026
- Updated
- Feb 23, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2026CVE publishedPublication date reported by the CVE source.
- Feb 23, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
- libsixel issue 207 regression proof of conceptproof 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