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