OpenMetadata 中存在信息泄露的 JWT，暴露了具有高权限的机器人用户

该漏洞的影响非常严重。攻击者利用泄露的 JWT 可以冒充 ingestion-bot，执行破坏性操作，例如修改 OpenMetadata 实例配置，甚至导致数据泄露。泄露的数据可能包括样本数据和与角色/策略相关的服务元数据。攻击者可以利用这些权限进行广泛的破坏，甚至可能导致服务不可用。由于该漏洞允许访问高权限账户，因此其潜在影响范围非常大，可能影响整个 OpenMetadata 实例的安全性。

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. 已保留2026-02-09
2. 发布日期2026-02-11
3. 修改日期2026-02-18
4. EPSS 更新日期2026-03-23

除了升级至 1.11.8 版本外，可以采取一些临时缓解措施。首先，限制对 /api/v1/ingestionPipelines 接口的访问，只允许必要的服务访问。其次，审查 ingestion-bot 的权限，确保其只拥有执行必要任务的最小权限集。如果升级过程出现问题，可以考虑回滚到之前的版本，并尽快修复升级问题。监控 OpenMetadata 日志，查找任何异常活动，例如未经授权的账户访问或配置更改。