GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow: Config API exposes secrets-backend kwargs overrides unmasked, leaking Vault credentials

CVSS 6.5CVE-2026-48892Control plane, storage & DevOpscurated

Impact

Per-key secrets-backend overrides supplied as environment variables such as AIRFLOW__SECRETS__BACKEND_KWARG__SECRET_ID surface in the Config API as synthetic options whose names are not in sensitive_config_values, so the masker leaves them alone. An authenticated user with Config read permission reads the secrets-backend credentials themselves - Vault role_id and secret_id, for example - which is the key to every other secret the deployment stores. That is a privilege jump from a read-only Airflow role to the credential store backing the whole orchestration layer, including whatever cluster and storage credentials the GPU pipelines use. This is a different masker gap from CVE-2026-48828, in a different API.

Who can reach it

Network access to the Airflow UI or REST API as an authenticated user with Config read permission, on a deployment that exposes the Config API and configures its secrets backend via per-key environment overrides.

What to do

Upgrade to apache-airflow 3.3.0 or later and restart the API server. Then rotate the secrets-backend credentials themselves - a Vault AppRole secret_id that was readable must be assumed burned - and consider disabling Config API exposure (expose_config) as a standing hardening step. Note that 3.3.0 does not close the team-scoped variant tracked as CVE-2026-65017.

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.