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-3145: Memory Corruption in libvips

0
Medium
VulnerabilityCVE-2026-3145cvecve-2026-3145
Published: Wed Feb 25 2026 (02/25/2026, 02:02:10 UTC)
Source: CVE Database V5
Product: libvips

Description

A flaw has been found in libvips up to 8.18.0. The affected element is the function vips_foreign_load_matrix_file_is_a/vips_foreign_load_matrix_header of the file libvips/foreign/matrixload.c. Executing a manipulation can lead to memory corruption. The attack needs to be launched locally. This patch is called d4ce337c76bff1b278d7085c3c4f4725e3aa6ece. A patch should be applied to remediate this issue.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/04/2026, 20:39:45 UTC

Technical Analysis

CVE-2026-3145 identifies a memory corruption vulnerability in libvips, an open-source image processing library widely used for efficient image transformations. The flaw resides in the matrix loading functionality within the file libvips/foreign/matrixload.c, specifically in the functions vips_foreign_load_matrix_file_is_a and vips_foreign_load_matrix_header. These functions handle loading matrix files, and improper handling of input data can lead to memory corruption. This vulnerability requires local access to the system, meaning an attacker must have some level of local privileges to trigger the flaw. The vulnerability does not require user interaction or elevated privileges beyond local access, but the attacker must be able to manipulate the input to these functions. Memory corruption can lead to unpredictable behavior including crashes, data leakage, or potential code execution depending on the exploitation context. The vulnerability affects all libvips versions from 8.0 through 8.18.0. A patch identified by commit d4ce337c76bff1b278d7085c3c4f4725e3aa6ece has been released to remediate the issue. No known exploits have been reported in the wild, and the CVSS v4.0 base score is 4.8, reflecting a medium severity level due to the local attack vector and limited scope of impact. Organizations relying on libvips for image processing should prioritize applying the patch to prevent potential exploitation.

Potential Impact

The impact of CVE-2026-3145 primarily affects systems running libvips versions up to 8.18.0, which are used in various applications and services for image processing. Successful exploitation could lead to memory corruption, which may cause application crashes, denial of service, or potentially allow an attacker to execute arbitrary code or access sensitive information if combined with other vulnerabilities. Since exploitation requires local access, the threat is more significant in multi-user environments, shared hosting, or containerized deployments where untrusted users have local system access. Organizations using libvips in backend services, image processing pipelines, or web applications could face service disruptions or compromise of data integrity. Although no public exploits are known, the vulnerability could be leveraged by insider threats or attackers who gain initial local foothold. The medium severity rating indicates moderate risk, but the potential for escalation or lateral movement within networks makes timely remediation important.

Mitigation Recommendations

To mitigate CVE-2026-3145, organizations should apply the official patch identified by commit d4ce337c76bff1b278d7085c3c4f4725e3aa6ece to update libvips to a fixed version beyond 8.18.0. If immediate patching is not feasible, restrict local access to systems running libvips to trusted users only, minimizing the risk of exploitation. Employ strict access controls and monitoring on systems where libvips is deployed, especially in shared or multi-tenant environments. Conduct code reviews and input validation on any custom integrations that invoke libvips matrix loading functions to detect and prevent malformed inputs. Additionally, implement runtime protections such as memory corruption mitigations (e.g., ASLR, DEP) and sandboxing to limit the impact of potential exploitation. Regularly audit and update all dependencies to ensure vulnerabilities are promptly addressed. Finally, maintain comprehensive logging and alerting to detect anomalous local activity that could indicate exploitation attempts.

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-24T19:53:43.308Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699e6866b7ef31ef0bae9de9

Added to database: 2/25/2026, 3:11:34 AM

Last enriched: 3/4/2026, 8:39:45 PM

Last updated: 4/10/2026, 6:06:28 PM

Views: 84

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