Skip to content
major vulnerability· requires attention

Apache Airflow is widely used; this vulnerability enables cross-session privilege escalation in workflow infrastructure and can impact orgs' data pipelines and operations.

Applications

CVE-2026-76186

9.1
Critical
EPSS n/aPatch availableSep 18, 2026

Airflow Keycloak token mismatch enables cross-session privilege escalation.

common questions

Is CVE-2026-76186 being exploited?

Not confirmed. CVE-2026-76186 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-76186?

CVE-2026-76186 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76186?

Yes. A fix has been recorded for CVE-2026-76186. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76186 affect?

CVE-2026-76186 affects Apache Airflow 3.3+ with Keycloak auth manager, apache-airflow-providers-keycloak < 0.10.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76186?

Upgrade provider to >=0.10.0; revoke/rotate sessions and Keycloak tokens immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Airflow 3.3+ with Keycloak auth managerapache-airflow-providers-keycloak < 0.10.0
impact

Attacker with a valid Airflow login plus a stolen Keycloak token can act with another user's privileges and persist across sessions.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Airflow Keycloak provider
  • affected< 0.10.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free