Airflow vulnerabilitiesAnd the versions its exploited flaws hit.
Airflow is made by Apache. We track 92 published vulnerabilities listed under that exact name, across 114 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 18 January 2022. Apache lists newer releases under their own names, such as Airflow Cncf Kubernetes, so check those pages too.
The most recent Airflow flaw added to the known-exploited list is CVE-2020-11978, on 18 January 2022. We keep watching the known-exploited list.
Is Airflow listed under other names? Yes.
Apache also lists Airflow under more specific names, such as Airflow Cncf Kubernetes and Airflow Common SQL Provider. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Airflow Cncf Kubernetes2 published vulnerabilities
- Airflow Common SQL Provider1 published vulnerability
- Airflow Celery Provider1 published vulnerability
- Airflow Hive Provider1 published vulnerability
- Airflow Spark Provider1 published vulnerability
- Airflow Sqoop Provider1 published vulnerability
- Airflow Hdfs Provider1 published vulnerability
Which versions of Airflow do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 1.10.11" means every version up to, but not including, 1.10.11. Find your version, then patch.
- CVE-2020-11978Exploited list, 18 Jan 2022
Apache Airflow Command Injection
before 1.10.11 - CVE-2020-13927Exploited list, 18 Jan 2022
Apache Airflow's Experimental API Authentication Bypass
before 1.10.11
Which Airflow vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 8.8Apache Airflow Command Injection
A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow.
- 9.8Apache Airflow's Experimental API Authentication Bypass
The previous default setting for Airflow's Experimental API was to allow all API requests without authentication.
Which Airflow flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact.
- >99%
An issue was found in Apache Airflow versions 1.10.10 and below.
- 86%CVE-2022-40127High
A vulnerability in Example Dags of Apache Airflow allows an attacker with UI access who can trigger DAGs, to execute arbitrary commands via manually provided run_id parameter.
- 82%CVE-2022-45402Medium
In Apache Airflow versions prior to 2.4.3, there was an open redirect in the webserver's `/login` endpoint.
- 81%CVE-2021-38540Critical
The variable import endpoint was not protected by authentication in Airflow >=2.0.0, <2.1.3.
- 78%CVE-2022-24288High
In Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI.
- 37%CVE-2020-11981Critical
An issue was found in Apache Airflow versions 1.10.10 and below.
- 25%CVE-2020-13944Medium
In Apache Airflow < 1.10.12, the "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit.
- 24%CVE-2020-17526High
Incorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Airflow Webserver on...
- 16%CVE-2020-17515Medium
The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit.
Running Airflow? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow.
- Matched to
- Airflow on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 92 published vulnerabilities listed under the name Airflow, across 114 versions. The most recent Airflow flaw added to the known-exploited list is CVE-2020-11978, on 18 January 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2020-11978 and CVE-2020-13927.
Apache also lists Airflow under more specific names, such as Airflow Cncf Kubernetes and Airflow Common SQL Provider. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-11978, affects before 1.10.11. The versions for every exploited flaw are listed on this page.
Create a EdgeProtect account and track Airflow. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.