Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

DOM Clobbering Gadget found in astro's client-side router that leads to XSS

CVE-2024-47885GHSA-m85w-3h95-hcf9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (astro 4.16.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm astro

    Affected
    >= 3.0.0, < 4.16.1
    Fixed in
    4.16.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.9 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:H
EPSS
  • CVE-2024-47885: 0.45% estimated exploitation activity in the next 30 days; percentile 38.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A DOM Clobbering gadget has been discoverd in Astro's client-side router. It can lead to cross-site scripting (XSS) in websites enables Astro's client-side routing and has stored attacker-controlled scriptless HTML elements (i.e., iframe tags with unsanitized name attributes) on the destination pages. Details Backgrounds DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references: [1] https://scnps.co/papers/sp23domclob.pdf [2] https://research.securitum.com/xss-in-amp4email-dom-clobbering/ Gadgets found in Astro We identified a DOM Clobbering gadget in Astro's client-side routing module, specifically in the <ViewTransitions / component. When integrated, this component…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-m85w-3h95-hcf9

  2. Revision 1 · created ·

    Published from osv record GHSA-m85w-3h95-hcf9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-47885

Advisory: DOM Clobbering Gadget found in astro's client-side router that leads to XSS
IDs: CVE-2024-47885, GHSA-m85w-3h95-hcf9
Record: https://patchnext.com/advisories/cve-2024-47885 (revision 2, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: astro 4.16.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm astro: affected >= 3.0.0, < 4.16.1; fixed in 4.16.1

## Suggested inspection (read-only)
- `npm ls astro --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on astro.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m85w-3h95-hcf9 (OSV record GHSA-m85w-3h95-hcf9 lists affected ranges: npm astro >=3.0.0 <4.16.1 (fixed))
- Verified: https://github.com/advisories/GHSA-m85w-3h95-hcf9 (GitHub-reviewed advisory GHSA-m85w-3h95-hcf9 lists affected ranges: npm astro >=3.0.0 <4.16.1)

Commands are suggestions: review each one before running it.

Loading voting…