CVE-2026-3283 json
libvips extract.c vips_extract_band_build out-of-bounds
published 8mo ago modified 4mo ago also EUVD-2026-8990
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
A vulnerability has been found in libvips 8.19.0. This issue affects the function vips_extract_band_build of the file libvips/conversion/extract.c. The manipulation of the argument extract_band leads to out-of-bounds read. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 24795bb3d19d84f7b6f5ed86451ad556c8f2fe70. To fix this issue, it is recommended to deploy a patch.
Patch / fix
- vips Debian 12 8.14.1-3+deb12u3
- vips Debian 13 8.16.1-1+deb13u1
- vips Debian 14 8.18.0-3
debian advisories DEBIAN-CVE-2026-3283
- github.com/libvips/libvips@24795bb commit
- github.com/libvips/libvips#4887 pull request
Is CVE-2026-3283 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-3283 updated cvss 3.3
libvips: vips: libvips: Information disclosure due to out-of-bounds read
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/libvips/libvips/issues/4880#issue-3944214985 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/libvips/libvips/issues/4880 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C |
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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 |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- n/a libvips
Classification
References
-
github.com
/libvips/libvips/pull/4887
issue-tracking, patch
-
github.com
/libvips/libvips/commit/24795bb3d19d84f7b6f5ed86451ad556c8f2fe70
patch
-
github.com
/libvips/libvips/issues/4880#issue-3944214985
exploit, issue-tracking, vendor-advisory
-
github.com
/libvips/libvips/issues/4880
issue-tracking, exploit, vendor-advisory
-
vuldb.com
/?id.348012
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.348012
signature, permissions-required, vdb-entry
-
vuldb.com
/?submit.758863
third-party-advisory, vdb-entry
-
github.com
/libvips/libvips/
product
Sources
- CVE List CVE-2026-3283
- NVD CVE-2026-3283
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.