← Back to results
Vulnerability record · public intelligence
CVE-2026-86466
HIGH

Apache Airflow FAB provider: FAB Authentik provider: id_token issuer/audience not validated

Published Sep 16, 2026 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood0.37%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Apache Airflow FAB provider: FAB Authentik provider: id_token issuer/audience not validated

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Apache Airflow FAB provider: the Authentik OAuth path in the FAB auth manager does not validate the issuer or audience claims of the id_token it accepts. An attacker holding a token that the same Authentik identity provider minted for a different client application can present it to Airflow and be authenticated as the user it names, because the audience claim is never checked. Affects deployments using the FAB auth manager with Authentik OAuth where the same Authentik instance also serves other applications; the attacker needs a valid token for any of those other applications, not for Airflow.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. GitHub advisory ↗
  2. lists.apache.org ↗
  3. www.cve.org ↗
  4. lists.apache.org ↗

Record history

Published Sep 16, 2026 · Last refreshed Nov 3, 2026