Quick answers
- Is CVE-2026-7725 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7725 being exploited in the wild.
- How severe is CVE-2026-7725?
- Medium severity, with a CVSS score of 6.3, published 4 May 2026.
- Which products and versions are affected?
- prefect (PyPI) < 3.6.25.dev7, ECOSYSTEM:introduced=0,fixed=3.6.25.dev7.
- Is there a fix for CVE-2026-7725?
- Yes. prefect (PyPI): upgrade to 3.6.25.dev7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-7725 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7725?
- Check whether you run prefect (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- prefect (PyPI): upgrade to 3.6.25.dev7 or later
pip install "prefect>=3.6.25.dev7"
Technical details
An argument injection vulnerability exists in Prefect's GitRepository Pull Handler within 'src/prefect/runner/storage.py'. The issue stems from improper neutralization of special elements in the 'commit_sha' and 'directories' arguments used during Git pull steps. A remote attacker with low privileges can exploit this by providing crafted input that is interpreted as command-line arguments by the underlying Git process. This can lead to unauthorized code execution or data manipulation within the runner's context. The vulnerability is addressed in version 3.6.25.dev7.
Affected products
- PrefectHQ prefect < 3.6.25.dev7
Identifiers
- CVE-2026-7725
- GHSA-6rcx-55r6-jx65
- PYSEC-2026-2955
Timeline
- 2026-05-04: disclosed
- 2026-05-04: advisory
- 2026-05-22: patched: GitHub advisory reviewed and patch confirmed.