<?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>Mon, 05 Oct 2026 22:28:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-232604</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232604</link>
      <description>EUVD-2026-232604</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232604</guid>
    </item>
    <item>
      <title>fkie_cve-2022-39222</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39222</link>
      <description>&lt;p&gt;Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability if they are running a version prior to 2.35.0. An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token. Version 2.35.0 has introduced a fix for this issue. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability if they are running a version prior to 2.35.0. An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token. Version 2.35.0 has introduced a fix for this issue. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-39222</guid>
    </item>
    <item>
      <title>GHSA-vh7g-p26c-j2cw — Dex vulnerable to Man-in-the-Middle allowing ID token capture via intercepted authorization code</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vh7g-p26c-j2cw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dexidp/dex&lt;/p&gt;
&lt;p&gt;### Impact
Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce&lt;/p&gt;
&lt;p&gt;1) A victim navigates to a malicious website&lt;/p&gt;
&lt;p&gt;2) The webserver initiates a connection with a Dex instance directly - https://dexexample.com/auth/https:%252F%252Faccounts.google.com?access_type=online&amp;amp;client_id=example&amp;amp;nonce=2AaJAimQU9CbeOFsNra1d7CJTWB&amp;amp;redirect_uri=http%3A%2F%2Flocalhost%3A40393%2Fauth%2Fcallback&amp;amp;response_type=code&amp;amp;scope=openid+email&amp;amp;state=2AaJAjhpUmsB25csCo5muvorMTl. In this example, the Dex instance is hosted on `dexexample.com`, and the connector is `accounts.google.com`.&lt;/p&gt;
&lt;p&gt;3) Dex returns a 302 Redirect to the connector IDP, https://accounts.google.com/o/oauth2/v2/auth?client_id=237800849078-hri2ndt7gdafpf34kq8crd5sik9pe3so.apps.googleusercontent.com&amp;amp;redirect_uri=https%3A%2F%2Fdexexample.com%2Fauth%2Fcallback&amp;amp;response_type=code&amp;amp;scope=openid+email&amp;amp;state=g3dkmpontsr3ugocoddjx72ef. The attacker records the state parameter value g3dkmpontsr3ugocoddjx72ef which will be used as the request ID later on.&lt;/p&gt;
&lt;p&gt;4) The malicious website redirects the victim’s browser to the connector…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dexidp/dex&lt;/p&gt;
&lt;p&gt;### Impact
Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce&lt;/p&gt;
&lt;p&gt;1) A victim navigates to a malicious website&lt;/p&gt;
&lt;p&gt;2) The webserver initiates a connection with a Dex instance directly - https://dexexample.com/auth/https:%252F%252Faccounts.google.com?access_type=online&amp;amp;client_id=example&amp;amp;nonce=2AaJAimQU9CbeOFsNra1d7CJTWB&amp;amp;redirect_uri=http%3A%2F%2Flocalhost%3A40393%2Fauth%2Fcallback&amp;amp;response_type=code&amp;amp;scope=openid+email&amp;amp;state=2AaJAjhpUmsB25csCo5muvorMTl. In this example, the Dex instance is hosted on `dexexample.com`, and the connector is `accounts.google.com`.&lt;/p&gt;
&lt;p&gt;3) Dex returns a 302 Redirect to the connector IDP, https://accounts.google.com/o/oauth2/v2/auth?client_id=237800849078-hri2ndt7gdafpf34kq8crd5sik9pe3so.apps.googleusercontent.com&amp;amp;redirect_uri=https%3A%2F%2Fdexexample.com%2Fauth%2Fcallback&amp;amp;response_type=code&amp;amp;scope=openid+email&amp;amp;state=g3dkmpontsr3ugocoddjx72ef. The attacker records the state parameter value g3dkmpontsr3ugocoddjx72ef which will be used as the request ID later on.&lt;/p&gt;
&lt;p&gt;4) The malicious website redirects the victim’s browser to the connector…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vh7g-p26c-j2cw</guid>
    </item>
    <item>
      <title>gsd-2022-39222</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-39222</link>
      <description>gsd-2022-39222</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-39222</guid>
    </item>
    <item>
      <title>RHSA-2023:7725 — Red Hat Security Advisory: RHACS 4.3 enhancement and security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:7725</link>
      <description>&lt;p&gt;dexidp: gaining access to applications accepting that token&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;dexidp: gaining access to applications accepting that token&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:7725</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-3113 — Red Hat Advanced Cluster Security: Schwachstelle ermöglicht Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-3113</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Advanced Cluster Security ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Advanced Cluster Security ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-3113</guid>
    </item>
  </channel>
</rss>
