CVE-2026-84376

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-70213 (ENISA EUVD) · GHSA-376h-93r7-7g6f (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 commit Patch Available

commit 05763a0884aa (withastro/astro)

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

https://github.com/withastro/astro/commit/05763a0884aabb1da78a2749d5bb9d41ae620527
GitHub pull request 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 advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmastro @ 7.2.4 (fixes <= 7.2.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
astro—
  • every version up to 7.2.4: fixed in 7.2.4
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 112 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-376h-93r7-7g6f · GitHub severity MODERATE
  14. 2026-11-01 07:38 UTCEchelonGraph re-scored
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-30 00:55 UTCOSV refresh
  18. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-25 13:56 UTCEchelonGraph re-scored
  24. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 73 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-22 13:14 UTCEchelonGraph re-scored
  3. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-18 03:06 UTCEchelonGraph re-scored
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-12 14:53 UTCEchelonGraph re-scored
  15. 2026-10-11 19:18 UTCEchelonGraph re-scored
  16. 2026-10-11 16:35 UTCEchelonGraph re-scored
  17. 2026-10-11 13:52 UTCEchelonGraph re-scored
  18. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-10 02:07 UTCEchelonGraph re-scored
  21. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-09 01:39 UTCEchelonGraph re-scored
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-07 23:41 UTCEchelonGraph re-scored
  26. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-06 14:04 UTCEchelonGraph re-scored
  28. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-10-05 13:46 UTCEchelonGraph re-scored
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-04 13:20 UTCEchelonGraph re-scored
  32. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-10-03 12:52 UTCEchelonGraph re-scored
  34. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-02 07:09 UTCEchelonGraph re-scored
  36. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-01 06:52 UTCEchelonGraph re-scored
  38. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-09-30 06:30 UTCEchelonGraph re-scored
  40. 2026-09-29 06:12 UTCEchelonGraph re-scored
  41. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-09-28 05:54 UTCEchelonGraph re-scored
  43. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-09-27 05:36 UTCEchelonGraph re-scored
  45. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-09-26 04:52 UTCEchelonGraph re-scored
  47. 2026-09-25 02:09 UTCEchelonGraph re-scored
  48. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-09-24 01:51 UTCEchelonGraph re-scored
  50. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  51. 2026-09-23 01:33 UTCEchelonGraph re-scored
  52. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-09-22 01:14 UTCEchelonGraph re-scored
  54. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  55. 2026-09-21 00:56 UTCEchelonGraph re-scored
  56. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-09-20 00:37 UTCEchelonGraph re-scored
  58. 2026-09-19 00:20 UTCEchelonGraph re-scored
  59. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-09-18 00:02 UTCEchelonGraph re-scored
  61. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  62. 2026-09-16 23:44 UTCEchelonGraph re-scored
  63. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  64. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  65. 2026-09-15 23:25 UTCEchelonGraph re-scored
  66. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  67. 2026-09-13 22:23 UTCEchelonGraph re-scored
  68. 2026-09-12 22:05 UTCEchelonGraph re-scored
  69. 2026-09-11 21:47 UTCEchelonGraph re-scored
  70. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  71. 2026-09-10 21:29 UTCEchelonGraph re-scored
  72. 2026-09-09 04:55 UTCEchelonGraph re-scored
  73. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2026-84376?
CVE-2026-84376 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-84376 published?
The CVE record for CVE-2026-84376 was published on September 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-84376 actively exploited?
CVE-2026-84376 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84376?
CVE-2026-84376 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84376?
A fix for CVE-2026-84376 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84376 are linked in the Vendor Advisories panel on this page.

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.