Host secret disclosure via unchecked environment interpolation
Published Jul 29, 2026 · Updated Jul 29, 2026
Protection mechanism failure in Flyto2 Core before 2.26.6 allows remote attackers to read host environment secrets through workflows. The variable resolver calls os.getenv for every ${env.VAR} token before module-policy enforcement, without checking the env.get denylist or an allowlist. An untrusted workflow can place the returned value into an allowed outbound module, exposing API keys, tokens, or DSNs held in the process environment.
Summary
What happened
Protection mechanism failure in Flyto2 Core before 2.26.6 allows remote attackers to read host environment secrets through workflows. The variable resolver calls os.getenv for every ${env.VAR} token before module-policy enforcement, without checking the env.get denylist or an allowlist. An untrusted workflow can place the returned value into an allowed outbound module, exposing API keys, tokens, or DSNs held in the process environment.
The record
- CVE
- CVE-2026-67427
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Flyto2
- Product
- Flyto2 Core
- Classifications
- CWE-668, CWE-522, CWE-693, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.26.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA environment interpolation reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo