API key disclosure via caller-controlled provider endpoint
Published Jul 29, 2026 · Updated Jul 29, 2026
Credential disclosure in Flyto2 Core before 2.26.6 allows remote attackers to steal provider API keys via a crafted base_url. The llm.chat _call_openai path reads a provider key from an environment variable and attaches it as a Bearer token to the caller-supplied endpoint. An unauthenticated caller must control base_url through the MCP agent or hosted API surface; successful exploitation exposes the key and the data or billing access granted by it.
Summary
What happened
Credential disclosure in Flyto2 Core before 2.26.6 allows remote attackers to steal provider API keys via a crafted base_url. The llm.chat _call_openai path reads a provider key from an environment variable and attaches it as a Bearer token to the caller-supplied endpoint. An unauthenticated caller must control base_url through the MCP agent or hosted API surface; successful exploitation exposes the key and the data or billing access granted by it.
The record
- CVE
- CVE-2026-67425
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Flyto2
- Product
- Flyto2 Core
- Classifications
- CWE-522, CWE-201, T1552
- 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-qq9q-xgm3-xv9g key-exfiltration 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