CVE-2026-86468 · Package
NO FIX YET · SEE WHAT TO DO
Some Airflow CLI command shapes, such as Variable commands with a trailing --description, --conn-extra, and the inline --password of keycloak-auth-manager commands, are logged without masking their secrets. A user who can read audit events but is denied Variable and Connection access can read those values through the event-log API.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Apache Airflow 3.x with CLI audit logging where users can read audit events. Exposure needs a user who can read audit events but lacks Variable and Connection access, and a command shape that the masking misses. Deployments that do not expose audit events to such users are lower risk.
Not affected if audit-events-restricted, no-cli-secret-args
Who cares apache-airflow, python, self-hosted
airflow version and compare it with the fixed version below.--description, --conn-extra or --password to see whether cleartext secrets were recorded.3.4.0 or later.Apache Airflow's CLI records its arguments in the audit log but masks secrets by argument position, so some supported command shapes leave secrets in cleartext, for example a trailing --description on Variable commands, --conn-extra, and the inline --password of airflow keycloak-auth-manager commands. A user who can read audit events but is denied Variable and Connection access can retrieve those values through the event-log API.
Users of apache-airflow are recommended to upgrade to 3.4.0 or later. Audit-log entries written before the upgrade keep the cleartext values: purge the affected entries and rotate the secrets they contain.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.