What is GHSA-26W7-CXV4-GFX2?

GHSA-26W7-CXV4-GFX2 is a critical-severity out-of-bounds read vulnerability in astro (npm), affecting versions < 7.2.8. It is fixed in 7.2.8. A read operation accesses a memory location beyond the intended buffer boundary.

How severe is GHSA-26W7-CXV4-GFX2?

GHSA-26W7-CXV4-GFX2 has a CVSS score of 9.8 (Critical). 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 astro are affected by GHSA-26W7-CXV4-GFX2?

astro (npm) versions < 7.2.8 is affected.

Is there a fix for GHSA-26W7-CXV4-GFX2?

Yes. GHSA-26W7-CXV4-GFX2 is fixed in 7.2.8. Upgrade to this version or later.

Is GHSA-26W7-CXV4-GFX2 exploitable, and should I be worried?

Whether GHSA-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2 in astro

Q: How severe is GHSA-26W7-CXV4-GFX2?

GHSA-26W7-CXV4-GFX2 has a CVSS score of 9.8 (Critical). 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 astro are affected by GHSA-26W7-CXV4-GFX2?

astro (npm) versions < 7.2.8 is affected.

Q: Is there a fix for GHSA-26W7-CXV4-GFX2?

Yes. GHSA-26W7-CXV4-GFX2 is fixed in 7.2.8. Upgrade to this version or later.

Q: Is GHSA-26W7-CXV4-GFX2 exploitable, and should I be worried?

Whether GHSA-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2?

Upgrade astro to 7.2.8 or later.

Summary

Astro: Remote code execution through AVIF image optimization

A vulnerability in libheif, used by the default Sharp image service in Astro, can lead to remote code execution when a malicious AVIF image is optimized.

Projects are affected when an attacker can cause Astro to process an untrusted AVIF image.

The fix was released in Astro 7.2.8, which requires Sharp 0.35.4.

Impact

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

GHSA-26W7-CXV4-GFX2 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. 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 (7.2.8); upgrading removes the vulnerable code path.

Affected versions

astro (< 7.2.8)

Security releases

astro → 7.2.8 (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 astro to 7.2.8 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-26W7-CXV4-GFX2? GHSA-26W7-CXV4-GFX2 is a critical-severity out-of-bounds read vulnerability in astro (npm), affecting versions < 7.2.8. It is fixed in 7.2.8. A read operation accesses a memory location beyond the intended buffer boundary.
How severe is GHSA-26W7-CXV4-GFX2? GHSA-26W7-CXV4-GFX2 has a CVSS score of 9.8 (Critical). 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 astro are affected by GHSA-26W7-CXV4-GFX2? astro (npm) versions < 7.2.8 is affected.
Is there a fix for GHSA-26W7-CXV4-GFX2? Yes. GHSA-26W7-CXV4-GFX2 is fixed in 7.2.8. Upgrade to this version or later.
Is GHSA-26W7-CXV4-GFX2 exploitable, and should I be worried? Whether GHSA-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2 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-26W7-CXV4-GFX2? Upgrade astro to 7.2.8 or later.