Skip to content

← Actionable
Low, CVSS 3.5amended

Astro Development Server has Arbitrary Local File Read

CVE-2025-64757GHSA-x3h8-62x9-952g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (astro 5.14.3), 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.

Affected packages

  • npm astro

    Affected
    < 5.14.3
    Fixed in
    5.14.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.5 · CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
  • CVE-2025-64757: 0.43% estimated exploitation activity in the next 30 days; percentile 37.25 (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 A vulnerability has been identified in the Astro framework's development server that allows arbitrary local file read access through the image optimization endpoint. The vulnerability affects Astro development environments and allows remote attackers to read any image file accessible to the Node.js process on the host system. Details - Title: Arbitrary Local File Read in Astro Development Image Endpoint - Type: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - Component: /packages/astro/src/assets/endpoint/node.ts - Affected Versions: Astro v5.x development builds (confirmed v5.13.3) - Attack Vector: Network (HTTP GET request) - Authentication Required: None The vulnerability exists in the Node.js image endpoint handler used during development mode. The endpoint accepts an href parameter that specifies the path to an image file. In development mode, this parameter is processed without adequate path validation, allowing attackers to…

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

    Amended from ghsa record GHSA-x3h8-62x9-952g

  2. Revision 1 · created ·

    Published from osv record GHSA-x3h8-62x9-952g

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-64757

Advisory: Astro Development Server has Arbitrary Local File Read
IDs: CVE-2025-64757, GHSA-x3h8-62x9-952g
Record: https://patchnext.com/advisories/cve-2025-64757 (revision 2, 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: Low (CVSS 3.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: astro 5.14.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm astro: affected < 5.14.3; fixed in 5.14.3

## 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`.

## 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.
- 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-x3h8-62x9-952g (OSV record GHSA-x3h8-62x9-952g lists affected ranges: npm astro >=0 <5.14.3 (fixed))
- Verified: https://github.com/advisories/GHSA-x3h8-62x9-952g (GitHub-reviewed advisory GHSA-x3h8-62x9-952g lists affected ranges: npm astro >=0 <5.14.3)

Commands are suggestions: review each one before running it.

Loading voting…