Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2913: Heap-based Buffer Overflow in libvips

0
Low
VulnerabilityCVE-2026-2913cvecve-2026-2913
Published: Sun Feb 22 2026 (02/22/2026, 04:02:13 UTC)
Source: CVE Database V5
Product: libvips

Description

A vulnerability was determined in libvips up to 8.19.0. The affected element is the function vips_source_read_to_memory of the file libvips/iofuncs/source.c. This manipulation causes heap-based buffer overflow. It is possible to launch the attack on the local host. The attack's complexity is rated as high. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. Patch name: a56feecbe9ed66521d9647ec9fbcd2546eccd7ee. Applying a patch is the recommended action to fix this issue. The confirmation of the bugfix mentions: "[T]he impact of this is negligible, since this only affects custom seekable sources larger than 4 GiB (and the crash occurs in user code rather than libvips itself)."

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/01/2026, 06:18:39 UTC

Technical Analysis

CVE-2026-2913 identifies a heap-based buffer overflow vulnerability in the libvips image processing library, affecting all versions up to 8.19.0. The vulnerability resides in the function vips_source_read_to_memory within the source.c file. This function mishandles memory when reading from custom seekable sources larger than 4 GiB, leading to a buffer overflow on the heap. The overflow can cause a crash in the user code that integrates libvips, rather than in libvips itself, which limits the scope of the impact. The vulnerability requires local access to the host system, and the complexity to exploit it is high due to the need for specific conditions, such as large custom data sources and precise triggering of the overflow. No authentication or user interaction is necessary, but the exploitability is difficult. The vulnerability has been publicly disclosed, but no known exploits are currently active in the wild. The patch identified by commit a56feecbe9ed66521d9647ec9fbcd2546eccd7ee fixes the issue by correcting the memory handling in the affected function. The CVSS v4.0 score is 2.0, indicating low severity, primarily because the impact is limited to local crashes and does not lead to code execution or privilege escalation. This vulnerability mainly affects applications and systems that utilize libvips for image processing tasks involving large custom seekable sources, which are relatively uncommon scenarios.

Potential Impact

The primary impact of CVE-2026-2913 is a potential denial of service through application crashes when processing large custom seekable sources exceeding 4 GiB in size. Since the crash occurs in user code rather than libvips itself, the risk of remote code execution or privilege escalation is negligible. However, for organizations relying on libvips in critical image processing workflows, especially those handling very large images or custom data sources, this vulnerability could lead to instability or service interruptions. The requirement for local access and the high complexity of exploitation reduce the likelihood of widespread attacks. Nonetheless, unpatched systems could experience unexpected application failures, potentially affecting availability and operational continuity in environments where libvips is embedded in local processing pipelines or desktop applications.

Mitigation Recommendations

To mitigate CVE-2026-2913, organizations should apply the official patch identified by commit a56feecbe9ed66521d9647ec9fbcd2546eccd7ee as soon as possible. Beyond patching, it is advisable to audit the use of libvips in environments to identify any workflows that process custom seekable sources larger than 4 GiB and assess their exposure. Restrict local access to trusted users only, as exploitation requires local presence. Implement monitoring for application crashes related to image processing tasks to detect potential exploitation attempts or stability issues. Where feasible, limit the size of input sources to below 4 GiB or validate input sizes before processing to reduce risk. Additionally, maintain up-to-date software inventories and ensure that libvips dependencies are regularly updated to incorporate security fixes.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-20T20:20:44.103Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699a8349be58cf853bd68abf

Added to database: 2/22/2026, 4:17:13 AM

Last enriched: 3/1/2026, 6:18:39 AM

Last updated: 4/8/2026, 10:49:59 AM

Views: 122

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses