OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

• CVE-2026-46481: 0.24% estimated exploitation activity in the next 30 days; percentile 15.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 TESTCONNECTION 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. - 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 (for example, GET /api/v1/services/databaseServices/{id}?include=all) with bot-level privileges. This looks different from GHSA-pqqf-7hxm-rj5r, because it affects the automations/workflows TESTCONNECTION endpoint on OpenMetadata 1.12.1, not the ingestion pipelines endpoints. --- Version / Product - Product: OpenMetadata (open source, Apache 2.0) - Version: 1.12.1 - GET…

Published by the source

21 May 2026, 16:36 UTC

Last modified by the source

9 Jun 2026, 13:12 UTC

Source last checked

26 Oct 2026, 16:46 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9vmh-whc4-7phg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46481

Advisory: OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users
IDs: CVE-2026-46481, GHSA-9vmh-whc4-7phg
Record: https://patchnext.com/advisories/cve-2026-46481 (revision 1, source checked 26 Oct 2026, 16:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.open-metadata:openmetadata-service 1.12.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.open-metadata:openmetadata-service: affected < 1.12.4; fixed in 1.12.4

## Suggested inspection (read-only)
- Maven org.open-metadata:openmetadata-service: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.open-metadata:openmetadata-service.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9vmh-whc4-7phg (GitHub-reviewed advisory GHSA-9vmh-whc4-7phg lists affected ranges: Maven org.open-metadata:openmetadata-service >=0 <1.12.4)

Commands are suggestions: review each one before running it.