<?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, 06 Oct 2026 18:44:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-247800</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-247800</link>
      <description>EUVD-2026-247800</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-247800</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54066</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54066</link>
      <description>&lt;p&gt;DiracX-Web is a web application that provides an interface to interact with the DiracX services. Prior to version 0.1.0-a8, an attacker can forge a request that they can pass to redirect an authenticated user to another arbitrary website. In the login page, DiracX-Web has a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI. Paired with a parameter pollution, an attacker can hide their malicious URI. This could be used for phishing, and extract new data (such as redirecting to a new &amp;#34;log in&amp;#34; page, and asking another time credentials). Version 0.1.0-a8 fixes this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;DiracX-Web is a web application that provides an interface to interact with the DiracX services. Prior to version 0.1.0-a8, an attacker can forge a request that they can pass to redirect an authenticated user to another arbitrary website. In the login page, DiracX-Web has a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI. Paired with a parameter pollution, an attacker can hide their malicious URI. This could be used for phishing, and extract new data (such as redirecting to a new &amp;#34;log in&amp;#34; page, and asking another time credentials). Version 0.1.0-a8 fixes this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54066</guid>
    </item>
    <item>
      <title>GHSA-hfj7-542q-8fvv — DiracX-Web is vulnerable to attack through an Open Redirect on its login page</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hfj7-542q-8fvv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @dirac-grid/diracx-web-components&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An attacker can forge a request to redirect an authenticated user to any arbitrary website.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;On the login page, we have a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI.&lt;/p&gt;
&lt;p&gt;Paired with a parameter pollution, we can hide our malicious URI (ex: `https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb`).&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;https://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern.ch/auth&lt;/p&gt;
&lt;p&gt;This POC can leak user&amp;#39;s position.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This could be used for phishing and extracting new data (such as redirecting to a new &amp;#34;log in&amp;#34; page, and asking users to reenter credentials).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @dirac-grid/diracx-web-components&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An attacker can forge a request to redirect an authenticated user to any arbitrary website.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;On the login page, we have a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI.&lt;/p&gt;
&lt;p&gt;Paired with a parameter pollution, we can hide our malicious URI (ex: `https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb`).&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;https://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern.ch/auth&lt;/p&gt;
&lt;p&gt;This POC can leak user&amp;#39;s position.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This could be used for phishing and extracting new data (such as redirecting to a new &amp;#34;log in&amp;#34; page, and asking users to reenter credentials).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hfj7-542q-8fvv</guid>
    </item>
  </channel>
</rss>
