Quick answers
- Is CVE-2026-111452 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111452 being exploited in the wild.
- How severe is CVE-2026-111452?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow.
- Is there a fix for CVE-2026-111452?
- 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-111452 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111452?
- Check whether you run Apache Airflow. 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 secrets masker's key normalization function lowercased keys and replaced non-word characters with underscores, which failed to match camelCase or PascalCase keys against multi-word sensitive field names (e.g., `privateKey` never matched `private_key`). An unauthenticated or unprivileged user with read access to task logs, rendered template fields, or API responses could extract plaintext credentials stored under camelCase keys. The fix adds PascalCase/camelCase boundary splitting during key matching to correctly identify sensitive fields regardless of naming convention.
Affected products
- Apache Airflow
Timeline
- 2026-10-16: patched
- 2026-11-09: advisory