<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 11:33:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-405800</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405800</link>
      <description>EUVD-2026-405800</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405800</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126359</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126359</link>
      <description>&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. From 3.12.0 until 4.13.16, the css helper in hono/css escapes interpolated string values separately and therefore fails to neutralize a closing style tag when &amp;amp;lt; ends the template text or a preceding value and / begins the next attacker-controlled value. During server-side rendering, the combined output can close the &amp;amp;lt;Style /&amp;amp;gt; element early and cause the remainder of the interpolated value to be interpreted as HTML. Applications that place an untrusted string immediately after &amp;amp;lt; in a css template, including adjacent untrusted interpolations, can expose viewers to attacker-controlled HTML or script and information accessible to that page. Other uses of the css helper are not affected. This issue is fixed in version 4.13.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. From 3.12.0 until 4.13.16, the css helper in hono/css escapes interpolated string values separately and therefore fails to neutralize a closing style tag when &amp;amp;lt; ends the template text or a preceding value and / begins the next attacker-controlled value. During server-side rendering, the combined output can close the &amp;amp;lt;Style /&amp;amp;gt; element early and cause the remainder of the interpolated value to be interpreted as HTML. Applications that place an untrusted string immediately after &amp;amp;lt; in a css template, including adjacent untrusted interpolations, can expose viewers to attacker-controlled HTML or script and information accessible to that page. Other uses of the css helper are not affected. This issue is fixed in version 4.13.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-126359</guid>
    </item>
    <item>
      <title>GHSA-3gg2-335m-rxc6 — Hono: `css` helper does not escape a closing tag split between the template and an interpolated value, allowing HTML in…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3gg2-335m-rxc6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `css` helper in `hono/css` escapes a `/` that follows `&amp;lt;` inside an interpolated value so that a value cannot close the `&amp;lt;style&amp;gt;` element. The check only looks inside each value. When the text before a value ends with `&amp;lt;`, whether that is the template itself or an earlier interpolated value, and the next value starts with `/`, the `/` is not escaped and the combined output contains an unescaped closing tag.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Interpolated string values are escaped one at a time before they are joined with the surrounding template text. The rule that neutralizes `&amp;lt;/` therefore cannot see a `&amp;lt;` that belongs to the template. A template such as a `content` declaration that opens with a literal `&amp;lt;` and interpolates a string right after it produces a raw `&amp;lt;/style&amp;gt;` when that string starts with `/style&amp;gt;`. During server-side rendering the `&amp;lt;Style /&amp;gt;` element is closed early and the rest of the value is interpreted as HTML.&lt;/p&gt;
&lt;p&gt;This issue arises only when `&amp;lt;` is the last character before an interpolation in a `css` template, either written in the template or supplied by a preceding value, and the interpolated value is controlled by a client.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A client that controls such a value can inject HTML, including script, into the page rendered on the server.&lt;/p&gt;
&lt;p&gt;This may lead to:&lt;/p&gt;
&lt;p&gt;- Execution of attacker-controlled script in the browser of a user who views the page
- Exposure of information available to that page&lt;/p&gt;
&lt;p&gt;This issue affects applications that interpolate untrusted st…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `css` helper in `hono/css` escapes a `/` that follows `&amp;lt;` inside an interpolated value so that a value cannot close the `&amp;lt;style&amp;gt;` element. The check only looks inside each value. When the text before a value ends with `&amp;lt;`, whether that is the template itself or an earlier interpolated value, and the next value starts with `/`, the `/` is not escaped and the combined output contains an unescaped closing tag.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Interpolated string values are escaped one at a time before they are joined with the surrounding template text. The rule that neutralizes `&amp;lt;/` therefore cannot see a `&amp;lt;` that belongs to the template. A template such as a `content` declaration that opens with a literal `&amp;lt;` and interpolates a string right after it produces a raw `&amp;lt;/style&amp;gt;` when that string starts with `/style&amp;gt;`. During server-side rendering the `&amp;lt;Style /&amp;gt;` element is closed early and the rest of the value is interpreted as HTML.&lt;/p&gt;
&lt;p&gt;This issue arises only when `&amp;lt;` is the last character before an interpolation in a `css` template, either written in the template or supplied by a preceding value, and the interpolated value is controlled by a client.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A client that controls such a value can inject HTML, including script, into the page rendered on the server.&lt;/p&gt;
&lt;p&gt;This may lead to:&lt;/p&gt;
&lt;p&gt;- Execution of attacker-controlled script in the browser of a user who views the page
- Exposure of information available to that page&lt;/p&gt;
&lt;p&gt;This issue affects applications that interpolate untrusted st…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3gg2-335m-rxc6</guid>
    </item>
  </channel>
</rss>
