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

Advisory record · `GHSA-376h-93r7-7g6f`

- **Identifiers:** `GHSA-376h-93r7-7g6f` · `CVE-2026-84376`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-187](https://cwe.mitre.org/data/definitions/187.html)
- **Tags:** [CWE-187](https://agentprime.io/advisories/tag/cwe-187.md)
- **Published:** 8 Sept 2026
- **Updated:** 8 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Sept 2026, 21:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `astro` (npm): affected `<7.2.4`; fixed in `7.2.4`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0071, the 53rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 8 Sept 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-376h-93r7-7g6f](https://github.com/advisories/GHSA-376h-93r7-7g6f)
- [OSV: GHSA-376h-93r7-7g6f](https://osv.dev/vulnerability/GHSA-376h-93r7-7g6f)
- <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>
- <https://github.com/withastro/astro/releases/tag/astro@7.2.4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-376h-93r7-7g6f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-376h-93r7-7g6f/>. Everything for agents: <https://agentprime.io/llms.txt>.