CVE-2026-26010

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 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, though other services
• In the Network tab, introspect the request made to api/v1/services/ingestionPipelines, and find the jwtToken in the response:

• Use the JWT to issue (potentially destructive) API calls

• Resulting mutated description:

Note that this is also the case for these services, among others:

• acme_nexus_redshift
• 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

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.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2026-26010 has a CVSS score of 7.6 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-26010? CVE-2026-26010 is a high-severity improper privilege management vulnerability in org.open-metadata:openmetadata-sdk (maven), affecting versions < 1.11.8. It is fixed in 1.11.8. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2026-26010? CVE-2026-26010 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.open-metadata:openmetadata-sdk are affected by CVE-2026-26010? org.open-metadata:openmetadata-sdk (maven) versions < 1.11.8 is affected.
4. Is there a fix for CVE-2026-26010? Yes. CVE-2026-26010 is fixed in 1.11.8. Upgrade to this version or later.
5. Is CVE-2026-26010 exploitable, and should I be worried? Whether CVE-2026-26010 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-26010 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-26010? Upgrade org.open-metadata:openmetadata-sdk to 1.11.8 or later.