Skip to main content
CVE-2026-126364VulnerabilityPublished

@astrojs/node can read files · Astro: Image endpoint

Affects @astrojs/nodeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-126364· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 7.4.7 when convenient.

Data as of 13 Nov 2026, 19:37 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.3
Patch
Available – fixed in 7.4.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade astro to 7.4.7.

Affected software

ProductAffectedFixed in
npm@astrojs/nodeAffected
  • <=11.1.11
Fixed in–
npmastroAffected
  • >=5.14.3 <7.4.7
Fixed in
  • 7.4.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade astro to version 7.4.7 or later, which fixes the path validation logic to compare paths exactly and only ignore case for Windows drive letters. Upgrading @astrojs/node alone is insufficient since the fix is in astro. Before upgrading, ensure no directory exists next to the build output directory that differs only by letter case to prevent exploitation.

Description

A path validation flaw in the /_image endpoint of the @astrojs/node adapter allows reading image files from directories that differ only by letter case from the build output directory on case-sensitive filesystems. This occurs because the path check was case-insensitive, permitting access to files outside the intended directory if a case-variant sibling directory exists. The issue affects astro versions from 5.14.3 up to 7.4.6 and is fixed in 7.4.7.

References

Community reviews

Loading reviews…