Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-102984

Vulnerability in @astrojs/node (CVE-2026-102984)

Summary

Vulnerability in @astrojs/node (CVE-2026-102984). Risk of unauthorized operations or information disclosure. Exploitable via Host. Mitigation: upgrade to 11.1.3 or later.

Original description

The description as published by the source.

Summary

In the Astro Node adapter, a request whose Host header contains a malformed port (for example example.com:65536 or example.com:8080:8080) produced an invalid request URL. The fallback intended to recover from an unparseable URL reused the same malformed host, so it failed again and raised an uncaught TypeError: Invalid URL while the request was being built, before any route ran.

Impact

The effect depends on the adapter configuration:

  • Default configuration (standalone): the request returns 500 Internal Server Error and the server continues running.
  • With the opt-in staticHeaders: true option: the throw reaches a synchronous HTTP handler that does not catch it, becoming an uncaughtException that terminates the process.

This is an availability-only issue. It does not expose data or allow code execution. Triggering it requires sending a hand-crafted Host header, and many proxies and CDNs reject malformed hosts before they reach the origin.

Affected versions

@astrojs/node <= 11.1.2.

Patches

Fixed in @astrojs/node 11.1.3. When the incoming host cannot be parsed, the request URL now degrades to a host the server controls, so the request is handled instead of throwing. Hosts carrying more than a single hostname:port pair are also rejected during host validation.

Workarounds

Upgrade to @astrojs/node 11.1.3 or later. Deployments that terminate malformed Host headers at a reverse proxy or CDN are not reachable through this…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-102984 has been found in @astrojs/node.
Attackers can target a specific entry point like Host over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @astrojs/node to 11.1.3 or later.
If unsure, ask your IT team or search "@astrojs/node CVE-2026-102984" on the vendor's site.

CVE-2026-102984 (@astrojs/node) — CWE-248
Attack surface: Host / standalone / uncaughtException
Patched: 11.1.3 — apply immediately
Workaround: Upgrade to @astrojs/node 11.1.3 or later.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-248) exists in @astrojs/node. Attackers reach the vulnerable code path via Host.

📍 Affected scope

Check the vendor advisory for the affected versions of @astrojs/node. Attack surface: Host / standalone / uncaughtException.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 11.1.3.

🛡️ Workaround

Workaround: Upgrade to @astrojs/node 11.1.3 or later.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@astrojs/node' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@astrojs/node' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @astrojs/node を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Upgrade to `@astrojs/node` 11.1.3 or later.

    パッチが適用されるまでの応急処置として、Upgrade to @astrojs/node 11.1.3 or later. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @astrojs/node to 11.1.3

    ステージング環境で 11.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @astrojs/node
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details