Airflow: apprise connection config extra returned unmasked by the connections API

Impact

The connections API does not mask the apprise provider's config extra, and that field can contain credentials for notification services. A user with permission to read connections gets those credentials in cleartext, even though Airflow 3 treats connection credentials as write-only. The leaked credentials belong to external notification services (chat, paging, email), not to Airflow itself.

Who can reach it

An authenticated Airflow user with permission to read connections, on a deployment that has apprise connections configured.

What to do

Upgrade apache-airflow to 3.4.0 or later and restart the API server. Airflow 2.x is affected and end of life, so it gets no fix and has to move to 3.4.0. Rotate any apprise credentials that users who should not have them could have read.

References

Related entries

• Airflow: reserved serialization keys in Dag run conf crash the scheduler or build objects in the TriggererCVE-2026-111395 · Apache Airflow scheduler and Triggerer (Dag run conf deserialization)Unscored
• Airflow secrets masker: values under camelCase keys left unredacted in logs and API responsesCVE-2026-111452 · Apache Airflow secrets masker (camelCase sensitive key names)Unscored
• Airflow: async connection test lets a create-only user overwrite another user's connectionCVE-2026-111455 · Apache Airflow asynchronous connection test (commit_on_success)Unscored
• Airflow secrets masker: secrets nested more than five levels deep shown in cleartextCVE-2026-113504 · Apache Airflow secrets masker (nesting depth limit)Unscored
• Airflow: failed token revocation at logout is ignored, so the token stays validCVE-2026-113508 · Apache Airflow API logout (server-side token revocation)Unscored
• Gitea: Helm chart upload decompresses without a size limit before the quota check, allowing CPU exhaustionCVE-2026-117677 · Gitea (Helm chart package upload)Unscored