{"answers":{"affected":"2 open source packages ship an affected version, including @astrojs/node.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55207 exists.","fix":"Upgrade @astrojs/node to 9.4.1 or later.","what":"CVE-2025-55207 is a medium-severity vulnerability in withastro astro, published on 15 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55207 and fix it if it is affected.\n\nWhat it is: CVE-2025-55207 is a medium-severity vulnerability in withastro astro, published on 15 Aug 2025. 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-2025-55207 exists.\n\nAffected packages and fixed versions:\n- @astrojs/node (npm): affected all versions; fixed in 9.4.1\n- @astrojs/node (npm): affected all versions; fixed in 9.4.1\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-2025-55207/ (Markdown: https://insights.sbomify.com/CVE-2025-55207/index.md)","id":"CVE-2025-55207","markdown":"https://insights.sbomify.com/CVE-2025-55207/index.md","name":"CVE-2025-55207","record":{"aliases":["GHSA-9x9c-ghc5-jhw9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Astro web framework","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via crafted links in specific Astro Node adapter configurations, enabling phishing attacks.","user_interaction":"not_required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Astro is a web framework for content-driven websites. Following CVE-2025-54793 there's still an Open Redirect vulnerability in a subset of Astro deployment scenarios prior to version 9.4.1. Astro 5.12.8 addressed CVE-2025-54793 where https://example.com//astro.build/press would redirect to the external origin //astro.build/press. However, with the Node deployment adapter in standalone mode and trailingSlash set to \"always\" in the Astro configuration, https://example.com//astro.build/press still redirects to //astro.build/press. This affects any user who clicks on a specially crafted link pointing to the affected domain. Since the domain appears legitimate, victims may be tricked into trusting the redirected page, leading to possible credential theft, malware distribution, or other phishing-related attacks. This issue has been patched in version 9.4.1.","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":"@astrojs/node's trailing slash handling causes open redirect issue","id":"CVE-2025-55207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Chamilo LMS has Stored Cross Site Scripting on Social Networks Uploaded Files","id":"CVE-2025-55208"},"packages":[{"ecosystem":"npm","fixed":["9.4.1"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":null,"source":"GHSA-9x9c-ghc5-jhw9"},{"ecosystem":"npm","fixed":["9.4.1"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":"pkg:npm/%40astrojs/node","source":"GHSA-9x9c-ghc5-jhw9"}],"prev":{"headline":"Capsule tenant owners with \"patch namespace\" permission can hijack system namespaces label","id":"CVE-2025-55205"},"products":["astro"],"published":"2025-08-15","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-15","vendors":["withastro"]},"summary":"Attackers can redirect users to malicious sites via crafted links in specific Astro Node adapter configurations, enabling phishing attacks.","url":"https://insights.sbomify.com/CVE-2025-55207/"}