CVE-2026-26010: OpenMetadata SDK Leaky JWTs Expose Privileged Bot Users

Summary

11/02/2026
Yes i
High
7.6

CVE-2026-26010: Leaky JWTs in OpenMetadata exposing highly-privileged bot users. Affects org.open-metadata:openmetadata-sdk versions < 1.11.8. Fixed in 1.11.8. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenMetadata SDK is a Java-based library designed to facilitate the integration and management of metadata across various data sources. It provides functionalities for data ingestion, lineage tracking, and metadata management. However, a critical vulnerability has been identified that allows unauthorized access to sensitive JWT tokens used by the ingestion bot, potentially leading to privilege escalation and data manipulation.

Vulnerability Detail

The vulnerability arises from API calls made by the OpenMetadata UI to the ingestion pipelines endpoint, which inadvertently leak JWT tokens associated with the ingestion bot. This allows any read-only user to access a highly privileged account, typically possessing the Ingestion Bot Role. The consequences of this vulnerability include the potential for destructive changes to OpenMetadata instances and data leakage of sensitive information that should be restricted based on user roles and policies.

How To Fix

Latest published version: 2.0.6 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.11.8

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can implement role-based filtering to ensure that JWT tokens are only returned to users with explicit admin or service account permissions. Additionally, consider rotating the Ingestion Bot Tokens in affected environments to mitigate immediate risks.

Conclusion

In summary, CVE-2026-26010 represents a significant vulnerability within the OpenMetadata SDK that can lead to privilege escalation through the leakage of sensitive JWT tokens. Users are advised to update to the latest version to mitigate risks and implement role-based access controls as a temporary measure.

See every vulnerability recorded for org.open-metadata:openmetadata-sdk →

Share this vulnerability

FAQ

The vulnerability allows unauthorized users to access privileged JWT tokens, leading to potential privilege escalation and destructive actions within OpenMetadata.

Any user with read-only access to the OpenMetadata UI can exploit this vulnerability, potentially affecting all OpenMetadata instances.

Consequences include unauthorized data manipulation, data leakage, and the ability to perform destructive actions on the OpenMetadata instance.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score for this vulnerability is 7.6, indicating a high severity level.

How To Fix

Latest published version: 2.0.6 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.11.8

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback