Skip to main content
VulnerabilityPublished

CVE-2026-46481: open-metadata OpenMetadata · Insertion of Sensitive Information Into Sent Data

Affects open-metadata OpenMetadataSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 1.12.4 soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.12.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade OpenMetadata and open-metadata/OpenMetadata to 1.12.4.

Affected software

ProductAffectedFixed in
open-metadataOpenMetadataAffected
  • <1.12.4
Fixed in
  • 1.12.4
GitHubopen-metadata/OpenMetadatapkg:github/open-metadata/OpenMetadataOther threatsAffected
  • <1.12.4
Fixed in
  • 1.12.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenMetadata to version 1.12.4 or later, where this vulnerability is patched. No other mitigation is indicated or required according to the available data.

Description

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 <jwt> to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.

References

Community reviews

Loading reviews…