<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Nov 2026 18:40:28 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-114128</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-114128</link>
      <description>&lt;p&gt;Astro is a web framework for content-driven websites. Prior to 7.3.2, Astro&amp;#39;s JSX and MDX rendering pipeline treats string children of script and style elements as trusted HTML without distinguishing compiler-generated literal content from dynamic expression values. An application that passes attacker-controlled data directly as a dynamic child can allow a value containing a closing script or style tag to terminate the element and inject arbitrary HTML and JavaScript. Other JSX expression contexts escape dynamic strings automatically; the issue is limited to script and style children rendered through the astro:jsx renderer, including MDX components. Successful exploitation can produce reflected or stored cross-site scripting under the application&amp;#39;s origin. This issue is fixed in 7.3.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Astro is a web framework for content-driven websites. Prior to 7.3.2, Astro&amp;#39;s JSX and MDX rendering pipeline treats string children of script and style elements as trusted HTML without distinguishing compiler-generated literal content from dynamic expression values. An application that passes attacker-controlled data directly as a dynamic child can allow a value containing a closing script or style tag to terminate the element and inject arbitrary HTML and JavaScript. Other JSX expression contexts escape dynamic strings automatically; the issue is limited to script and style children rendered through the astro:jsx renderer, including MDX components. Successful exploitation can produce reflected or stored cross-site scripting under the application&amp;#39;s origin. This issue is fixed in 7.3.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-114128</guid>
    </item>
    <item>
      <title>GHSA-98hj-9722-w3j8 — Astro: Reflected/Stored XSS via unescaped &lt;script&gt;/&lt;style&gt; tag content in JSX/MDX rendering</title>
      <link>https://db.gcve.eu/vuln/ghsa-98hj-9722-w3j8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: astro&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Astro&amp;#39;s JSX and MDX rendering pipeline treated string children of `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` elements as trusted HTML. When a dynamic value was passed through a JSX expression, such as `&amp;lt;script&amp;gt;{value}&amp;lt;/script&amp;gt;`, an attacker-controlled value containing `&amp;lt;/script&amp;gt;` or `&amp;lt;/style&amp;gt;` could terminate the element and inject arbitrary HTML and JavaScript.&lt;/p&gt;
&lt;p&gt;Other JSX expression contexts escaped dynamic strings automatically. This behavior was limited to `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` children rendered through Astro&amp;#39;s `astro:jsx` renderer, including MDX components.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The affected rendering paths marked all string children of `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` elements as safe HTML, without distinguishing literal content generated by the compiler from dynamic expression values. An application was vulnerable when attacker-controlled data, such as a query parameter or CMS field, was interpolated directly into one of these elements.&lt;/p&gt;
&lt;p&gt;For example, a value containing `&amp;lt;/script&amp;gt;&amp;lt;script&amp;gt;alert(1)&amp;lt;/script&amp;gt;` passed to `&amp;lt;script&amp;gt;{value}&amp;lt;/script&amp;gt;` was emitted without escaping. The browser interpreted the first closing tag as markup and executed the injected script.&lt;/p&gt;
&lt;p&gt;The fix preserves raw rendering for literal script and style content while escaping dynamic string children like other JSX expression values.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Affected applications could be vulnerable to reflected or stored cross-site scripting. Exploitation required an application to pass attacker-controlled data directly as a dynamic c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: astro&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Astro&amp;#39;s JSX and MDX rendering pipeline treated string children of `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` elements as trusted HTML. When a dynamic value was passed through a JSX expression, such as `&amp;lt;script&amp;gt;{value}&amp;lt;/script&amp;gt;`, an attacker-controlled value containing `&amp;lt;/script&amp;gt;` or `&amp;lt;/style&amp;gt;` could terminate the element and inject arbitrary HTML and JavaScript.&lt;/p&gt;
&lt;p&gt;Other JSX expression contexts escaped dynamic strings automatically. This behavior was limited to `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` children rendered through Astro&amp;#39;s `astro:jsx` renderer, including MDX components.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The affected rendering paths marked all string children of `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` elements as safe HTML, without distinguishing literal content generated by the compiler from dynamic expression values. An application was vulnerable when attacker-controlled data, such as a query parameter or CMS field, was interpolated directly into one of these elements.&lt;/p&gt;
&lt;p&gt;For example, a value containing `&amp;lt;/script&amp;gt;&amp;lt;script&amp;gt;alert(1)&amp;lt;/script&amp;gt;` passed to `&amp;lt;script&amp;gt;{value}&amp;lt;/script&amp;gt;` was emitted without escaping. The browser interpreted the first closing tag as markup and executed the injected script.&lt;/p&gt;
&lt;p&gt;The fix preserves raw rendering for literal script and style content while escaping dynamic string children like other JSX expression values.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Affected applications could be vulnerable to reflected or stored cross-site scripting. Exploitation required an application to pass attacker-controlled data directly as a dynamic c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-98hj-9722-w3j8</guid>
    </item>
  </channel>
</rss>
