CVE-2026-67427 is an information disclosure vulnerability in Flyto2 Core, an execution kernel for automation and AI-agent workflows. In versions prior to 2.26.6, the workflow engine's variable resolver expands ${env.VAR} expressions against arbitrary host environment variables without enforcing an allowlist or capability policy check. As a result, workflow-supplied parameters or step values can bypass the default capability policy restrictions intended to block environment access through env.get and env.load_dotenv. This creates an alternate path to sensitive process environment data and allows secrets to be exposed through otherwise permitted workflow modules, results, or traces.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
env.get and env.load_dotenv as a sufficient protection boundary. Prevent untrusted users, workflows, agents, API clients, or MCP-exposed inputs from supplying ${env.*} expressions or other interpolated values. Restrict or disable workflow and API paths that accept untrusted parameter interpolation, minimize storage of sensitive secrets in process environment variables, and constrain outbound-capable modules and network egress to reduce opportunities for secret exfiltration.Patch, then assume compromise.
flyto-core package to version 2.26.7 or later. In addition to upgrading, the resolver should enforce the same deny-by-default policy and explicit allowlist model for ${env.*} interpolation that applies to direct environment access APIs, or remove implicit environment interpolation entirely and require explicit environment passing at workflow start.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.