What is GHSA-54XQ-CGQR-RPM3?

GHSA-54XQ-CGQR-RPM3 is a high-severity security vulnerability in sharp (npm), affecting versions < 0.32.6. It is fixed in 0.32.6.

How severe is GHSA-54XQ-CGQR-RPM3?

GHSA-54XQ-CGQR-RPM3 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of sharp are affected by GHSA-54XQ-CGQR-RPM3?

sharp (npm) versions < 0.32.6 is affected.

Is there a fix for GHSA-54XQ-CGQR-RPM3?

Yes. GHSA-54XQ-CGQR-RPM3 is fixed in 0.32.6. Upgrade to this version or later.

Is GHSA-54XQ-CGQR-RPM3 exploitable, and should I be worried?

Whether GHSA-54XQ-CGQR-RPM3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-54XQ-CGQR-RPM3 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-54XQ-CGQR-RPM3 in sharp

Q: How severe is GHSA-54XQ-CGQR-RPM3?

GHSA-54XQ-CGQR-RPM3 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of sharp are affected by GHSA-54XQ-CGQR-RPM3?

sharp (npm) versions < 0.32.6 is affected.

Q: Is there a fix for GHSA-54XQ-CGQR-RPM3?

Yes. GHSA-54XQ-CGQR-RPM3 is fixed in 0.32.6. Upgrade to this version or later.

Q: Is GHSA-54XQ-CGQR-RPM3 exploitable, and should I be worried?

Whether GHSA-54XQ-CGQR-RPM3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-54XQ-CGQR-RPM3 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-54XQ-CGQR-RPM3?

Upgrade sharp to 0.32.6 or later.

Summary

sharp vulnerability in libwebp dependency CVE-2023-4863

Overview

sharp uses libwebp to decode WebP images and versions prior to the latest 0.32.6 are vulnerable to the high severity https://github.com/advisories/GHSA-j7hp-h8jx-5ppr.

Who does this affect?

Almost anyone processing untrusted input with versions of sharp prior to 0.32.6.

How to resolve this?

Using prebuilt binaries provided by sharp?

Most people rely on the prebuilt binaries provided by sharp.

Please upgrade sharp to the latest 0.32.6, which provides libwebp 1.3.2.

Using a globally-installed libvips?

Please ensure you are using the latest libwebp 1.3.2.

Possible workaround

Add the following to your code to prevent sharp from decoding WebP images.

sharp.block({ operation: ["VipsForeignLoadWebp"] });

Impact

GHSA-54XQ-CGQR-RPM3 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.32.6); upgrading removes the vulnerable code path.

Affected versions

sharp (< 0.32.6)

Security releases

sharp → 0.32.6 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade sharp to 0.32.6 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-54XQ-CGQR-RPM3? GHSA-54XQ-CGQR-RPM3 is a high-severity security vulnerability in sharp (npm), affecting versions < 0.32.6. It is fixed in 0.32.6.
How severe is GHSA-54XQ-CGQR-RPM3? GHSA-54XQ-CGQR-RPM3 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of sharp are affected by GHSA-54XQ-CGQR-RPM3? sharp (npm) versions < 0.32.6 is affected.
Is there a fix for GHSA-54XQ-CGQR-RPM3? Yes. GHSA-54XQ-CGQR-RPM3 is fixed in 0.32.6. Upgrade to this version or later.
Is GHSA-54XQ-CGQR-RPM3 exploitable, and should I be worried? Whether GHSA-54XQ-CGQR-RPM3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-54XQ-CGQR-RPM3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-54XQ-CGQR-RPM3? Upgrade sharp to 0.32.6 or later.