PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-102984 – Denial of Service (Uncaught Exception) – Astro @astrojs/node Adapter ≤ 11.1.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-102984 is a denial-of-service vulnerability in the @astrojs/node adapter for the Astro web framework, caused by an uncaught exception when processing a malformed Host header. The flaw affects versions up to and including 11.1.2 and carries a CVSS score of 8.2 (High). Under certain configurations, exploitation can crash the entire Node.js process, taking the affected site offline.

Technical details

  • Root cause: The @astrojs/node adapter builds a request URL directly from the incoming Host header. A malformed port value (e.g., a port number that is out of range, or a header containing multiple colon-delimited port segments) produces an invalid URL.
  • Trigger condition: The adapter’s fallback/recovery logic reuses the same malformed host value and also fails, resulting in an uncaught TypeError: Invalid URL before the request reaches routing.
  • Attack vector: Network — an unauthenticated attacker can send a single HTTP request with a crafted Host header directly to the origin server; no authentication or user interaction is required.
  • Impact: In the default standalone configuration, the malformed request results in an HTTP 500 response and the server continues to run. However, when the adapter is configured with staticHeaders: true, the exception is not caught by the synchronous handler and the Node.js process terminates, causing a full denial of service until the process is restarted.
  • Mitigating factor: Reverse proxies or CDNs that reject malformed Host headers before forwarding traffic to the origin prevent this request from reaching the vulnerable code path.
  • This issue affects availability only; it does not permit code execution, data exposure, or data modification.

Affected software

  • @astrojs/node adapter versions up to and including 11.1.2
  • Fixed in @astrojs/node version 11.1.3

Severity

  • CVSS Score: 8.2 (High)
  • Attack Vector: Network

Mitigation and recommended actions

  • Immediate: Upgrade @astrojs/node to version 11.1.3 or later, which fixes the URL-parsing failure.
  • If patching is not immediately possible: Deploy the affected application behind a reverse proxy, load balancer, or CDN configured to reject requests containing malformed or non-standard Host headers before they reach the origin server. Review whether staticHeaders: true is enabled, as this configuration is the one confirmed to result in full process termination rather than a recoverable 500 error.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge