Quick answers
- Is CVE-2026-86466 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86466 being exploited in the wild.
- How severe is CVE-2026-86466?
- High severity, with a CVSS score of 8.1, published 16 September 2026.
- Which products and versions are affected?
- Apache Airflow FAB provider before 3.9.0.
- Is there a fix for CVE-2026-86466?
- A patch was published on 2026-09-09: Fix merged to apache/airflow main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86466 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86466?
- Check whether you run Apache-Airflow-Providers-Fab. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Apache Airflow FAB provider's Authentik OAuth integration fails to validate the `issuer` and `audience` claims in received OpenID Connect ID tokens. This is a token validation bypass vulnerability in the OAuth/OIDC implementation. An attacker with a valid token minted by the same Authentik instance for a different client application can present it to Airflow; since the audience claim is never checked, the token is accepted and the attacker is authenticated as the user named in the token. The attack requires network access to Airflow and a valid token from any application served by the target Authentik instance—not necessarily Airflow itself. This issue was previously fixed for Azure AD (CVE-2026-75156) but the Authentik code path was overlooked. Upgrade to apache-airflow-providers-fab version 3.9.0 or later to obtain the fix.
Affected products
- Apache Airflow FAB provider before 3.9.0
Timeline
- 2026-09-16: disclosed
- 2026-09-09: patched: Fix merged to apache/airflow main branch