Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.4amended

Astro allows unauthorized third-party images in _image endpoint

CVE-2025-55303GHSA-xf8x-j4p2-f749

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (astro 5.13.2, 4.16.19; @astrojs/node 9.1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm astro

    Affected
    <= 4.16.18>= 5.0.0-alpha.0, < 5.13.2
    Fixed in
    5.13.2, 4.16.19

  • npm @astrojs/node

    Affected
    <= 9.1.0
    Fixed in
    9.1.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source
EPSS
  • CVE-2025-55303: 0.64% estimated exploitation activity in the next 30 days; percentile 50.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary In affected versions of astro, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served. Details On-demand rendered sites built with Astro include an /image endpoint which returns optimized versions of images. The /image endpoint is restricted to processing local images bundled with the site and also supports remote images from domains the site developer has manually authorized (using the image.domains or image.remotePatterns options). However, a bug in impacted versions of astro allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. /image?href=//example.com/image.png. Proof of Concept 1. Create a new minimal Astro project (astro@5.13.0). 2. Configure it to use the Node adapter (@astrojs/node@9.1.0 — newer versions are not impacted): 3. Build the site by running astro build. 4. Run the server, e.g. with astro preview. 5.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xf8x-j4p2-f749

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-xf8x-j4p2-f749

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-55303

Advisory: Astro allows unauthorized third-party images in _image endpoint
IDs: CVE-2025-55303, GHSA-xf8x-j4p2-f749
Record: https://patchnext.com/advisories/cve-2025-55303 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: astro 5.13.2, 4.16.19; @astrojs/node 9.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm astro: affected <= 4.16.18; >= 5.0.0-alpha.0, < 5.13.2; fixed in 5.13.2, 4.16.19
- npm @astrojs/node: affected <= 9.1.0; fixed in 9.1.1

## Suggested inspection (read-only)
- `npm ls astro --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @astrojs/node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on astro, @astrojs/node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xf8x-j4p2-f749 (OSV record GHSA-xf8x-j4p2-f749 lists affected ranges: npm astro >=5.0.0-alpha.0 =0 =0 <9.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-xf8x-j4p2-f749 (GitHub-reviewed advisory GHSA-xf8x-j4p2-f749 lists affected ranges: npm @astrojs/node >=0 =0 =5.0.0-alpha.0 <5.13.2)

Commands are suggestions: review each one before running it.

Loading voting…