Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76187 – Authentication Bypass – Apache Airflow Keycloak Provider before 0.10.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76187 is a critical improper-authentication vulnerability in the apache-airflow-providers-keycloak package used by Apache Airflow’s Keycloak auth manager. The unauthenticated OAuth2 token endpoint accepts a client-credentials grant from any confidential client registered in the shared Keycloak realm, not only the client configured for Airflow. This allows an attacker holding valid credentials for an unrelated application in the same realm to obtain a signed Airflow session token, and carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the token endpoint that issues Airflow session tokens does not validate that the client_id presented in a client-credentials grant matches the client_id configured for Airflow in [keycloak_auth_manager]; it forwards the request to Keycloak for any confidential client in the realm.
  • Trigger conditions: Airflow must be configured to use the Keycloak auth manager, and the Keycloak realm used by Airflow must be shared with other confidential clients (a common multi-application realm setup).
  • Attack vector: network, unauthenticated at the Airflow layer — the attacker needs only valid client-credentials for any other confidential client in the same realm, not for Airflow itself. No privileges on Airflow and no user interaction are required.
  • Impact: the attacker’s client credentials are effectively accepted as valid Airflow login material, and Airflow mints a signed session token tied to that client’s service-account identity. The endpoint also relays unauthenticated credential-guessing attempts against Keycloak under Airflow’s identity. Resource authorization is still evaluated per subject, so the practical access gained is whatever that service account is entitled to, plus any Airflow endpoint gated only on being authenticated.

Affected software

  • apache-airflow-providers-keycloak versions before 0.10.0, when configured as the Airflow auth manager against a Keycloak realm shared with other confidential clients.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade apache-airflow-providers-keycloak to version 0.10.0 or later, which restricts the token endpoint to accept only the client ID configured for Airflow.
  • If immediate patching is not possible: disable or restrict the client-credentials grant for non-Airflow clients in the shared Keycloak realm, or isolate Airflow into its own dedicated Keycloak realm so no other confidential clients can obtain tokens accepted by Airflow. Additionally, apply scope restrictions to limit the privileges granted to any service account that could be used in such a token request.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge