<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Sharp (&lt; 0.35.4) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/sharp--0.35.4/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 08 Sep 2026 21:50:11 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/sharp--0.35.4/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Critical Remote Code Execution Vulnerabilities in libheif Affecting Sharp</title><link>https://feed.craftedsignal.io/briefs/2026-09-sharp-libheif-vulnerabilities/</link><pubDate>Tue, 08 Sep 2026 21:50:11 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-sharp-libheif-vulnerabilities/</guid><description>Multiple critical vulnerabilities in the libheif library, including CVE-2026-84383, enable potential remote code execution via malicious AVIF image processing in applications using the sharp npm package.</description><content:encoded><![CDATA[<p>Security researchers have identified multiple critical vulnerabilities within the libheif library, a dependency used by the sharp npm package for image processing. The vulnerabilities, notably tracked as CVE-2026-84383, arise during the parsing of HEIF/AVIF image formats. If an application using an affected version of sharp processes a specially crafted, malicious AVIF image, it can trigger memory corruption leading to potential remote code execution (RCE) on glibc-based Linux systems.</p>
<p>The impact is contingent on how the application handles untrusted image input. While the upstream libheif vulnerability is classified as critical, the sharp package maintainers have downgraded the severity to high as sharp itself does not provide native networking features. However, the risk remains significant for any system that ingests and processes images from external or untrusted sources. Users are strongly urged to upgrade to sharp version 0.35.4 or later, which incorporates the patched libheif version 1.23.2.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation could result in full remote code execution on the underlying host operating system. This vulnerability affects any service or infrastructure utilizing the sharp npm package (versions prior to 0.35.4) to decode HEIF/AVIF image files. Targeted sectors include web applications, content management systems, and image processing pipelines that accept user-submitted files.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade all instances of the sharp npm package to version 0.35.4 or later immediately.</li>
<li>For environments unable to update immediately, apply the code-level blocklist to disable HEIF/AVIF decoding: sharp.block({ operation: [&quot;VipsForeignLoadHeif&quot;] });.</li>
<li>Ensure the Node.js runtime environment is compiled as a Position Independent Executable (PIE) to provide exploit mitigations against RCE attempts, noting that official Node.js binaries may lack this configuration by default.</li>
<li>Audit image processing pipelines to identify and isolate services currently handling untrusted AVIF or HEIF file uploads.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>rce</category><category>image-processing</category><category>library-vulnerability</category></item></channel></rss>