<?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>Sun, 04 Oct 2026 18:05:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-1584 — Quarkus-oidc: id and access tokens leak via the authorization code flow</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-1584</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; quarkus-oidc, Red Hat build of Quarkus 2.13.8.Final, Red Hat RHINT Service Registry 2.5.4 GA&lt;/p&gt;
&lt;p&gt;A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; quarkus-oidc, Red Hat build of Quarkus 2.13.8.Final, Red Hat RHINT Service Registry 2.5.4 GA&lt;/p&gt;
&lt;p&gt;A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-1584</guid>
    </item>
  </channel>
</rss>
