Quick answers
- Is CVE-2026-67427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67427 being exploited in the wild.
- How severe is CVE-2026-67427?
- High severity, with a CVSS score of 8.6, published 29 July 2026.
- Which products and versions are affected?
- flyto-core (PyPI) < 2.26.7, ECOSYSTEM:introduced=0,fixed=2.26.7.
- Is there a fix for CVE-2026-67427?
- Yes. flyto-core (PyPI): upgrade to 2.26.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67427 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-67427?
- Check whether you run flyto-core (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
- flyto-core (PyPI): upgrade to 2.26.7 or later
pip install "flyto-core>=2.26.7"
Technical details
A vulnerability in Flyto2 Core's workflow engine allows for the exfiltration of host environment variables. While the `env.get` and `env.load_dotenv` modules are denylisted by default to prevent secret exfiltration, the `VariableResolver` in `src/core/engine/variable_resolver.py` performs `${env.VAR}` interpolation without checking the module policy or an allowlist. An attacker can trigger this via the workflow API or MCP agent surface by providing parameters containing the interpolation syntax. The resolved secrets can then be exfiltrated through any allowed outbound module. This issue is patched in version 2.26.7.
Affected products
- flytohub flyto-core < 2.26.7
Identifiers
- CVE-2026-67427
- GHSA-hr7p-wg7r-hg9m
- PYSEC-2026-3570
Timeline
- 2026-07-07: disclosed: Initial report by kaimandalic
- 2026-07-29: advisory: NVD publication date
- 2026-07-30: patched: GitHub Advisory published and version 2.26.7 released