Loading vulnerability…
CVE-2026-67425 is a high-severity credential exposure vulnerability in Flyto2 Core affecting versions prior to 2.26.6. The flaw arises because components such as llm.chat can read provider API credentials from environment variables when explicit caller credentials are absent, then automatically attach those secrets as Bearer tokens in outbound Authorization headers to a caller-controlled custom base_url. Although the product includes SSRF validation intended to block loopback, private-network, and metadata targets, that protection still permits requests to public routable hosts. As a result, an attacker can supply a public endpoint they control and cause Flyto2 Core to forward operator-held credentials to that endpoint. Exposed secrets can include API keys used for external AI or vector services, creating a direct path to credential exfiltration without requiring code execution on the runner itself.
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.
Patch, then assume compromise.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insecure credential forwarding vulnerability in Flyto2 Core that allows unauthenticated remote attackers to exfiltrate environment-derived operator API keys by supplying a public attacker-controlled base_url.
An information disclosure vulnerability in flytohub flyto-core prior to version 2.26.6 where llm.chat can leak provider API keys in the Authorization header to an attacker-controlled base_url.
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.