<?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>Wed, 07 Oct 2026 02:10:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-275880</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275880</link>
      <description>EUVD-2026-275880</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275880</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27478</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27478</link>
      <description>&lt;p&gt;Unity Catalog is an open, multi-modal Catalog for data and AI. In 0.4.0 and earlier, a critical authentication bypass vulnerability exists in the Unity Catalog token exchange endpoint (/api/1.0/unity-control/auth/tokens). The endpoint extracts the issuer (iss) claim from incoming JWTs and uses it to dynamically fetch the JWKS endpoint for signature validation without validating that the issuer is a trusted identity provider.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Unity Catalog is an open, multi-modal Catalog for data and AI. In 0.4.0 and earlier, a critical authentication bypass vulnerability exists in the Unity Catalog token exchange endpoint (/api/1.0/unity-control/auth/tokens). The endpoint extracts the issuer (iss) claim from incoming JWTs and uses it to dynamically fetch the JWKS endpoint for signature validation without validating that the issuer is a trusted identity provider.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27478</guid>
    </item>
    <item>
      <title>GHSA-qqcj-rghw-829x — Unity Catalog has a JWT Issuer Validation Bypass tht Allows Complete User Impersonation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qqcj-rghw-829x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.unitycatalog:unitycatalog-server&lt;/p&gt;
&lt;p&gt;**Context:**
A critical authentication bypass vulnerability exists in the Unity Catalog token exchange endpoint (/api/1.0/unity-control/auth/tokens). The endpoint extracts the issuer (iss) claim from incoming JWTs and uses it to dynamically fetch the JWKS endpoint for signature validation without validating that the issuer is a trusted identity provider.&lt;/p&gt;
&lt;p&gt;**Way to exploit:**&lt;/p&gt;
&lt;p&gt;An attacker can exploit this by:
1. Hosting their own OIDC-compliant server with a valid JWKS endpoint
2. Signing a JWT with their own private key, setting the iss claim to their server
3. Setting the sub/email claim to any known user in the Unity Catalog system
4. Exchanging this crafted token for a valid internal access token&lt;/p&gt;
&lt;p&gt;This results in complete impersonation of any user in the system, granting access to all catalogs, schemas, tables, and other resources that user has permissions to.&lt;/p&gt;
&lt;p&gt;Additionally, the implementation does not validate the audience (aud) claim, allowing tokens intended for other services to be used.&lt;/p&gt;
&lt;p&gt;**Example**&lt;/p&gt;
&lt;p&gt;Example implementation doing token exchange with a self hosted `.well-known/openid-configuration` and `jwks` endpoint.&lt;/p&gt;
&lt;p&gt;This can be run with `python3 main.py` and `TARGET_USER`, `UC_SERVER` and `PORT` adjusted to the testing setup.&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
&amp;#34;&amp;#34;&amp;#34;Unity Catalog JWT Issuer Validation Bypass PoC - Minimal Version&amp;#34;&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;import base64, secrets, threading, time
from datetime import datetime, timedelta, timezone
import jwt, requests
from cryptography.hazmat.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.unitycatalog:unitycatalog-server&lt;/p&gt;
&lt;p&gt;**Context:**
A critical authentication bypass vulnerability exists in the Unity Catalog token exchange endpoint (/api/1.0/unity-control/auth/tokens). The endpoint extracts the issuer (iss) claim from incoming JWTs and uses it to dynamically fetch the JWKS endpoint for signature validation without validating that the issuer is a trusted identity provider.&lt;/p&gt;
&lt;p&gt;**Way to exploit:**&lt;/p&gt;
&lt;p&gt;An attacker can exploit this by:
1. Hosting their own OIDC-compliant server with a valid JWKS endpoint
2. Signing a JWT with their own private key, setting the iss claim to their server
3. Setting the sub/email claim to any known user in the Unity Catalog system
4. Exchanging this crafted token for a valid internal access token&lt;/p&gt;
&lt;p&gt;This results in complete impersonation of any user in the system, granting access to all catalogs, schemas, tables, and other resources that user has permissions to.&lt;/p&gt;
&lt;p&gt;Additionally, the implementation does not validate the audience (aud) claim, allowing tokens intended for other services to be used.&lt;/p&gt;
&lt;p&gt;**Example**&lt;/p&gt;
&lt;p&gt;Example implementation doing token exchange with a self hosted `.well-known/openid-configuration` and `jwks` endpoint.&lt;/p&gt;
&lt;p&gt;This can be run with `python3 main.py` and `TARGET_USER`, `UC_SERVER` and `PORT` adjusted to the testing setup.&lt;/p&gt;
&lt;p&gt;```python
#!/usr/bin/env python3
&amp;#34;&amp;#34;&amp;#34;Unity Catalog JWT Issuer Validation Bypass PoC - Minimal Version&amp;#34;&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;import base64, secrets, threading, time
from datetime import datetime, timedelta, timezone
import jwt, requests
from cryptography.hazmat.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qqcj-rghw-829x</guid>
    </item>
  </channel>
</rss>
