# CVE-2026-26010: Leaky JWTs in OpenMetadata exposing highly-privileged bot users

> Read-only users can steal privileged JWTs from API responses to gain Ingestion Bot role, enabling destructive changes and data leakage.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-pqqf-7hxm-rj5r

## What is CVE-2026-26010?

CVE-2026-26010 is a high-severity vulnerability in open-metadata OpenMetadata, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenMetadata is a unified metadata platform. Prior to 1.11.8, calls issued by the UI against /api/v1/ingestionPipelines leak JWTs used by ingestion-bot for certain services (Glue / Redshift / Postgres). 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). This vulnerability is fixed in 1.11.8.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-26010?

2 open source packages ship an affected version, including org.open-metadata:openmetadata-sdk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.open-metadata:openmetadata-sdk` | Maven | All versions | 1.11.8 |
| `org.open-metadata:openmetadata-sdk` | Maven | All versions | 1.11.8 |

Products: Open-Metadata Openmetadata.

## How do I fix CVE-2026-26010?

Upgrade org.open-metadata:openmetadata-sdk to 1.11.8 or later.

## Is CVE-2026-26010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26010 exists.

## Other vulnerabilities in open-metadata OpenMetadata

- [CVE-2024-28255](https://insights.sbomify.com/CVE-2024-28255/): Authentication Bypass in OpenMetadata (critical 9.8)
- [CVE-2024-28253](https://insights.sbomify.com/CVE-2024-28253/): SpEL Injection in `PUT /api/v1/policies` in OpenMetadata (critical 9.4)
- [CVE-2024-28254](https://insights.sbomify.com/CVE-2024-28254/): SpEL Injection in `GET /api/v1/events/subscriptions/validation/condition/<expr>` in OpenMetadata (high 8.8)
- [CVE-2024-28847](https://insights.sbomify.com/CVE-2024-28847/): SpEL Injection in `PUT /api/v1/events/subscriptions` in OpenMetadata (high 8.8)
- [CVE-2024-28848](https://insights.sbomify.com/CVE-2024-28848/): SpEL Injection in `GET /api/v1/policies/validation/condition/<expr>` in OpenMetadata (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26010 and fix it if it is affected.

What it is: CVE-2026-26010 is a high-severity vulnerability in open-metadata OpenMetadata, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26010 exists.

Affected packages and fixed versions:
- org.open-metadata:openmetadata-sdk (Maven): affected all versions; fixed in 1.11.8
- org.open-metadata:openmetadata-sdk (Maven): affected all versions; fixed in 1.11.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26010/ (Markdown: https://insights.sbomify.com/CVE-2026-26010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26010
- OSV: https://osv.dev/vulnerability/CVE-2026-26010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26010/
Summaries are generated and may contain mistakes; the official description above is the record.