Is astro 7.2 vulnerable?

npm · 11 releases from 7.2.0 to 7.2.10 · latest astro is 7.4.4 · checked 1 Nov 2026

Yes: 2 known advisories

Yes. astro 7.2.10, the last 7.2 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2026-114128, CVE-2026-114127. 2 more affect earlier 7.2.x releases. Upgrade to 7.3.3 or later to fix all of them.

Upgrade with:npm install astro@7.3.3

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting astro 7.2.10

  • MediumCVE-2026-114128GHSA-98hj-9722-w3j822 Oct 2026

    Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering

    Affected
    <7.3.2
    Fixed in
    7.3.2
  • LowCVE-2026-114127GHSA-mpr7-6m5w-76rw22 Oct 2026

    Astro: Arbitrary CSS injection in Astro View Transitions

    Affected
    >=7.1.0 <7.3.3
    Fixed in
    7.3.3

Fixed within 7.2.x, affecting earlier releases

  • CriticalGHSA-26w7-cxv4-gfx28 Sept 2026

    Astro: Remote code execution through AVIF image optimization

    Affected
    <7.2.8
    Fixed in
    7.2.8
  • MediumCVE-2026-84376GHSA-376h-93r7-7g6f8 Sept 2026

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

    Affected
    <7.2.4
    Fixed in
    7.2.4

Which of your client projects are still on astro 7.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact astro version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other astro versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.