Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-59731 – Authentication Bypass – Astro 6.4.7

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

Summary

CVE-2026-59731 is a high-severity authentication bypass vulnerability in the Astro web framework (withastro/astro), affecting version 6.4.7. The flaw stems from a URL canonicalization mismatch between middleware-level authorization logic and the rewrite route-matching stage, enabling unauthenticated remote attackers to access middleware-protected routes by supplying a sufficiently encoded URL path. It carries a CVSS v3.1 base score of 8.2 (High) and is classified under CWE-647 (Use of Non-Canonical URL Paths for Authorization Decisions).

Technical details

  • Root cause: Astro’s iterative URI decoder applies a fixed maximum number of decoding passes. When that cap is reached, the framework makes the authorization decision based on a partially decoded pathname rather than the fully resolved one (CWE-647). The rewrite route-matching stage that executes after middleware authorization performs one additional decodeURI() call, resolving the path to a different, fully decoded representation — one that may match a protected route the authorization check never evaluated.
  • Trigger conditions: The target application must be running Astro in Server-Side Rendering (SSR) mode with middleware that enforces pathname-based access control, and rewrite route matching must be active downstream of the middleware authorization check.
  • Attack vector: A remote, unauthenticated attacker sends an HTTP request whose URL path is encoded enough times to exhaust the decoder’s iteration limit. Middleware evaluates the obfuscated, partially decoded path, finds no match against protected route patterns, and allows the request to proceed. The downstream rewrite router then performs its final decodeURI() pass, resolving the path to the intended protected route (e.g., /admin) and serving the protected content.
  • Impact: Unauthenticated access to middleware-protected routes. CVSS assigns high confidentiality impact (exposure of protected content) and low integrity impact. No availability impact.

This vulnerability continues a documented class of URL normalization/decoding inconsistency flaws in Astro, following CVE-2025-64765 and CVE-2025-66202, which exploited similar encoding bypass techniques against earlier Astro middleware implementations.

Affected software

  • withastro/astro version 6.4.7

Severity

CVSS v3.1 Base Score: 8.2 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Astro to version 6.4.8, which contains the vendor fix addressing the URL decoder canonicalization mismatch (commit 27c80ea, pull request #17109).
  • If immediate patching is not possible: Apply WAF or reverse-proxy rules to reject requests whose URL paths contain excessive consecutive levels of percent-encoding before they reach the application, and restrict internet-facing access to Astro SSR applications where operationally feasible.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

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