Leaky JWTs in OpenMetadata exposing highly-privileged bot users

The primary impact of CVE-2026-26010 is the unauthorized access to highly privileged accounts, typically those associated with the Ingestion Bot Role. An attacker who successfully extracts a JWT can leverage this access to perform destructive changes within the OpenMetadata instance. This includes modifying metadata, deleting critical data, and potentially exfiltrating sensitive information such as sample data or service metadata that would otherwise be restricted by role-based access controls. The potential blast radius extends to any data managed by OpenMetadata, particularly those services integrated via ingestion pipelines like Glue, Redshift, and Postgres. The ease of exploitation, requiring only a read-only user account, significantly increases the risk.

Organizations utilizing OpenMetadata for data governance and metadata management are at risk. Specifically, deployments with read-only user accounts that have access to the /api/v1/ingestionPipelines endpoint are particularly vulnerable. Environments relying on the 'Ingestion Bot' role for automated data ingestion processes are also at heightened risk, as a compromised JWT could disrupt these critical workflows.

• java / server: Monitor OpenMetadata access logs for requests to /api/v1/ingestionPipelines originating from read-only user accounts. Look for unusual patterns or large numbers of requests. • generic web: Use curl to test the /api/v1/ingestionPipelines endpoint with a read-only user's credentials and examine the response headers for JWT tokens.

curl -H "Authorization: Bearer <read_only_jwt>" https://<openmetadata_url>/api/v1/ingestionPipelines

1. 2026-02-11Disclosure

   disclosure

2. 2026-02-11PoC

   poc

3. 2026-02-11Patch

   patch

1. Reserviert2026-02-09
2. Veröffentlicht2026-02-11
3. Geändert2026-02-18
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2026-26010 is to upgrade to OpenMetadata SDK version 1.11.8 or later, which addresses the JWT leakage vulnerability. If an immediate upgrade is not feasible, consider implementing temporary workarounds. Restrict access to the /api/v1/ingestionPipelines endpoint to authorized users only. Implement stricter JWT validation and rotation policies to minimize the impact of a compromised token. Monitor API logs for suspicious activity, specifically focusing on requests originating from unauthorized users. After upgrading, confirm the fix by attempting to access the /api/v1/ingestionPipelines endpoint with a read-only user account and verifying that JWTs are no longer exposed.