GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow 3.0.3: users with read-only permissions can view sensitive connection fields

CVSS 6.5CVE-2025-54831Control plane, storage & DevOpscurated

Impact

Airflow 3 moved to a write-only model for sensitive Connection fields: only connection editors were supposed to see passwords and extras. In 3.0.3 that model was broken, and any user with READ permission could retrieve the sensitive values through both the REST API and the UI, bypassing AIRFLOW__CORE__HIDE_SENSITIVE_VAR_CONN_FIELDS. On a fleet where Airflow drives data loading, training launches and model promotion, those connections are the credentials for object storage, registries, databases and cluster APIs - so a low-privilege viewer account becomes a credential dump. Airflow 2.x is unaffected, where editor visibility was the documented behavior.

Who can reach it

Any authenticated Airflow user holding only read permissions on Connections, via the REST API or the web UI. No editor role and no cluster access required.

What to do

Upgrade Airflow from 3.0.3 to 3.0.4 or later - a scheduler/webserver/API-server restart, no GPU node impact. Treat any connection secret that existed on a 3.0.3 install as exposed to every read-capable user and rotate it; the config flag that normally hides these fields did not help here.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.