# CVE-2026-107474: Apache Airflow connections API sensitive extra masking bypass

Source: https://junglewise.ai/threats/cve-2026-107474-the-apache-airflow-connections-api-did-not-mask-the-apprise  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-107474 · Severity: info · Published 2026-11-09

Apache Airflow's API for managing database and service connections failed to mask sensitive credentials stored in provider-specific fields, such as notification service tokens for the Apprise provider. An authenticated user with permission to view connections could retrieve these credentials in cleartext, potentially exposing third-party service authentication secrets.

Technologies: [Apache Airflow](https://junglewise.ai/threats/technologies/airflow). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-107474 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-107474 being exploited in the wild.

**How severe is CVE-2026-107474?** Informational severity, published 9 November 2026.

**Which products and versions are affected?** Apache Airflow prior to 3.4.0.

**Is there a fix for CVE-2026-107474?** Yes: fixed in apache-airflow 3.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-107474 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-107474?** Check whether you run Apache Airflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in apache-airflow 3.4.0

## Technical details

The connections API used only field-name-based masking for sensitive extras, failing to mask provider-declared secrets with generic names like "config" that could embed notification-service credentials. An authenticated user with read access to connections could retrieve these unmasked values via API calls. The fix adds provider metadata-based masking to hide all fields that any installed provider declares sensitive, independent of connection type.

## Affected products

- Apache Airflow prior to 3.4.0

## Timeline

- 2026-11-09: disclosed
- 2026-10-19: patched

## References

- [https://pypi.python.org/](https://pypi.python.org/)
- [https://github.com/apache/airflow/pull/73794](https://github.com/apache/airflow/pull/73794)

## Related threats

- [Apache Airflow incomplete deserialization check bypass in scheduler](https://junglewise.ai/threats/cve-2026-96285-apache-airflow-3-3-1-shipped-a-fix-for-that-checks-the-scheduler)
- [Apache Airflow scheduler XCom deserialization privilege escalation](https://junglewise.ai/threats/cve-2026-86829-apache-airflow-s-scheduler-fully-deserializes-xcom-values-written)
- [Apache Airflow CLI audit log secrets exposure](https://junglewise.ai/threats/cve-2026-86468-apache-airflow-s-cli-records-its-arguments-in-the-audit-log-but)
- [Apache Airflow unsafe deserialization in deadline alert fields](https://junglewise.ai/threats/cve-2026-82337-apache-airflow-rebuilt-deadline-alert-fields-through-generic)
- [Apache Airflow Task SDK secret cache key collision in multi-team deployments](https://junglewise.ai/threats/cve-2026-76185-apache-airflow-s-task-sdk-secret-cache-built-its-keys-from-the)