Skip to content
Fencer Vulns
high 8.8

CVE-2022-24288 in the critical feed json

Apache Airflow: RCE in example DAGs

published 2022-02-25 4 y ago modified 2026-09-08 2 mo ago also BIT-airflow-2022-24288 , EUVD-2022-0013 , GHSA-3v7g-4pg3-7r6j , PYSEC-2022-30

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
78.4%
EPSS 78.4% chance of exploitation in 30 days, percentile 99.5%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • pypi apache-airflow 2.2.4
  • bitnami airflow 2.2.4
  • Apache Software Foundation Apache Airflow 2.2.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-24288 updated cvss 9.9

Airflow: RCE in example DAGs

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present “Can be mitigated by setting `[core] load_examples` to `False`.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

78.37% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi apache-airflow
<2.2.4
2.2.4
bitnami airflow
<2.2.4
2.2.4

Affected products

  • Apache Software Foundation Apache Airflow

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.