High Memory corruption exploit reference

CVE-2026-3283 — libvips extract.c vips_extract_band_build out-of-bounds

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.

Published Feb 27, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.2%

ahead of 9% of scored CVEs · Oct 14, 2026

Affects

Libvips

CVSS base

7.1

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Libvips Libvips).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Libvips	Libvips	version 8.19.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
4.8	CVSS 4.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
1.9	CVSS 4.0	Low	—	—	cna@vuldb.com via NIST National Vulnerability Database
7.1	CVSS 3.1	High	1.8	5.2	nvd@nist.gov via NIST National Vulnerability Database
3.3	CVSS 3.1	Low	1.8	1.4	cna@vuldb.com via NIST National Vulnerability Database
3.3	CVSS 3.1	Low	—	—	VulDB via CVE Program (cve.org) e CISA ADP
3.3	CVSS 3.0	Low	—	—	VulDB via CVE Program (cve.org) e CISA ADP
1.7	CVSS 2.0	Low	3.1	2.9	cna@vuldb.com via NIST National Vulnerability Database
1.7	CVSS 2.0	Low	—	—	VulDB via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.1 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 7.1
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Feb 27, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

github.com/libvips/libvips/issues/4880
Exploit, Issue Tracking, Vendor Advisory, issue-tracking, NIST National Vulnerability Database
github.com/libvips/libvips/issues/4880
Exploit, Issue Tracking, Vendor Advisory, exploit, issue-tracking, NIST National Vulnerability Database
github.com/libvips/libvips/pull/4887
Issue Tracking, Patch, issue-tracking, patch, NIST National Vulnerability Database
github.com/libvips/libvips/commit/24795bb3d19d84f7b6f5ed86451ad556c8f2fe70
Patch, patch, NIST National Vulnerability Database
github.com/libvips/libvips/
Product, product, NIST National Vulnerability Database
vuldb.com/
Third Party Advisory, VDB Entry, vdb-entry, technical-description, NIST National Vulnerability Database
vuldb.com/
Third Party Advisory, VDB Entry, third-party-advisory, NIST National Vulnerability Database
vuldb.com/
Permissions Required, VDB Entry, signature, permissions-required, NIST National Vulnerability Database

Elsewhere on this site

Libvips
every CVE for this vendor

Memory corruption
same class

CWE-119
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-35590 Heap-based Buffer Overflow in Libvips Jul 20, 2026
High CVE-2026-35591 Heap-based Buffer Overflow in Libvips Jul 20, 2026
High CVE-2026-33327 Integer Overflow or Wraparound in Libvips Jul 20, 2026
Medium CVE-2026-33328 Integer Overflow or Wraparound in Libvips Jul 20, 2026
Medium CVE-2026-3284 libvips extract.c vips_extract_area_build integer overflow Feb 27, 2026
High CVE-2026-3282 libvips unpremultiply.c vips_unpremultiply_build out-of-bounds Feb 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-3283 is "libvips extract.c vips_extract_band_build out-of-bounds", rated High. It affects Libvips (Libvips); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.