Vulnerabilities in pkg:maven/org.open-metadata/openmetadata-sdk

PACKAGE
Advisory Identifier: GHSA-pqqf-7hxm-rj5r
Advisory Summary

CVE-2026-26010 is a HIGH (CVSS 7.6) leaky jwts vulnerability (CWE-269: Improper Privilege Management) affecting Openmetadata sdk libraries in the Maven ecosystem. The issue involves leaky jwts in openmetadata exposing highly-privileged bot users. Remediation is available by upgrading affected packages to version 1.11.8.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.open-metadata/openmetadata-sdk

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.open-metadata/openmetadata-sdk. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-pqqf-7hxm-rj5r CVE-2026-26010 HIGH Leaky JWTs in OpenMetadata exposing highly-privileged bot users

CVE-2026-26010 at a Glance

CVE Identifier CVE-2026-26010
GHSA Identifier GHSA-pqqf-7hxm-rj5r
Severity HIGH
CVSS v3.1 Base Score 7.6
CWE Classification CWE-269: Improper Privilege Management
Affected Product Openmetadata sdk
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.6

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:L/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-26010

To remediate this vulnerability, upgrade all affected Openmetadata sdk dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.open-metadata:openmetadata-sdk fixed: 1.11.8
<dependency>
    <groupId>org.open-metadata</groupId>
    <artifactId>openmetadata-sdk</artifactId>
    <version>1.11.8</version>
</dependency>
Verify Direct and Transitive Dependencies

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-26010, 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 sdk in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.11.8), 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-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Openmetadata sdk, 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

### Summary Calls issued by the UI against `/api/v1/ingestionPipelines` leak JWTs used by `ingestion-bot` for certain services (Glue / Redshift / Postgres) ### Details Any read-only user can gain access to a highly privileged account, typically which has the Ingestion Bot Role. This enables destructive changes in OpenMetadata instances, and potential data leakage (e.g. sample data, or service metadata which would be unavailable per roles/policies). ### PoC I was able to extract the JWT used by the bot/agent populating [sample_athena.default](https://sandbox.open-metadata.org/database/sample_athena.default) in the Collate Sandbox. To prove this out, I mutated the description to this UUID: `fe2e4cc1-da72-4acf-8535-112a3cfa9c7e,` which you can see @ https://sandbox.open-metadata.org/database/sample_athena.default. #### Steps to Reproduce * Create a Collate Sandbox account; these are non-admin accounts by default with minimal permissions. * Open the Developer Console * Go to the Services Page. In this case, [sample_athena](https://sandbox.open-metadata.org/service/databaseServices/sample_athena?showDeletedTables=false&currentPage=1), though other services * In the Network tab, introspect the request made to api/v1/services/ingestionPipelines, and find the jwtToken in the response: <img width="1329" height="299" alt="image" src="https://github.com/user-attachments/assets/0c405776-159e-4188-9591-ed8cc71bc596" /> * Use the JWT to issue (potentially destructive) API calls <img width="3024" height="1798" alt="image" src="https://github.com/user-attachments/assets/ab40b528-4d2b-404b-8f8a-482a1693e179" /> * Resulting mutated description: <img width="622" height="399" alt="image" src="https://github.com/user-attachments/assets/3fa630ff-93b5-4b7d-8e3c-220f8a84a23a" /> Note that this is also the case for these services, among others: * [acme_nexus_redshift](https://sandbox.open-metadata.org/service/databaseServices/acme_nexus_redshift) * [sample_postgres](https://sandbox.open-metadata.org/service/databaseServices/sample_postgres) ### Proposed Remediation Redact jwtToken in API payload. Implement role-based filtering - Only return JWT tokens to users with explicit admin/service account permissions (for Admins) Rotate Ingestion Bot Tokens in affected environments ### Impact _What kind of vulnerability is it? Who is impacted?_ * Vulnerability Type: Privilege Escalation * Risk: User impersonation, even for those with read-only access, can lead to destructive outcomes if malicious actors leverage the leaked JWT.

CVE-2026-26010 Affected Openmetadata sdk Versions

1 component(s)
Fixed Versions:
1.11.8
Product / Package Ecosystem Affected Versions Fixed Version
org.open-metadata:openmetadata-sdk
Maven
< 1.11.8
1.11.8

References

Frequently Asked Questions

What is CVE-2026-26010?
CVE-2026-26010 is a security vulnerability in Openmetadata sdk involving Leaky JWTs in OpenMetadata exposing highly-privileged bot users under CWE-269: Improper Privilege Management.
Which Openmetadata sdk versions are affected?
Affected versions include releases prior to 1.11.8 across affected packages: org.open-metadata:openmetadata-sdk.
What version fixes CVE-2026-26010?
Upgrading to 1.11.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openmetadata-sdk affected?
Yes, org.open-metadata:openmetadata-sdk is affected in releases prior to 1.11.8. Upgrade your dependency to 1.11.8 or later.
What is the CVSS score of CVE-2026-26010?
CVE-2026-26010 has a CVSS v3.1 base score of 7.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L.
What CWE is associated with CVE-2026-26010?
CVE-2026-26010 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check Maven dependencies for CVE-2026-26010?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.open-metadata'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pqqf-7hxm-rj5r",
  "modified" : "2026-02-18T23:30:21Z",
  "published" : "2026-02-11T14:23:02Z",
  "aliases" : [ "CVE-2026-26010" ],
  "summary" : "Leaky JWTs in OpenMetadata exposing highly-privileged bot users",
  "details" : "### Summary\nCalls issued by the UI against `/api/v1/ingestionPipelines` leak JWTs used by `ingestion-bot` for certain services (Glue / Redshift / Postgres)\n\n### Details\nAny read-only user can gain access to a highly privileged account, typically which has the Ingestion Bot Role. This enables destructive changes in OpenMetadata instances, and potential data leakage (e.g. sample data, or service metadata which would be unavailable per roles/policies). \n\n\n### PoC\nI was able to extract the JWT used by the bot/agent populating [sample_athena.default](https://sandbox.open-metadata.org/database/sample_athena.default) in the Collate Sandbox. To prove this out, I mutated the description to this UUID: `fe2e4cc1-da72-4acf-8535-112a3cfa9c7e,` which you can see  @ https://sandbox.open-metadata.org/database/sample_athena.default.\n\n#### Steps to Reproduce\n\n* Create a Collate Sandbox account; these are non-admin accounts by default with minimal permissions.\n* Open the Developer Console\n* Go to the Services Page. In this case, [sample_athena](https://sandbox.open-metadata.org/service/databaseServices/sample_athena?showDeletedTables=false&currentPage=1), though other services \n* In the Network tab, introspect the request made to api/v1/services/ingestionPipelines, and find the jwtToken in the response:\n<img width=\"1329\" height=\"299\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0c405776-159e-4188-9591-ed8cc71bc596\" />\n\n* Use the JWT to issue (potentially destructive) API calls\n<img width=\"3024\" height=\"1798\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ab40b528-4d2b-404b-8f8a-482a1693e179\" />\n\n* Resulting mutated description:\n<img width=\"622\" height=\"399\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3fa630ff-93b5-4b7d-8e3c-220f8a84a23a\" />\n\nNote that this is also the case for these services, among others:\n* [acme_nexus_redshift](https://sandbox.open-metadata.org/service/databaseServices/acme_nexus_redshift) \n* [sample_postgres](https://sandbox.open-metadata.org/service/databaseServices/sample_postgres)\n\n### Proposed Remediation\nRedact jwtToken in API payload.\nImplement role-based filtering - Only return JWT tokens to users with explicit admin/service account permissions\n(for Admins) Rotate Ingestion Bot Tokens in affected environments\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n* Vulnerability Type: Privilege Escalation\n* Risk: User impersonation, even for those with read-only access, can lead to destructive outcomes if malicious actors leverage the leaked JWT.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.open-metadata:openmetadata-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.11.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-metadata/OpenMetadata/security/advisories/GHSA-pqqf-7hxm-rj5r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-26010"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-metadata/OpenMetadata"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-metadata/OpenMetadata/releases/tag/1.11.8-release"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-11T14:23:02Z",
    "nvd_published_at" : "2026-02-11T21:16:21Z"
  }
}