Quick answers
- Is CVE-2026-111455 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111455 being exploited in the wild.
- How severe is CVE-2026-111455?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow before 3.4.0.
- Is there a fix for CVE-2026-111455?
- Yes: fixed in Apache Airflow 3.4.0. Until then: Disable the non-default `[core] test_connection` setting if asynchronous connection testing is not required, or restrict who has create connection permissions until upgraded. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111455 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111455?
- 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
Disable the non-default `[core] test_connection` setting if asynchronous connection testing is not required, or restrict who has create connection permissions until upgraded.
Technical details
The vulnerability exists in the asynchronous connection test handler when the non-default `[core] test_connection` setting is enabled. The API checks permissions at the time the test is queued (checking "create" permission if the connection doesn't exist yet), but when the test completes with `commit_on_success`, it writes the connection regardless of whether it was created by another user in the interim. The fix adds a `commit_allows_update` flag recorded at enqueue time to prevent create-only tests from overwriting subsequently-created connections.
Affected products
- Apache Airflow before 3.4.0
Timeline
- 2026-11-09: disclosed
- 2026-10-16: patched