CVE-2026-2913: libvips source.c vips_source_read_to_memory heap-based overflow
Noroxi assessment
Priority: Monitor (action score 4/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: vips (Debian:12) 8.14.1-3+deb12u3; vips (Debian:13) 8.16.1-1+deb13u1; vips (Debian:14) 8.18.0-2.
Low priority for now. Upgrade to vips (Debian:12) 8.14.1-3+deb12u3; vips (Debian:13) 8.16.1-1+deb13u1; vips (Debian:14) 8.18.0-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)."
- Published
- Feb 22, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-119
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 2.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libvips | libvips | cpe:2.3:a:libvips:libvips |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
n/a libvips
- 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 8.11 … (+8)affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libvips libvipsup to 8.19.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | vips | before 8.14.1-3+deb12u3 | 8.14.1-3+deb12u3 |
| Debian:13 | vips | before 8.16.1-1+deb13u1 | 8.16.1-1+deb13u1 |
| Debian:14 | vips | before 8.18.0-2 | 8.18.0-2 |
| openSUSE:Tumbleweed | vips | before 8.18.7-1.1 | 8.18.7-1.1 |
Same product
libvips: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-17534vips_foreign_load_gif_scan_image in foreign/gifload.c in libvips before 8.8.2 tries to access a color map before a DGifGetImageDesc call…36Monitor
- CVE-2025-29769libvips has a potential heap-based buffer overflow when attempting to convert multiband TIFF input to HEIF output34Monitor
- CVE-2026-69242libvips: Integer overflow leading to heap buffer overflow leading to possible attacker-controlled mmap-resident write33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-40032Sep 11, 2023 · Potential segfault due to NULL pointer dereference in libvips22Monitor
- ← EarlierCVE-2025-59933Sep 29, 2025 · libvips is vulnerable to Buffer Over-Read in poppler-based pdfload20Monitor
- Later →CVE-2026-3145Feb 24, 2026 · libvips matrixload.c vips_foreign_load_matrix_header memory corruption19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:vips | 8.14.1-3+deb12u3 · Debian:12 | Package registry (OSV) |
| opensuse:vips | 8.18.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Niebelungen (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31452 days apartlibvips matrixload.c vips_foreign_load_matrix_header memory corruption19Monitor
- CVE-2026-31473 days apartlibvips csvload.c vips_foreign_load_csv_build heap-based overflow7Monitor
- CVE-2026-32814 days apartlibvips bandrank.c vips_bandrank_build heap-based overflow7Monitor
- CVE-2026-32824 days apartlibvips unpremultiply.c vips_unpremultiply_build out-of-bounds7Monitor
- CVE-2026-32834 days apartlibvips extract.c vips_extract_band_build out-of-bounds7Monitor
Not on record for this CVE: EPSS history · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.