Skip to main content
Vulnerability Database/CVE-2026-114113

CVE-2026-114113: Sharp libvips Multiple Vulnerabilities

CVE-2026-114113 affects Sharp image processing library versions before 0.35.0 through multiple libvips vulnerabilities in GIF, TIFF and VIPS decoders. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114113 Overview

CVE-2026-114113 affects the Sharp image processing library before version 0.35.0. Sharp bundles a vulnerable version of libvips that contains multiple flaws in its GIF, TIFF, and VIPS image decoders. The bundled vulnerabilities include CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591, and CVE-2026-69242. Attackers can supply crafted GIF, TIFF, or VIPS files to applications that use Sharp to process untrusted input. Processing these files triggers the underlying libvips flaws, impacting integrity and availability of the host application.

Critical Impact

Applications using Sharp to decode untrusted image uploads can be compromised when attackers submit malicious GIF, TIFF, or VIPS files, with a CVSS 4.0 base score of 8.4.

Affected Products

  • Sharp Node.js library versions prior to 0.35.0
  • Bundled libvips image decoders for GIF, TIFF, and VIPS formats
  • Applications and services that use Sharp to process attacker-controlled image input

Discovery Timeline

  • 2026-10-21 - CVE-2026-114113 published to the National Vulnerability Database (NVD)
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114113

Vulnerability Analysis

Sharp is a widely deployed Node.js module for high-performance image conversion. It statically bundles libvips, the underlying C image processing library. In versions before 0.35.0, Sharp ships a libvips build affected by five distinct decoder vulnerabilities. The flaws reside in parsers for the GIF, TIFF, and VIPS image formats. When Sharp calls into libvips to decode a crafted file, the vulnerable decoder path is executed inside the application process. This exposes any service that performs image resizing, format conversion, or thumbnail generation on uploaded content.

Root Cause

The root cause is a bundled-dependency exposure. Sharp links against a pinned libvips version containing memory safety and parsing defects in CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591, and CVE-2026-69242. Even if the host system has a patched libvips installed, Sharp uses its bundled copy by default. Upgrading libvips at the OS level does not remediate the issue.

Attack Vector

Exploitation requires an attacker to deliver a crafted GIF, TIFF, or VIPS file to a Sharp-based pipeline. Typical delivery channels include profile avatar uploads, document attachments, and user-generated media processed server-side. The CVSS 4.0 vector indicates local attack vector with low privileges and no user interaction, with high impact on vulnerable system integrity and availability. The vulnerability manifests inside the libvips decoder routines during image parsing. Refer to the GitHub Security Advisory GHSA-f88m-g3jw-g9cj and the VulnCheck Advisory on Sharp Vulnerabilities for decoder-level technical details.

Detection Methods for CVE-2026-114113

Indicators of Compromise

  • Unexpected crashes, segmentation faults, or restarts in Node.js worker processes handling image uploads.
  • Image processing jobs that consume anomalous CPU or memory when parsing GIF, TIFF, or VIPS inputs.
  • Presence of Sharp versions below 0.35.0 in package-lock.json, yarn.lock, or deployed node_modules directories.

Detection Strategies

  • Inventory all applications that import sharp and compare installed versions against the fixed 0.35.0 baseline using software composition analysis.
  • Instrument image-processing endpoints to log the MIME type, file extension, and parsed format of every uploaded file.
  • Alert on child process termination signals from Node.js workers performing image decoding.

Monitoring Recommendations

  • Forward Node.js stderr and process exit telemetry to a centralized log pipeline for correlation.
  • Track outbound network connections from image processing workers to detect post-exploitation activity.
  • Monitor dependency manifests in CI/CD for reintroduction of vulnerable Sharp versions.

How to Mitigate CVE-2026-114113

Immediate Actions Required

  • Upgrade Sharp to version 0.35.0 or later in all projects and container images.
  • Rebuild and redeploy any Docker images or serverless bundles that cached the vulnerable Sharp binaries.
  • Audit upload endpoints and temporarily restrict GIF, TIFF, and VIPS file processing until the upgrade is complete.

Patch Information

Upgrade sharp to 0.35.0 or newer. This release bundles a libvips version that remediates CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591, and CVE-2026-69242. See the GitHub Security Advisory GHSA-f88m-g3jw-g9cj for release details.

Workarounds

  • Validate uploaded file formats and reject GIF, TIFF, and VIPS inputs at the ingress layer where feasible.
  • Isolate image decoding in sandboxed worker processes or containers with reduced privileges and resource limits.
  • Enforce strict file size limits and timeouts on image processing jobs to constrain exploit surface.
bash
# Configuration example
npm install sharp@^0.35.0
npm audit --production

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.