Apache Airflow: task JWT tokens written to logs let UI users act as Dag authors

Impact

The JWT tokens that Airflow issues to tasks for calling back into the execution API were written into task logs. Any user who can read logs in the UI can lift a token and act with the privileges of a Dag author, which on a multi-team GPU cluster means submitting or altering work that lands on other teams' nodes and queues. Log read access is normally granted much more broadly than Dag authoring, so this collapses the separation the RBAC model is meant to provide.

Who can reach it

Any authenticated Airflow UI/API user with task-log read access. No special configuration needed.

What to do

Upgrade to Airflow 3.2.0 and restart the API server, scheduler and workers. Treat logs written by affected versions as containing live credentials: purge or restrict them, since tokens remain valid until they expire.

References

Related entries

• Apache Airflow: asset materialize permission lets a user trigger DAGs they have no access toCVE-2026-32228 · Apache Airflow (asset materialize permission)High
• Automated Logic WebCTRL / i-Vu server and controllers, BACnet transport trust: This is the vendor formally concedingCVE-2026-32666 · Automated Logic WebCTRL / i-Vu server and controllers, BACnet transport trustHigh
• Apache Tomcat: Missing encryption of sensitive data introduced by the CVE-2026-29146 fixCVE-2026-34486 · Apache TomcatHigh
• Apache Airflow: bulk Task Instance API authorizes the URL dag_id but acts on the body dag_idCVE-2026-41084 · Apache Airflow (bulk Task Instances API, PATCH/DELETE authorization)High
• JFrog Artifactory: internal anonymous-user token returned to unauthenticated callersCVE-2026-42018 · JFrog Artifactory (anonymous-user token disclosure)High
• Prometheus: Azure AD remote-write client secret served in plaintext from the /-/config endpointCVE-2026-42151 · Prometheus (Azure AD remote-write OAuth client_secret in /-/config)High