CVE-2025-54831: Apache Airflow Information Disclosure

CVE-2025-54831 Overview

CVE-2025-54831 is an information disclosure vulnerability in Apache Airflow 3.0.3. The flaw allows users with READ permissions to view sensitive Connection fields through both the REST API and the web UI. Apache Airflow 3 introduced a write-only model intended to restrict sensitive connection fields to Connection Editing Users. Version 3.0.3 unintentionally violated this model and bypassed the AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS configuration option. Airflow 2.x is not affected because exposing sensitive information to connection editors was the documented behavior in that release line. The issue maps to [CWE-213] (Exposure of Sensitive Information Due to Incompatible Policies).

Critical Impact
Authenticated users with only READ permissions can retrieve passwords, API tokens, and other sensitive credentials stored in Airflow Connections, undermining the intended write-only access model.

Affected Products

Apache Airflow 3.0.3
Apache Airflow REST API (Connections endpoints)
Apache Airflow Web UI (Connections views)

Discovery Timeline

2025-09-26 - CVE-2025-54831 published to NVD
2025-11-04 - Last updated in NVD database

Technical Details for CVE-2025-54831

Vulnerability Analysis

Apache Airflow stores external system credentials in Connection objects. These objects contain fields such as passwords, extras, and other secrets used by operators and hooks at runtime. Airflow 3 redesigned the access model so that sensitive fields could only be set by Connection Editing Users and not read back through the API or UI. In Apache Airflow 3.0.3, the serialization logic for Connections returned sensitive fields in API and UI responses to users holding READ permissions. The AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS setting, which normally masks sensitive values in logs and responses, did not suppress these fields either. Any operator with read access to Connections could therefore enumerate credentials for databases, cloud providers, message brokers, and SaaS integrations wired into Airflow.

Root Cause

The root cause is an authorization and serialization defect in the Airflow 3.0.3 Connections code path. The write-only access policy intended for sensitive fields was not enforced on the read paths exposed by the REST API and UI. The mask routine tied to AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS was not applied to those response objects.

Attack Vector

An authenticated user with READ permission on Connections sends a request to the Connections API endpoint or browses the Connections page in the UI. The response includes the sensitive fields in clear text. No additional privilege escalation step is required, and user interaction is not needed. The attack vector is network-based and depends only on having a low-privilege Airflow account.

The vulnerability is described in prose only because no verified public exploit code is available. See the Apache Mailing List Discussion and the Openwall OSS Security Update for advisory details.

Detection Methods for CVE-2025-54831

Indicators of Compromise

Unexpected GET requests to /api/v1/connections or /api/v2/connections endpoints from accounts that do not normally manage Connections.
Web UI access patterns where READ-only users repeatedly browse the Connections list or individual Connection detail views.
Authentication events from Airflow service accounts on external systems originating from hosts unrelated to scheduled DAG runs.

Detection Strategies

Inspect Airflow webserver and API access logs for Connections endpoint calls and correlate caller identity against role assignments.
Alert when accounts lacking the Op or Admin role retrieve Connection objects via the API.
Compare the running Airflow version against 3.0.3 across all environments and flag any instance still on the vulnerable build.

Monitoring Recommendations

Enable audit logging on the Airflow metadata database and ship logs to a centralized SIEM for correlation.
Monitor downstream systems referenced by Airflow Connections for authentications from unexpected source addresses or at unusual times.
Track configuration drift on AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS and related security settings.

How to Mitigate CVE-2025-54831

Immediate Actions Required

Upgrade Apache Airflow from 3.0.3 to 3.0.4 or later on every scheduler, webserver, and worker node.
Rotate all credentials stored in Airflow Connections that existed during the time the 3.0.3 deployment was reachable by READ users.
Audit Airflow role assignments and remove unnecessary READ access to Connections for non-operator accounts.

Patch Information

The Apache Airflow project fixed the issue in version 3.0.4. Users running 3.0.3 should upgrade directly to >=3.0.4. Airflow 2.x branches are not affected and do not require this patch. Refer to the Apache Mailing List Discussion for the official announcement.

Workarounds

Restrict network access to the Airflow webserver and API to trusted operator workstations until the upgrade is applied.
Remove the Viewer and other READ-only roles from any user who does not require visibility into Connections metadata.
Migrate sensitive credentials out of Airflow Connections into an external secrets backend such as HashiCorp Vault or AWS Secrets Manager and reference them by name.

bash

# Upgrade Apache Airflow to a patched version
pip install --upgrade "apache-airflow>=3.0.4"

# Verify the installed version
airflow version