CVE-2025-54415: astronomer dag-factory · OS Command Injection
Affects astronomer dag-factorySource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in 0.23.0 : patch astronomer dag-factory as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.23.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:UExploitation evidence
Disclosed: evidence found.
CVE published 26 Jul 2025
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 |
|---|---|---|
GitHubastronomer/dag-factorypkg:github/astronomer/dag-factoryOther 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
European organizations should immediately upgrade dag-factory to version 0.23.0a9 or later to remediate the vulnerability. Additionally, organizations should audit their GitHub Actions workflows to avoid using pull_request_target triggers in contexts where untrusted code can be executed. Implement strict branch protection rules and require code reviews before merging pull requests to reduce the risk of malicious contributions. Limit the permissions granted to GITHUB_TOKEN by using fine-grained tokens or GitHub App tokens with minimal scopes. Employ secrets scanning and monitoring to detect unauthorized access or exfiltration attempts. Consider isolating CI/CD runners in restricted environments with minimal network access to limit the impact of potential compromise. Regularly review and rotate secrets used in workflows. Finally, conduct security awareness training for developers on secure CI/CD practices and the risks of third-party dependencies.
Description
dag-factory is a library for Apache Airflow® to construct DAGs declaratively via configuration files. In versions 0.23.0a8 and below, a high-severity vulnerability has been identified in the cicd.yml workflow within the astronomer/dag-factory GitHub repository. The workflow, specifically when triggered by pull_request_target, is susceptible to exploitation, allowing an attacker to execute arbitrary code within the GitHub Actions runner environment. This misconfiguration enables an attacker to establish a reverse shell, exfiltrate sensitive secrets, including the highly-privileged GITHUB_TOKEN, and ultimately gain full control over the repository. This is fixed in version 0.23.0a9.
References
- github.com/astronomer/dag-factory/security/advisories/GHSA-g5hx-xv45-9whg (opens in a new tab)
- github.com/astronomer/dag-factory/pull/460 (opens in a new tab)
- github.com/astronomer/dag-factory/pull/466 (opens in a new tab)
- github.com/astronomer/dag-factory/commit/751c0e58369e784f6a924347e381a705ea8133fe (opens in a new tab)