<?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>Wed, 30 Sep 2026 21:51:40 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-41591</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-41591</link>
      <description>&lt;p&gt;Marko is a declarative, HTML-based language for building web apps. Prior to marko version 5.38.36 and prior to @marko/runtime-tags 6.0.164, when dynamic text is interpolated into a &amp;lt;script&amp;gt; or &amp;lt;style&amp;gt; tag the Marko runtime failed to prevent tag breakout when the closing tag used non-lowercase casing. An attacker able to place input inside a &amp;lt;script&amp;gt; or &amp;lt;style&amp;gt; block could break out of the tag with &amp;lt;/SCRIPT&amp;gt;, &amp;lt;/Style&amp;gt;, etc. and inject arbitrary HTML/JavaScript, resulting in cross-site scripting. This issue has been patched in marko version 5.38.36 and @marko/runtime-tags 6.0.164.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Marko is a declarative, HTML-based language for building web apps. Prior to marko version 5.38.36 and prior to @marko/runtime-tags 6.0.164, when dynamic text is interpolated into a &amp;lt;script&amp;gt; or &amp;lt;style&amp;gt; tag the Marko runtime failed to prevent tag breakout when the closing tag used non-lowercase casing. An attacker able to place input inside a &amp;lt;script&amp;gt; or &amp;lt;style&amp;gt; block could break out of the tag with &amp;lt;/SCRIPT&amp;gt;, &amp;lt;/Style&amp;gt;, etc. and inject arbitrary HTML/JavaScript, resulting in cross-site scripting. This issue has been patched in marko version 5.38.36 and @marko/runtime-tags 6.0.164.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-41591</guid>
    </item>
    <item>
      <title>GHSA-x9fj-57fh-c8wq — Marko: XSS via case-insensitive script/style closing tag bypass in runtime HTML escaping</title>
      <link>https://db.gcve.eu/vuln/ghsa-x9fj-57fh-c8wq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: marko, npm: @marko/runtime-tags&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When dynamic text is interpolated into a `&amp;lt;script&amp;gt;` or `&amp;lt;style&amp;gt;` tag the Marko runtime failed to prevent tag breakout when the closing tag used non-lowercase casing.
An attacker able to place input inside a `&amp;lt;script&amp;gt;` or `&amp;lt;style&amp;gt;` block could break out of the tag with `&amp;lt;/SCRIPT&amp;gt;`, `&amp;lt;/Style&amp;gt;`, etc. and inject arbitrary HTML/JavaScript, resulting in cross-site scripting.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The affected helpers used case-sensitive regular expressions to detect attempts at closing the surrounding tag:&lt;/p&gt;
&lt;p&gt;```js
// packages/runtime-tags/src/html/content.ts
const unsafeScriptReg = /&amp;lt;\/script/g;
const unsafeStyleReg  = /&amp;lt;\/style/g;&lt;/p&gt;
&lt;p&gt;// packages/runtime-class/src/runtime/html/helpers/escape-script-placeholder.js
const unsafeCharsReg = /&amp;lt;\/script/g;&lt;/p&gt;
&lt;p&gt;// packages/runtime-class/src/runtime/html/helpers/escape-style-placeholder.js
const unsafeCharsReg = /&amp;lt;\/style/g;
```&lt;/p&gt;
&lt;p&gt;HTML tag names are case-insensitive in the browser parser, so inputs such as `&amp;lt;/SCRIPT&amp;gt;`, `&amp;lt;/Script&amp;gt;`, or `&amp;lt;/sTyLe&amp;gt;` were not matched by these regexes and passed through the helpers unchanged. A browser rendering the output treats the mixed-case end tag as a valid closing tag, terminating the script or style context, and then parses anything that follows as HTML.&lt;/p&gt;
&lt;p&gt;The Marko compiler routes interpolated values inside `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` tags through these helpers automatically (see `native-tag.ts:1080-1085`), so application code following the framework&amp;#39;s conventions had no way to detect or compensate for the ga…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: marko, npm: @marko/runtime-tags&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When dynamic text is interpolated into a `&amp;lt;script&amp;gt;` or `&amp;lt;style&amp;gt;` tag the Marko runtime failed to prevent tag breakout when the closing tag used non-lowercase casing.
An attacker able to place input inside a `&amp;lt;script&amp;gt;` or `&amp;lt;style&amp;gt;` block could break out of the tag with `&amp;lt;/SCRIPT&amp;gt;`, `&amp;lt;/Style&amp;gt;`, etc. and inject arbitrary HTML/JavaScript, resulting in cross-site scripting.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The affected helpers used case-sensitive regular expressions to detect attempts at closing the surrounding tag:&lt;/p&gt;
&lt;p&gt;```js
// packages/runtime-tags/src/html/content.ts
const unsafeScriptReg = /&amp;lt;\/script/g;
const unsafeStyleReg  = /&amp;lt;\/style/g;&lt;/p&gt;
&lt;p&gt;// packages/runtime-class/src/runtime/html/helpers/escape-script-placeholder.js
const unsafeCharsReg = /&amp;lt;\/script/g;&lt;/p&gt;
&lt;p&gt;// packages/runtime-class/src/runtime/html/helpers/escape-style-placeholder.js
const unsafeCharsReg = /&amp;lt;\/style/g;
```&lt;/p&gt;
&lt;p&gt;HTML tag names are case-insensitive in the browser parser, so inputs such as `&amp;lt;/SCRIPT&amp;gt;`, `&amp;lt;/Script&amp;gt;`, or `&amp;lt;/sTyLe&amp;gt;` were not matched by these regexes and passed through the helpers unchanged. A browser rendering the output treats the mixed-case end tag as a valid closing tag, terminating the script or style context, and then parses anything that follows as HTML.&lt;/p&gt;
&lt;p&gt;The Marko compiler routes interpolated values inside `&amp;lt;script&amp;gt;` and `&amp;lt;style&amp;gt;` tags through these helpers automatically (see `native-tag.ts:1080-1085`), so application code following the framework&amp;#39;s conventions had no way to detect or compensate for the ga…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x9fj-57fh-c8wq</guid>
    </item>
  </channel>
</rss>
