<?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, 16 Oct 2026 03:06:02 +0000</lastBuildDate>
    <item>
      <title>BIT-authentik-2024-42490 — authentik has Insufficient Authorization for several API endpoints</title>
      <link>https://cve.radiocsirt.org/vuln/bit-authentik-2024-42490</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: authentik&lt;/p&gt;
&lt;p&gt;authentik is an open-source Identity Provider. Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this are /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/, /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/, and /api/v3/.../used_by/. Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable. authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: authentik&lt;/p&gt;
&lt;p&gt;authentik is an open-source Identity Provider. Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this are /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/, /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/, and /api/v3/.../used_by/. Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable. authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-authentik-2024-42490</guid>
    </item>
    <item>
      <title>EUVD-2026-159547</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-159547</link>
      <description>EUVD-2026-159547</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-159547</guid>
    </item>
    <item>
      <title>fkie_cve-2024-42490</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-42490</link>
      <description>&lt;p&gt;authentik is an open-source Identity Provider. Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this are /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/, /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/, and /api/v3/.../used_by/. Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable. authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;authentik is an open-source Identity Provider. Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this are /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/, /api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/, and /api/v3/.../used_by/. Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable. authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-42490</guid>
    </item>
    <item>
      <title>GHSA-qxqc-27pr-wgc8 — GoAuthentik vulnerable to Insufficient Authorization for several API endpoints</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qxqc-27pr-wgc8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: goauthentik.io&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Several API endpoints can be accessed by users without correct authentication/authorization.&lt;/p&gt;
&lt;p&gt;The main API endpoints affected by this:&lt;/p&gt;
&lt;p&gt;-   `/api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/`
-   `/api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/`
-   `/api/v3/.../used_by/`&lt;/p&gt;
&lt;p&gt;Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Access to the API endpoints can be blocked at a Reverse-proxy/Load balancer level to prevent this issue from being exploited.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;-   Email us at [security@goauthentik.io](mailto:security@goauthentik.io)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: goauthentik.io&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Several API endpoints can be accessed by users without correct authentication/authorization.&lt;/p&gt;
&lt;p&gt;The main API endpoints affected by this:&lt;/p&gt;
&lt;p&gt;-   `/api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_certificate/`
-   `/api/v3/crypto/certificatekeypairs/&amp;lt;uuid&amp;gt;/view_private_key/`
-   `/api/v3/.../used_by/`&lt;/p&gt;
&lt;p&gt;Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Access to the API endpoints can be blocked at a Reverse-proxy/Load balancer level to prevent this issue from being exploited.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;-   Email us at [security@goauthentik.io](mailto:security@goauthentik.io)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qxqc-27pr-wgc8</guid>
    </item>
  </channel>
</rss>
