# GHSA-26w7-cxv4-gfx2: Astro: Remote code execution through AVIF image optimization

> Remote code execution via malicious AVIF images processed by Astro's default image optimization service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2026

## What is GHSA-26w7-cxv4-gfx2?

GHSA-26w7-cxv4-gfx2 is a code injection vulnerability in astro, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-26w7-cxv4-gfx2?

2 open source packages ship an affected version, including astro.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | All versions | 7.2.8 |
| `astro` | npm | All versions | 7.2.8 |

## How do I fix GHSA-26w7-cxv4-gfx2?

Upgrade astro to 7.2.8 or later.

## Is GHSA-26w7-cxv4-gfx2 being exploited?

There is no known exploitation of GHSA-26w7-cxv4-gfx2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-26w7-cxv4-gfx2 and fix it if it is affected.

What it is: GHSA-26w7-cxv4-gfx2 is a code injection vulnerability in astro, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-26w7-cxv4-gfx2 in the wild and no public exploit code.

Affected packages and fixed versions:
- astro (npm): affected all versions; fixed in 7.2.8
- astro (npm): affected all versions; fixed in 7.2.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-26w7-cxv4-gfx2/ (Markdown: https://insights.sbomify.com/GHSA-26w7-cxv4-gfx2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-26w7-cxv4-gfx2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-26w7-cxv4-gfx2/
Summaries are generated and may contain mistakes; the official description above is the record.