libvips up to 8.18.0 csvload.c vips_foreign_load_csv_build heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libvips up to 8.18.0. It has been classified as critical. This impacts the function vips_foreign_load_csv_build of the file libvips/foreign/csvload.c. This manipulation causes heap-based overflow.
This vulnerability appears as CVE-2026-3147. The attack requires local access. In addition, an exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as critical was found in libvips up to 8.18.0. Affected by this vulnerability is the function vips_foreign_load_csv_build of the file libvips/foreign/csvload.c. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-3147. The exploitation appears to be easy. An attack has to be approached locally. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 299977 (Linux Distros Unpatched Vulnerability : CVE-2026-3147), which helps to determine the existence of the flaw in a target environment.
Applying the patch b3ab458a25e0e261cbd1788474bbc763f7435780 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at Tenable (299977). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/libvips/libvips/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 299977
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-3147
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: b3ab458a25e0e261cbd1788474bbc763f7435780
Timeline
02/24/2026 Advisory disclosed02/24/2026 VulDB entry created
02/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 4874
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-3147 (🔒)
GCVE (CVE): GCVE-0-2026-3147
GCVE (VulDB): GCVE-100-347653
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/24/2026 20:59Updated: 02/28/2026 23:51
Changes: 02/24/2026 20:59 (59), 02/28/2026 23:51 (2)
Complete: 🔍
Submitter: Niebelungen
Cache ID: 216::103
Submit
Accepted
- Submit #758692: libvips 8.19.0(7fab325d2) Improper Validation of Array Index (by Niebelungen)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.