Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-126364

Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems

Products / packages withastro astro · @astrojs/node · astro

Published

Share

Severity and exploitation

Not in CISA KEVSource: MODERATE

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 02:25:31 UTC
GitHub_M · CVSS:4.0 · 6.3
Assessment vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
OSV · CVSS:4.0 · 6.3
Assessment vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

medium6.3

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Some package fixes recorded

Fix versions are recorded for 1 of 2 mapped packages. Check each release branch and any separate product guidance.

What this means

Astro versions 5.14.3 to 7.4.6 are vulnerable when used with @astrojs/node on case-sensitive filesystems, allowing unauthenticated attackers to read image files from outside the output directory if a case-variant sibling directory exists. The image endpoint checks paths case-insensitively. Only image files can be read.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

withastro · GitHub_M

astro

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 5.14.3, < 7.4.7

unaffected

unknown

Other versions: unknown

Packages

Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.

@astrojs/node npm
Affected range Recorded fix
Earlier releases through 11.1.11 (inclusive)Semantic versionsNot recorded

Version evidence: OSV · GHSA-r3h5-4585-7x3w

View original version evidence (0 explicit versions)
astro npm
Affected range Recorded fix
From 5.14.3 before 7.4.7Semantic versions7.4.7

Version evidence: OSV · GHSA-r3h5-4585-7x3w

View original version evidence (0 explicit versions)

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

Summary

The /_image endpoint used by the @astrojs/node adapter checks that a requested local image is inside the build output directory before reading it from disk. That check compared paths case-insensitively. On case-sensitive filesystems (such as Linux), a directory whose path differs from the output directory only by letter case is a different directory, but it passed the check.

For example, with the client output directory at /srv/app/dist/client/, a request such as:

/_image?href=/../../DIST/client/secret.png&w=32&f=png

resolved to /srv/app/DIST/client/secret.png and was served, even though that file is outside the output directory.

Impact

An unauthenticated attacker can read image files from outside the output directory, but only when all of the following are true:

  • The site uses on-demand rendering with the @astrojs/node adapter.
  • The server runs on a case-sensitive filesystem.
  • A directory exists whose path matches the output directory except for letter case (for example DIST/client next to dist/client). Such a layout is unusual, and the attacker cannot create it.

Only files the image service accepts can be read. Raster images are returned after resizing; SVG files are returned unchanged. Other file types fail during processing. Plain path traversal outside the output directory (for example /../../secret.png) was already rejected and is not affected.

Affected versions

astro >= 5.14.3, <= 7.4.6, when used with @astrojs/node (all versions up to 11.1.11). The vulnerable image endpoint is provided by astro and used by the @astrojs/node adapter.

Patches

Fixed in astro 7.4.7. The path check now compares paths exactly, and only ignores letter case for Windows drive-letter paths. The fix ships in astro, so upgrading @astrojs/node alone is not enough.

Workarounds

Upgrade to astro 7.4.7 or later. Before upgrading, make sure no directory next to the build output directory has a path that differs from it only by letter case.

Credits

Reported by @zachariah-mithani.

References

5 sources
withastro/astro · security/advisories/GHSA-r3h5-4585-7x3w
Security advisoryGitHub_M
withastro/astro · commit 7da442b
PatchGitHub_M
withastro/astro · releases/tag/astro@7.4.7
Release notesGitHub_M
nvd.nist.gov/vuln/detail/CVE-2026-126364
Security advisory
withastro/astro · repository
Source reference

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-126364

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory

GitHub_M

Related →
CWE-178 ↗

CWE-178: Improper Handling of Case Sensitivity

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-11-12
CISA-ADP

Additional data publisher

2026-11-13

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-126364

    Observed 2026-11-13T01:07:34.278Z · upstream updated 2026-11-13T00:37:58.791Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-13T00:37:48.200390Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.