JWTs divulgués dans OpenMetadata exposant des utilisateurs de bot très privilégiés

The primary impact of CVE-2026-26010 is the exposure of JWT tokens used by the OpenMetadata ingestion bot. These tokens typically grant elevated privileges, often associated with roles like 'Ingestion Bot'. An attacker who successfully extracts a JWT can leverage it to perform destructive actions within the OpenMetadata instance, including modifying metadata, deleting pipelines, and potentially exfiltrating sensitive data. The description specifically mentions sample data and service metadata as potential targets. This vulnerability is particularly concerning as it allows a read-only user to gain significant control, bypassing standard access controls and potentially leading to a complete compromise of the OpenMetadata environment. The ability to extract these tokens from the /api/v1/ingestionPipelines endpoint highlights a design flaw in how the API handles authentication and authorization.

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. Réservé2026-02-09
2. Publiée2026-02-11
3. Modifiée2026-02-18
4. EPSS mis à jour2026-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. Restricting access to the /api/v1/ingestionPipelines endpoint to authorized users only can limit the potential for JWT extraction. Review and strengthen the permissions associated with the 'Ingestion Bot' role to minimize the impact of a compromised token. Monitoring API access logs for unusual activity, particularly requests to the vulnerable endpoint, can provide early detection of potential exploitation. After upgrading, confirm the fix by attempting to access the /api/v1/ingestionPipelines endpoint with a read-only user account and verifying that JWT tokens are no longer exposed.