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-114111 Overview
CVE-2026-114111 affects the sharp Node.js image processing library in versions before 0.35.5. The library bundles a vulnerable librsvg dependency affected by CVE-2026-96889, a memory-related flaw classified as Use After Free [CWE-416]. Under specific runtime conditions on glibc-based Linux systems, an attacker can supply a crafted SVG image that triggers code execution when sharp decodes it through librsvg. The vulnerability affects applications that process untrusted SVG input, including web services performing image conversion, thumbnail generation, or format transformation.
Critical Impact
Attackers who can submit crafted SVG files to applications using vulnerable sharp versions on glibc-based Linux may achieve arbitrary code execution in the context of the processing service.
Affected Products
- sharp Node.js library versions prior to 0.35.5
- Applications bundling vulnerable librsvg through sharp on glibc-based Linux
- Server-side image processing pipelines that accept SVG input
Discovery Timeline
- 2026-10-21 - CVE-2026-114111 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114111
Vulnerability Analysis
The flaw originates in librsvg, the SVG rendering library bundled as a dependency within sharp. librsvg contains a memory-related defect tracked as CVE-2026-96889 and categorized under [CWE-416] Use After Free. When sharp processes an SVG image, it dispatches rendering to the bundled librsvg, inheriting the memory safety flaw.
Use-after-free conditions occur when a program references memory after it has been released. Attackers controlling the freed region's contents can hijack control flow and execute arbitrary instructions. The vulnerability is runtime-specific and manifests on glibc-based Linux distributions, where allocator behavior enables reliable exploitation.
Root Cause
The root cause is the Use After Free condition inside librsvg that sharp inherits by bundling the dependency. The sharp project did not expose a direct code defect; however, by shipping a vulnerable librsvg build, applications relying on sharp for SVG decoding are exposed to the upstream memory corruption. The glibc allocator behavior influences whether the freed memory can be reclaimed and manipulated by attacker-controlled data.
Attack Vector
The attack vector is local in CVSS terms but reachable through any application pathway that passes untrusted SVG content to sharp. In practice, this includes HTTP file upload endpoints, image proxy services, and content pipelines where SVG files originate from external sources. An attacker crafts an SVG file that triggers the vulnerable code path inside librsvg during parsing. If exploitation succeeds, the attacker executes code with the privileges of the hosting process.
No verified public exploit code examples are available for CVE-2026-114111. Refer to the GitHub Security Advisory GHSA-wq5f-xc86-pv6w and the VulnCheck Advisory on RCE Vulnerability for additional technical context.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-114111
Indicators of Compromise
- Unexpected child processes spawned by Node.js workers that invoke sharp for SVG processing
- Crash signatures or SIGSEGV events in logs originating from librsvg or rsvg-convert code paths
- Outbound network connections from image-processing workers to unknown hosts following SVG uploads
Detection Strategies
- Inventory Node.js applications and confirm the installed sharp version using npm ls sharp across build artifacts and runtime containers
- Software composition analysis (SCA) tooling should flag sharp versions below 0.35.5 as vulnerable
- Monitor upload endpoints for SVG payloads containing unusual element nesting, embedded foreign objects, or malformed references
Monitoring Recommendations
- Alert on process execution anomalies within containers that only expect the Node.js runtime and sharp to run
- Capture memory faults and segmentation violations from image processing workers and forward them to centralized logging
- Track file system writes and new socket connections initiated after SVG decoding operations
How to Mitigate CVE-2026-114111
Immediate Actions Required
- Upgrade sharp to version 0.35.5 or later in all projects, including transitive dependencies
- Rebuild and redeploy container images that bundle sharp to ensure the patched librsvg is included
- Restrict or disable SVG input where business requirements allow until patching is complete
Patch Information
Upgrade sharp to version 0.35.5, which bundles a fixed librsvg build that addresses CVE-2026-96889. Review the GitHub Security Advisory GHSA-wq5f-xc86-pv6w for release details. Validate downstream applications that pin older sharp versions and update lockfiles accordingly.
Workarounds
- Reject SVG uploads at the application layer and process only raster formats such as PNG or JPEG until the patch is applied
- Isolate image processing workloads in sandboxed containers with seccomp or AppArmor profiles limiting syscalls and network access
- Run sharp under a non-glibc runtime, such as a musl-based Alpine image, where the specific exploitation conditions do not apply
# Configuration example
npm install sharp@^0.35.5
npm ls sharp
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

