CVE-2026-84376

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Astro is a web framework for content-driven websites. Prior to 7.2.4, Astro stripped a configured non-root base path from request pathnames using a string-prefix check without verifying a path-segment boundary. With base "/app", a request to "/appX/admin" resolved internally to the protected "/admin" route while middleware observed "/appX/admin" in context.url.pathname. In applications that authorize base-prefixed routes by inspecting context.url.pathname, an unauthenticated remote attacker could bypass pathname-based middleware authorization and reach protected routes. This issue is fixed in version 7.2.4.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 2, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

[email protected]

Patch available: withastro/astro [email protected]

https://github.com/withastro/astro/releases/tag/[email protected]
github_commit Patch Available

commit 05763a0884aa (withastro/astro)

Patch available: withastro/astro [email protected] (contains commit 05763a0884aa)

https://github.com/withastro/astro/commit/05763a0884aabb1da78a2749d5bb9d41ae620527
github_pr Patch Available

Respect path-segment boundaries when stripping the configured base

Patch available: withastro/astro [email protected] (PR #17701 merged 2026-08-19)

https://github.com/withastro/astro/pull/17701
github Patch Available

Authorization bypass from missing path-segment boundary check when stripping the configured base · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-376h-93r7-7g6f

Vendor Advisories for CVE-2026-84376(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
astro—7.2.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 00:20 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:02 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 23:44 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 23:25 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 22:23 UTCEG score recompute
  12. 2026-09-12 22:05 UTCEG score recompute
  13. 2026-09-11 21:47 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 21:29 UTCEG score recompute
  17. 2026-09-09 04:55 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 04:37 UTCEG score recompute
  20. 2026-09-07 04:18 UTCEG score recompute
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-06 03:59 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-05 03:41 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 5 more
  1. 2026-09-04 03:23 UTCEG score recompute
  2. 2026-09-04 02:56 UTCEG score recompute
  3. 2026-09-02 17:35 UTCEG score recompute
  4. 2026-09-02 16:33 UTCEG score recompute
  5. 2026-09-02 16:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84376?
CVE-2026-84376 is a medium vulnerability published on September 2, 2026. Astro is a web framework for content-driven websites. Prior to 7.2.4, Astro stripped a configured non-root base path from request pathnames using a string-prefix check without verifying a path-segment boundary. With base "/app", a request to "/appX/admin" resolved internally to the protected…
When was CVE-2026-84376 disclosed?
CVE-2026-84376 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84376 actively exploited?
CVE-2026-84376 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.3% of all scored CVEs.
What is the CVSS score of CVE-2026-84376?
CVE-2026-84376 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-84376?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84376, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84376

Explore →

Is Your Infrastructure Affected by CVE-2026-84376?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs