<?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>Sat, 03 Oct 2026 22:46:15 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: CLEANSTART-2026-BE61221 — Security fixes for CVE-2025-62718, CVE-2025-69873, CVE-2026-29045, CVE-2026-29085, CVE-2026-29086, CVE-2026-29087, CVE-…</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: opensearch-dashboards-fips&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: opensearch-dashboards-fips&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221</guid>
    </item>
    <item>
      <title>EUVD-2026-318500</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318500</link>
      <description>EUVD-2026-318500</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318500</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44455</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44455</link>
      <description>&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.16, Improper handling of JSX element tag names in hono/jsx allowed unvalidated tag names to be directly inserted into the generated HTML output. When untrusted input is used as a tag name via the programmatic jsx() or createElement() APIs during server-side rendering, specially crafted values may break out of the intended element context and inject unintended HTML. This vulnerability is fixed in 4.12.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.16, Improper handling of JSX element tag names in hono/jsx allowed unvalidated tag names to be directly inserted into the generated HTML output. When untrusted input is used as a tag name via the programmatic jsx() or createElement() APIs during server-side rendering, specially crafted values may break out of the intended element context and inject unintended HTML. This vulnerability is fixed in 4.12.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44455</guid>
    </item>
    <item>
      <title>GHSA-69xw-7hcm-h432 — hono/jsx has Unvalidated JSX Tag Names that May Allow HTML Injection</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-69xw-7hcm-h432</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;Improper handling of JSX element tag names in hono/jsx allowed unvalidated tag names to be directly inserted into the generated HTML output.&lt;/p&gt;
&lt;p&gt;When untrusted input is used as a tag name via the programmatic `jsx()` or `createElement()` APIs during server-side rendering, specially crafted values may break out of the intended element context and inject unintended HTML.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;When rendering JSX elements to HTML strings, attribute values are escaped and attribute names are validated. However, element tag names were previously inserted into the output without validation.&lt;/p&gt;
&lt;p&gt;If a tag name contains characters such as `&amp;lt;`, `&amp;gt;`, quotes, or whitespace, it may alter the structure of the generated HTML.&lt;/p&gt;
&lt;p&gt;For example, malformed tag names can:&lt;/p&gt;
&lt;p&gt;* Break out of the intended element and introduce unintended HTML elements
* Inject attributes or event handlers into the rendered output&lt;/p&gt;
&lt;p&gt;This issue arises when untrusted input (such as query parameters or database content) is used as JSX tag names via `jsx()` or `createElement()` during server-side rendering.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control tag names used in JSX rendering may inject unintended HTML into the generated output.&lt;/p&gt;
&lt;p&gt;This may lead to:&lt;/p&gt;
&lt;p&gt;* Injection of unexpected HTML elements or attributes
* Corruption of the HTML structure
* Cross-site scripting (XSS) when combined with unsafe usage patterns&lt;/p&gt;
&lt;p&gt;This issue only affects applications that construct JSX tag names from untrusted input. Applications using static or allowl…&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;Improper handling of JSX element tag names in hono/jsx allowed unvalidated tag names to be directly inserted into the generated HTML output.&lt;/p&gt;
&lt;p&gt;When untrusted input is used as a tag name via the programmatic `jsx()` or `createElement()` APIs during server-side rendering, specially crafted values may break out of the intended element context and inject unintended HTML.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;When rendering JSX elements to HTML strings, attribute values are escaped and attribute names are validated. However, element tag names were previously inserted into the output without validation.&lt;/p&gt;
&lt;p&gt;If a tag name contains characters such as `&amp;lt;`, `&amp;gt;`, quotes, or whitespace, it may alter the structure of the generated HTML.&lt;/p&gt;
&lt;p&gt;For example, malformed tag names can:&lt;/p&gt;
&lt;p&gt;* Break out of the intended element and introduce unintended HTML elements
* Inject attributes or event handlers into the rendered output&lt;/p&gt;
&lt;p&gt;This issue arises when untrusted input (such as query parameters or database content) is used as JSX tag names via `jsx()` or `createElement()` during server-side rendering.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control tag names used in JSX rendering may inject unintended HTML into the generated output.&lt;/p&gt;
&lt;p&gt;This may lead to:&lt;/p&gt;
&lt;p&gt;* Injection of unexpected HTML elements or attributes
* Corruption of the HTML structure
* Cross-site scripting (XSS) when combined with unsafe usage patterns&lt;/p&gt;
&lt;p&gt;This issue only affects applications that construct JSX tag names from untrusted input. Applications using static or allowl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-69xw-7hcm-h432</guid>
    </item>
  </channel>
</rss>
