CVE-2026-86467: Apache Airflow Amazon provider: AWS auth manager: SAML login CSRF logs users into the attacker's account

Published Oct 20, 2026
·
Updated

Apache Airflow Amazon provider: the AWS auth manager's SAML login flow does not bind the authentication response to the browser that began it. The login handler discards the AuthnRequest ID and the callback validates the assertion without requiring a matching InResponseTo, so an unauthenticated attacker who can cause a victim to load a page can complete a SAML login in the victim's browser using the attacker's own assertion, silently logging the victim into the attacker's Airflow account. Subsequent work the victim performs lands in a session the attacker controls.

Affects deployments using the AWS auth manager with SAML authentication. The victim needs only to visit an attacker-controlled page; no Airflow account or credential is required of the attacker. This is the same login-CSRF class fixed in the Keycloak auth manager as CVE-2026-40948.

Users of apache-airflow-providers-amazon are recommended to upgrade to version 9.38.0, which fixes the issue.

Affected Software

1 affected component
pypi/apache-airflow-providers-amazon<9.38.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade apache-airflow-providers-amazon to a version that resolves this vulnerability.

    Fixed in 9.38.0

Event History

Oct 20, 2026
CVE Published
via MITRE·02:37 AM
Data Sourced
via MITRE·02:37 AM
DescriptionWeakness
Data Sourced
via NVD·03:17 AM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using the Apache Airflow Amazon provider's AWS auth manager with SAML authentication are affected. The provided information does not indicate that other authentication configurations are affected.

2

What does an attacker need to exploit this issue?

The attacker needs to cause a victim to load an attacker-controlled page and use the attacker's own SAML assertion. The attacker does not need an Airflow account or Airflow credentials.

3

What is the practical impact on a victim?

The victim can be silently logged into the attacker's Airflow account. Actions the victim subsequently performs occur in a session controlled by the attacker.

4

How can this be remediated?

Upgrade apache-airflow-providers-amazon to version 9.38.0, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203