{"answers":{"affected":"2 open source packages ship an affected version, including astro.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59731 exists.","fix":"Upgrade astro to 6.4.8 or later.","what":"CVE-2026-59731 is a high-severity authentication bypass vulnerability in withastro astro, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59731 and fix it if it is affected.\n\nWhat it is: CVE-2026-59731 is a high-severity authentication bypass vulnerability in withastro astro, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59731 exists.\n\nAffected packages and fixed versions:\n- astro (npm): affected from 6.4.7; fixed in 6.4.8\n- astro (npm): affected from 6.4.7; fixed in 6.4.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59731/ (Markdown: https://insights.sbomify.com/CVE-2026-59731/index.md)","id":"CVE-2026-59731","markdown":"https://insights.sbomify.com/CVE-2026-59731/index.md","name":"CVE-2026-59731","record":{"aliases":["GHSA-vj59-8hwv-xxmv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Astro web framework","requires_auth":"none","summary":"Attackers can bypass authorization checks in Astro by exploiting a mismatch between URL decoding limits and rewrite path canonicalization, accessing protected routes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-647","name":"Use of Non-Canonical URL Paths for Authorization Decisions"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Astro 6.4.7 Authorization Bypass via Decode Iteration Limit and Rewrite Path Canonicalization Mismatch","id":"CVE-2026-59731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"rclone archive extract allows S3 destination prefix escape via crafted archive paths","id":"CVE-2026-59732"},"packages":[{"ecosystem":"npm","fixed":["6.4.8"],"introduced":["6.4.7"],"last_affected":[],"package":"astro","purl":null,"source":"GHSA-vj59-8hwv-xxmv"},{"ecosystem":"npm","fixed":["6.4.8"],"introduced":["6.4.7"],"last_affected":[],"package":"astro","purl":"pkg:npm/astro","source":"GHSA-vj59-8hwv-xxmv"}],"prev":{"headline":"@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect","id":"CVE-2026-59730"},"products":["astro"],"published":"2026-07-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["withastro"]},"summary":"Attackers can bypass authorization checks in Astro by exploiting a mismatch between URL decoding limits and rewrite path canonicalization, accessing protected routes.","url":"https://insights.sbomify.com/CVE-2026-59731/"}