Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.3%top 81%

CVE-2026-59731: CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions in withastro astro

0
High
VulnerabilityCVE-2026-59731cvecve-2026-59731cwe-647
Published: 07/08/2026 (07/08/2026, 16:27:18 UTC)
Source: CVE Database V5
Vendor/Project: withastro
Product: astro

Description

Astro is a web framework for content-driven websites. Version 6.4.7 performs authorization decisions on a partially decoded pathname after reaching the iterative URL decoder limit, while later rewrite route matching performs an additional decodeURI() operation and can resolve the request to a protected route. This issue is fixed in version 6.4.8.

CVSS v3.1

Score 8.2high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected software

Affected versions
=6.4.7

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/16/2026, 10:05:50 UTC

Technical Analysis

CVE-2026-59731 affects the Astro web framework version 6.4.7. The vulnerability arises because authorization decisions are performed on a partially decoded URL path after the iterative URL decoder limit is reached. However, subsequent route matching performs an additional decodeURI() operation, which can resolve the request to a protected route that should not be accessible. This mismatch in decoding steps leads to improper authorization enforcement. The issue is addressed in version 6.4.8.

Potential Impact

An attacker can potentially bypass authorization controls by exploiting the difference in URL decoding between the authorization check and the route matching, gaining unauthorized access to protected routes. The CVSS score of 8.2 (high severity) reflects the network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact with limited integrity impact.

Mitigation Recommendations

Upgrade to Astro version 6.4.8 or later, where this vulnerability has been fixed. No other mitigation guidance is provided or necessary as the fix addresses the root cause.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-07-06T15:34:16.917Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a4e81d8c9d9e3dbe3746a4a

Added to database: 07/08/2026, 16:59:04 UTC

Last enriched: 07/16/2026, 10:05:50 UTC

Last updated: 08/22/2026, 10:52:10 UTC

Views: 105

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses