<?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-06T21:49:03.909019+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-325633</id>
    <title>EUVD-2026-325633</title>
    <updated>2026-10-06T21:49:03.968928+00:00</updated>
    <content>EUVD-2026-325633</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-325633"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46481</id>
    <title>fkie_cve-2026-46481</title>
    <updated>2026-10-06T21:49:03.968965+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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 &lt;jwt&gt; to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-46481"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9vmh-whc4-7phg</id>
    <title>GHSA-9vmh-whc4-7phg — OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users</title>
    <updated>2026-10-06T21:49:03.969001+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.open-metadata:openmetadata-service</p>
<p>**This is not applicable if an application is configuring the Secrets Store to store credentials. Please make sure to follow the best practices when deploying in production**
In OpenMetadata 1.12.1, 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:</p>
<p>- The cleartext database password in `request.connection.config.password`.
- The ingestion bot JWT in `openMetadataServerConnection.securityConfig.jwtToken`.</p>
<p>The leaked ingestion-bot token can then be reused as `Authorization: Bearer &lt;jwt&gt;` to access sensitive service APIs (for example, `GET /api/v1/services/databaseServices/{id}?include=all`) with bot-level privileges.</p>
<p>This looks different from GHSA-pqqf-7hxm-rj5r, because it affects the `automations/workflows` TEST_CONNECTION endpoint on OpenMetadata 1.12.1, not the ingestion pipelines endpoints.</p>
<p>---</p>
<p>Version / Product</p>
<p>- Product: OpenMetadata (open source, Apache 2.0)
- Version: 1.12.1
  - GET /api/v1/system/version →
    {"version":"1.12.1","revision":"618a2dc2ec8f70ffcd0378ee14ce92cb4f98f0c5"}
- Deployment: OpenMetadata server with SSO via Azure AD (OAuth), Oracle database service, secrets in DB secrets manager (`secretsManagerProvider: "db"`).</p>
<p>---</p>
<p>Preconditions</p>
<p>- Authenticated SSO user with access to the UI.
- User can open a Database Service and click “Test connection”.
- No server admin role, no shell/DB access.</p>
<p>---</p>
<p>PoC (short)</p>
<p>1) Login as a reg…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9vmh-whc4-7phg"/>
  </entry>
</feed>
