<?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>Fri, 02 Oct 2026 20:53:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-367996</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367996</link>
      <description>EUVD-2026-367996</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367996</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90450</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-90450</link>
      <description>&lt;p&gt;The application&amp;#39;s role-authorization lookup defaults to granting access when a request handler&amp;#39;s name is not present in its table of role requirements, rather than defaulting to deny. Any request handler that is not explicitly registered in this table is reachable by any authenticated user regardless of their assigned role, and any newly added handler is fail-open by default until explicitly added to the table.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The application&amp;#39;s role-authorization lookup defaults to granting access when a request handler&amp;#39;s name is not present in its table of role requirements, rather than defaulting to deny. Any request handler that is not explicitly registered in this table is reachable by any authenticated user regardless of their assigned role, and any newly added handler is fail-open by default until explicitly added to the table.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-90450</guid>
    </item>
    <item>
      <title>GHSA-47x5-rf97-8ggr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-47x5-rf97-8ggr</link>
      <description>&lt;p&gt;The application&amp;#39;s role-authorization lookup defaults to granting access when a request handler&amp;#39;s name is not present in its table of role requirements, rather than defaulting to deny. Any request handler that is not explicitly registered in this table is reachable by any authenticated user regardless of their assigned role, and any newly added handler is fail-open by default until explicitly added to the table.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The application&amp;#39;s role-authorization lookup defaults to granting access when a request handler&amp;#39;s name is not present in its table of role requirements, rather than defaulting to deny. Any request handler that is not explicitly registered in this table is reachable by any authenticated user regardless of their assigned role, and any newly added handler is fail-open by default until explicitly added to the table.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-47x5-rf97-8ggr</guid>
    </item>
    <item>
      <title>ICSA-26-254-01 — CISA Malcolm</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-254-01</link>
      <description>&lt;p&gt;A web interface reflects a portion of the request URL into a script context and a hyperlink attribute without adequate encoding, and does not require authentication to reach. This allows an unauthenticated network attacker to craft a link that, when visited by a user, executes arbitrary script in the context of the affected application and can redirect the user&amp;#39;s browser to an arbitrary external site. Successful exploitation could allow an attacker to act with the compromised user&amp;#39;s session privileges within the application. A file-transfer interface that requires valid credentials accepts attacker-controlled filenames without restricting shell metacharacters. An automated process later constructs and runs a system command using the uploaded file&amp;#39;s name, allowing an authenticated attacker to embed and execute arbitrary operating system commands with the privileges of that process. This allows an attacker to read and modify ingested log data, and could provide a foothold for further movement within the internal network. An interface that accepts file uploads from authenticated users extracts the contents of uploaded archives without validating that extracted file paths remain within the intended destination directory. This allows an authenticated attacker to craft an archive whose entries traverse outside the destination directory, causing the extraction process to write files to arbitrary locations with the privileges of that process. This could allow an attacker to inject f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A web interface reflects a portion of the request URL into a script context and a hyperlink attribute without adequate encoding, and does not require authentication to reach. This allows an unauthenticated network attacker to craft a link that, when visited by a user, executes arbitrary script in the context of the affected application and can redirect the user&amp;#39;s browser to an arbitrary external site. Successful exploitation could allow an attacker to act with the compromised user&amp;#39;s session privileges within the application. A file-transfer interface that requires valid credentials accepts attacker-controlled filenames without restricting shell metacharacters. An automated process later constructs and runs a system command using the uploaded file&amp;#39;s name, allowing an authenticated attacker to embed and execute arbitrary operating system commands with the privileges of that process. This allows an attacker to read and modify ingested log data, and could provide a foothold for further movement within the internal network. An interface that accepts file uploads from authenticated users extracts the contents of uploaded archives without validating that extracted file paths remain within the intended destination directory. This allows an authenticated attacker to craft an archive whose entries traverse outside the destination directory, causing the extraction process to write files to arbitrary locations with the privileges of that process. This could allow an attacker to inject f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-254-01</guid>
    </item>
  </channel>
</rss>
