CVE-2026-26010Public exploitNetwork attack vector

Privilege escalation via ingestion-bot JWT disclosure

Published Feb 11, 2026 · Updated Feb 11, 2026

Privilege escalation in OpenMetadata before 1.11.8 allows remote authenticated users to obtain an ingestion-bot JWT through an API response. The ingestion-pipeline retrieval path serializes openMetadataWorkflowConfig, including its jwtToken, to read-only callers instead of cleaning sensitive workflow configuration from the response. Read-only access and a configured Glue, Redshift, or Postgres ingestion service are required; the exposed bot token permits destructive metadata changes and access to otherwise restricted sample data and service metadata.

CVSS severity7.6
High
EPSS probability0.34%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Privilege escalation in OpenMetadata before 1.11.8 allows remote authenticated users to obtain an ingestion-bot JWT through an API response. The ingestion-pipeline retrieval path serializes openMetadataWorkflowConfig, including its jwtToken, to read-only callers instead of cleaning sensitive workflow configuration from the response. Read-only access and a configured Glue, Redshift, or Postgres ingestion service are required; the exposed bot token permits destructive metadata changes and access to otherwise restricted sample data and service metadata.

The record

CVE
CVE-2026-26010
Published
Feb 11, 2026
Updated
Feb 11, 2026
Vendor
OpenMetadata
Product
OpenMetadata
Classifications
CWE-269, T1550.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.11.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

OpenMetadata · OpenMetadataversion=< 1.11.8

Published CVSS scores

7.6NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
7.6GitHub, Inc.CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-269Improper Privilege Management
T1550.001Use Alternate Authentication Material: Application Access Token

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo