<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T21:27:46.967849+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-221688</id>
    <title>EUVD-2026-221688</title>
    <updated>2026-10-07T21:27:46.972657+00:00</updated>
    <content>EUVD-2026-221688</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-221688"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-22492</id>
    <title>fkie_cve-2023-22492</title>
    <updated>2026-10-07T21:27:46.972692+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ZITADEL is a combination of Auth0 and Keycloak. RefreshTokens is an OAuth 2.0 feature that allows applications to retrieve new access tokens and refresh the user's session without the need for interacting with a UI. RefreshTokens were not invalidated when a user was locked or deactivated. The deactivated or locked user was able to obtain a valid access token only through a refresh token grant. When the locked or deactivated user’s session was already terminated (“logged out”) then it was not possible to create a new session. Renewal of access token through a refresh token grant is limited to the configured amount of time (RefreshTokenExpiration). As a workaround, ensure the RefreshTokenExpiration in the OIDC settings of your instance is set according to your security requirements. This issue has been patched in versions 2.17.3 and 2.16.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-22492"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6rrr-78xp-5jp8</id>
    <title>GHSA-6rrr-78xp-5jp8 — Zitadel RefreshToken invalidation vulnerability</title>
    <updated>2026-10-07T21:27:46.972734+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/zitadel/zitadel</p>
<p>### Impact
RefreshTokens is an OAuth 2.0 feature that allows applications to retrieve new access tokens and refresh the user's session without the need for interacting with a UI.</p>
<p>RefreshTokens were not invalidated when a user was locked or deactivated. The deactivated or locked user was able to obtain a valid access token only through a refresh token grant.</p>
<p>When the locked or deactivated user’s session was already terminated (“logged out”) then it was not possible to create a new session. Renewal of access token through a refresh token grant is limited to the configured amount of time (RefreshTokenExpiration).</p>
<p>### Patches
2.x versions are fixed on &gt;= [2.17.3](https://github.com/zitadel/zitadel/releases/tag/v2.17.3)
2.16.x versions are fixed on &gt;= [2.16.4](https://github.com/zitadel/zitadel/releases/tag/v2.16.4)</p>
<p>ZITADEL recommends upgrading to the latest versions available in due course.</p>
<p>### Workarounds
Ensure the RefreshTokenExpiration in the OIDC settings of your instance is set according to your security requirements.</p>
<p>### References</p>
<p>https://zitadel.com/docs/guides/manage/console/instance-settings#oidc-token-lifetimes-and-expiration</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6rrr-78xp-5jp8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-22492</id>
    <title>gsd-2023-22492</title>
    <updated>2026-10-07T21:27:46.972777+00:00</updated>
    <content>gsd-2023-22492</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-22492"/>
  </entry>
</feed>
