chore(deps): Update dependency astro to v7.2.8 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
astro (source)	7.2.0 → 7.2.8

---

Astro: Authorization bypass from missing path-segment boundary check when stripping the configured base

CVE-2026-84376 / GHSA-376h-93r7-7g6f

More information

Details

Summary

Astro stripped a configured base path from request pathnames using a string-prefix check that did not verify a path-segment boundary. With base: "/app", a request to /appX/admin was treated as being under the base and resolved internally to the /admin route, while middleware still observed the public pathname /appX/admin. Middleware that authorizes routes by inspecting context.url.pathname could therefore be bypassed.

Impact

An unauthenticated remote attacker can bypass pathname-based middleware authorization in applications that:

• Configure a non-root base.
• Protect base-prefixed routes in middleware using context.url.pathname.

Because routing and middleware resolved different effective pathnames, a request such as /appX/admin (or other single-character extensions like /app2/admin or /app-/admin) reached the protected /admin route without passing the middleware check that guards /app/admin. Astro's authentication guide demonstrates protecting routes in middleware via context.url.pathname, so this is a reasonable and expected pattern.

Affected versions

astro <= 7.2.3.

Patches

Fixed in astro 7.2.4. Base stripping now requires the pathname to equal the base without its trailing slash, or to be followed by a /, so a prefix that does not end on a path-segment boundary is no longer treated as being under the base. Routing and context.url.pathname now resolve the same pathname.

Workarounds

Upgrade to astro 7.2.4 or later. As a mitigation before upgrading, avoid relying solely on prefix checks of context.url.pathname for authorization, or reject requests whose pathname does not begin with the configured base followed by a path-segment boundary.

Credits

Reported by @​Ryoga-exe.

Severity

• CVSS Score: 6.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/withastro/astro/security/advisories/GHSA-376h-93r7-7g6f
• https://nvd.nist.gov/vuln/detail/CVE-2026-84376
• https://github.com/withastro/astro/pull/17701
• https://github.com/withastro/astro/commit/05763a0884aabb1da78a2749d5bb9d41ae620527
• https://github.com/withastro/astro/releases/tag/astro@7.2.4
• https://github.com/advisories/GHSA-376h-93r7-7g6f

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Astro: Remote code execution through AVIF image optimization

GHSA-26w7-cxv4-gfx2

More information

Details

A vulnerability in libheif, used by the default Sharp image service in Astro, can lead to remote code execution when a malicious AVIF image is optimized.

Projects are affected when an attacker can cause Astro to process an untrusted AVIF image.

The fix was released in Astro 7.2.8, which requires Sharp 0.35.4.

Severity

• CVSS Score: 9.8 / 10 (Critical)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

• https://github.com/strukturag/libheif/security/advisories/GHSA-g89c-p67h-r497
• https://github.com/withastro/astro/security/advisories/GHSA-26w7-cxv4-gfx2
• https://github.com/withastro/astro/commit/ecb4082131490b4fe9a56aa44fda84b54ef8967b
• https://github.com/withastro/astro/releases/tag/astro@7.2.8
• https://github.com/advisories/GHSA-26w7-cxv4-gfx2

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

• If you want to rebase/retry this PR, check this box

[github-actions]

🎉 Welcome @renovate[bot]! Thank you for your first pull request to mars! We're excited to have you as a contributor. Our team will review your PR soon. In the meantime, please ensure all CI checks pass.