# CVE-2026-46481: OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users

> Non-admin users can leak cleartext database passwords and ingestion-bot JWTs via the TEST_CONNECTION workflow, enabling unauthorized access to sensitive APIs.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-9vmh-whc4-7phg

## What is CVE-2026-46481?

CVE-2026-46481 is a high-severity vulnerability in open-metadata OpenMetadata, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-46481?

2 open source packages ship an affected version, including org.open-metadata:openmetadata-service.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.open-metadata:openmetadata-service` | Maven | All versions | 1.12.4 |
| `org.open-metadata:openmetadata-service` | Maven | All versions | 1.12.4 |

## How do I fix CVE-2026-46481?

Upgrade org.open-metadata:openmetadata-service to 1.12.4 or later.

## Is CVE-2026-46481 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46481 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46481 and fix it if it is affected.

What it is: CVE-2026-46481 is a high-severity vulnerability in open-metadata OpenMetadata, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46481 exists.

Affected packages and fixed versions:
- org.open-metadata:openmetadata-service (Maven): affected all versions; fixed in 1.12.4
- org.open-metadata:openmetadata-service (Maven): affected all versions; fixed in 1.12.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46481/ (Markdown: https://insights.sbomify.com/CVE-2026-46481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46481
- OSV: https://osv.dev/vulnerability/CVE-2026-46481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46481/
Summaries are generated and may contain mistakes; the official description above is the record.