CVE-2022-40604: Apache Airflow · Use of Externally-Controlled Format String
Affects Apache AirflowSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIapache-airflowpkg:pypi/apache-airflowOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2022-40604, European organizations should take the following specific actions beyond generic patching advice: 1) Immediately verify the Apache Airflow version in use and upgrade to a version where this vulnerability is fixed (check Apache's official security advisories for patched versions beyond 2.3.4). 2) Implement strict input validation and sanitization on any user-controllable inputs, especially URL parameters, to prevent malicious format strings from being processed. 3) Employ network-level controls such as Web Application Firewalls (WAFs) to detect and block suspicious requests that may exploit format string vulnerabilities. 4) Conduct thorough code reviews and security testing on custom Airflow plugins or extensions that might interact with URL inputs to ensure they do not introduce similar vulnerabilities. 5) Monitor logs for unusual access patterns or error messages related to format string processing to detect potential exploitation attempts early. 6) Restrict access to Airflow web interfaces and APIs using strong authentication and network segmentation to reduce exposure. 7) Educate development and operations teams about the risks of format string vulnerabilities and secure coding practices to prevent recurrence. 8) If immediate patching is not feasible, consider deploying runtime application self-protection (RASP) solutions that can intercept and block malicious format string usage dynamically.
Description
In Apache Airflow 2.3.0 through 2.3.4, part of a url was unnecessarily formatted, allowing for possible information extraction.