CVE-2022-38362 json
Docker Provider <3.0 RCE vulnerability in example dag
published 4y ago modified 4mo ago also GHSA-746v-hfh2-xphm , PYSEC-2026-773 , EUVD-2022-6497
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Apache Airflow Docker's Provider prior to 3.0.0 shipped with an example DAG that was vulnerable to (authenticated) remote code exploit of code on the Airflow worker host.
Patch / fix
- pypi apache-airflow-providers-docker 3.0.0
- Apache Software Foundation Apache Airflow 3.0.0
Is CVE-2022-38362 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 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-providers-docker | <3.0.0 |
3.0.0 |
Affected products
- Apache Software Foundation Apache Airflow
References
-
lists.apache.org
/thread/614p38nf4gbk8xhvnskj9b1sqo2dknkb
web, mailing-list, vendor-advisory
-
openwall.com
/lists/oss-security/2022/08/16/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-38362
advisory
-
pypi.org
/project/apache-airflow-providers-docker
package
-
github.com
/advisories/GHSA-746v-hfh2-xphm
advisory
Sources
- CVE List CVE-2022-38362
- GitHub Advisory GHSA-746v-hfh2-xphm
- NVD CVE-2022-38362
- OSV PYSEC-2026-773
Fencer Intel 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.