<?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>Tue, 06 Oct 2026 02:28:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46481 — OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-46481</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-metadata OpenMetadata&lt;/p&gt;
&lt;p&gt;OpenMetadata is a unified metadata platform. Prior to version 1.12.4, a non-admin SSO user can trigger a TEST_CONNECTION workflow for a Database Service and receive, in the HTTP 201 response of POST /api/v1/automations/workflows, both the cleartext database password in request.connection.config.password and the ingestion bot JWT in openMetadataServerConnection.securityConfig.jwtToken. The leaked ingestion-bot token can then be reused as Authorization: Bearer &amp;lt;jwt&amp;gt; to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-metadata OpenMetadata&lt;/p&gt;
&lt;p&gt;OpenMetadata is a unified metadata platform. Prior to version 1.12.4, a non-admin SSO user can trigger a TEST_CONNECTION workflow for a Database Service and receive, in the HTTP 201 response of POST /api/v1/automations/workflows, both the cleartext database password in request.connection.config.password and the ingestion bot JWT in openMetadataServerConnection.securityConfig.jwtToken. The leaked ingestion-bot token can then be reused as Authorization: Bearer &amp;lt;jwt&amp;gt; to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-46481</guid>
    </item>
  </channel>
</rss>
