Security readout for executives and security teams
Plain-English summary
CVE-2026-3284 is a medium-severity integer overflow in libvips 8.19.0, an image-processing library. It requires local access with low privileges and is reported to affect availability only. Public exploit information exists, but the source bundle does not show confirmed active exploitation or KEV listing.
Executive priority
Treat as a routine but timely patching item. Business risk is lower than remotely exploitable flaws, but public exploit information and local availability impact justify remediation in normal vulnerability-management cycles.
Technical view
The flaw is in vips_extract_area_build in libvips/conversion/extract.c. Manipulating the extract_area argument can cause an integer overflow or wraparound. CVSS 4.0 is 4.8 with local attack vector, low complexity, low privileges, no user interaction, and low vulnerable-system availability impact.
Likely exposure
Exposure is most likely where libvips 8.19.0 is installed on systems that allow local users or local application components to invoke image-processing functions. Remote exposure is not established by the provided sources.
Exploitation context
The advisory states a public exploit exists and could be used. However, the attack is local, requires low privileges, and KEV is false. No cited source in the bundle confirms active exploitation in the wild.
Researcher notes
Evidence identifies libvips 8.19.0 and a specific vulnerable function. Sources do not establish broader affected version ranges, remote reachability, active exploitation, or an official release number containing the fix. Avoid assuming downstream products are affected without dependency confirmation.
Mitigation direction
- Identify systems and applications using libvips 8.19.0.
- Review vendor project guidance and apply the referenced patch commit if applicable.
- Prioritize shared servers or multi-user environments where local access is common.
- Monitor libvips releases for an official fixed version or advisory.
Validation and detection
- Inventory installed libvips versions across servers, containers, and application dependencies.
- Check whether commit 24795bb3d19d84f7b6f5ed86451ad556c8f2fe70 is present in deployed builds.
- Review GitHub issue and pull request status for remediation context.
- Confirm no unsupported local users can access affected image-processing workflows.
Public sources used
- CVE Program
- CVE List V5
- VDB-348013 | libvips extract.c vips_extract_area_build integer overflow
- VDB-348013 | CTI Indicators (IOB, IOC, IOA)
- Submit #758864 | libvips 8.19.0(7fab325d2) Integer Overflow or Wraparound
- GitHub issue 4879
- GitHub pull request 4887
- GitHub issue comment
- Patch commit 24795bb3d19d84f7b6f5ed86451ad556c8f2fe70
- libvips GitHub repository
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-189: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3284 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- VDB-348013 | libvips extract.c vips_extract_area_build integer overflowCVE reference · vdb-entry, technical-description
- VDB-348013 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #758864 | libvips 8.19.0(7fab325d2) Integer Overflow or WraparoundCVE reference · third-party-advisory
- https://github.com/libvips/libvips/issues/4879CVE reference · issue-tracking, exploit
- https://github.com/libvips/libvips/pull/4887CVE reference · issue-tracking, patch
- https://github.com/libvips/libvips/commit/24795bb3d19d84f7b6f5ed86451ad556c8f2fe70CVE reference · patch
- https://github.com/libvips/libvips/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Numeric Errors
Numeric Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
