CVE-2026-59730

{"id": "CVE-2026-59730", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-59730", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-28T13:48:33.961696Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 2.1, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "ACTIVE", "attackComplexity": "HIGH", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "withastro", "product": "astro", "versions": [{"status": "affected", "version": ">= 8.1.0, < 11.0.2"}]}]}], "published": "2026-07-27T21:17:05.843", "references": [{"url": "https://github.com/withastro/astro/commit/eb6f97e391ee587747e37609c255c7cd4b9cce3c", "source": "security-advisories@github.com"}, {"url": "https://github.com/withastro/astro/pull/17252", "source": "security-advisories@github.com"}, {"url": "https://github.com/withastro/astro/releases/tag/@astrojs/node@11.0.2", "source": "security-advisories@github.com"}, {"url": "https://github.com/withastro/astro/security/advisories/GHSA-r557-wffq-wvrc", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-601"}]}], "descriptions": [{"lang": "en", "value": "Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \\ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2."}, {"lang": "es", "value": "Astro es un framework web para sitios web basados en contenido. En las versiones 8.1.0 a 11.0.1, cuando trailingSlash: \u2019always\u2019 est\u00e1 configurado, el gestor de archivos est\u00e1ticos del servidor independiente @astrojs/node a\u00f1ade una barra final a las rutas de solicitud y emite una redirecci\u00f3n 301. Las rutas que comienzan con /\\ (barra-barra invertida) no eran reconocidas como rutas internas, por lo que el gestor devolv\u00eda la ruta original en el encabezado Location. Debido a que los navegadores tratan \\ como / seg\u00fan la especificaci\u00f3n de URL de WHATWG, la redirecci\u00f3n resultante podr\u00eda resolverse en un host externo. Precondiciones para la explotaci\u00f3n: trailingSlash: \u2019always\u2019 debe estar configurado (no es el valor predeterminado; el valor predeterminado es \u2019ignore\u2019), la ruta de solicitud no debe tener una extensi\u00f3n de archivo en su segmento final, y un atacante debe entregar el enlace manipulado a un usuario. Este problema ha sido solucionado en la versi\u00f3n 11.0.2."}], "lastModified": "2026-10-24T13:10:00.147", "sourceIdentifier": "security-advisories@github.com"}