{"vulnerability": "CVE-2026-67425", "sightings": [{"uuid": "535a48ef-8a1a-4c3d-adde-fd2753ceae8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67425", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-qq9q-xgm3-xv9g", "content": "", "creation_timestamp": "2026-07-30T16:35:10.352576Z"}, {"uuid": "0d8c705b-ba80-4b03-b7af-c696602f7076", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67425", "type": "seen", "source": "https://gist.github.com/alon710/118a4cdb35451ca1b82ac84f2659aa47", "content": "# CVE-2026-67425: CVE-2026-67425: Insecure Credential Forwarding in Flyto2 Core\n\n> **CVSS Score:** 8.6\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67425\n\n## Summary\nAn insecure credential forwarding vulnerability in Flyto2 Core prior to version 2.26.6 allows attackers to exfiltrate operator API keys. This occurs because the system forwards environment-derived API keys to user-controlled custom endpoints, bypassing SSRF guards designed only for private target validation.\n\n## TL;DR\nFlyto2 Core incorrectly forwarded high-privilege, environment-derived API keys to caller-controlled endpoints. This allowed unauthenticated remote attackers to exfiltrate sensitive keys by specifying a public, attacker-controlled host as the base URL.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-522, CWE-201\n- **Attack Vector**: Network (AV:N)\n- **CVSS v3.1**: 8.6 (High)\n- **EPSS Score**: 0.00319\n- **Impact**: Confidentiality High (C:H)\n- **Exploit Status**: Proof-of-Concept / Verified Private\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- Flyto2 Core (flytohub/flyto-core)\n- **Flyto2 Core**: < 2.26.6 (Fixed in: `2.26.6`)\n\n## Mitigation\n\n- Upgrade to Flyto2 Core 2.26.6 or later.\n- Configure the FLYTO_TRUSTED_LLM_HOSTS environment variable to whitelist permitted custom API gateways.\n- Establish firewall rules to restrict outbound HTTP/HTTPS traffic to trusted LLM endpoints only.\n\n**Remediation Steps:**\n1. Pull and deploy the latest version (2.26.6+) of Flyto2 Core.\n2. Audit current configuration files and system environments for exposed API keys.\n3. Define FLYTO_TRUSTED_LLM_HOSTS in your runner environments if you utilize self-hosted or proxy model endpoints.\n\n## References\n\n- [Insecure Credential Forwarding in Flyto2 Core](https://github.com/flytohub/flyto-core/security/advisories/GHSA-qq9q-xgm3-xv9g)\n- [Fix Insecure Credential Forwarding Commit](https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc)\n- [Flyto2 Core Release Tag v2.26.6](https://github.com/flytohub/flyto-core/releases/tag/v2.26.6)\n- [NVD - CVE-2026-67425](https://nvd.nist.gov/vuln/detail/CVE-2026-67425)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67425) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-30T22:32:21.523271Z"}, {"uuid": "f4d766f2-ea46-4df5-a30a-06e046ade408", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67425", "type": "seen", "source": "https://gist.github.com/alon710/118a4cdb35451ca1b82ac84f2659aa47", "content": "# CVE-2026-67425: CVE-2026-67425: Insecure Credential Forwarding in Flyto2 Core\n\n> **CVSS Score:** 8.6\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67425\n\n## Summary\nAn insecure credential forwarding vulnerability in Flyto2 Core prior to version 2.26.6 allows attackers to exfiltrate operator API keys. This occurs because the system forwards environment-derived API keys to user-controlled custom endpoints, bypassing SSRF guards designed only for private target validation.\n\n## TL;DR\nFlyto2 Core incorrectly forwarded high-privilege, environment-derived API keys to caller-controlled endpoints. This allowed unauthenticated remote attackers to exfiltrate sensitive keys by specifying a public, attacker-controlled host as the base URL.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-522, CWE-201\n- **Attack Vector**: Network (AV:N)\n- **CVSS v3.1**: 8.6 (High)\n- **EPSS Score**: 0.00319\n- **Impact**: Confidentiality High (C:H)\n- **Exploit Status**: Proof-of-Concept / Verified Private\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- Flyto2 Core (flytohub/flyto-core)\n- **Flyto2 Core**: < 2.26.6 (Fixed in: `2.26.6`)\n\n## Mitigation\n\n- Upgrade to Flyto2 Core 2.26.6 or later.\n- Configure the FLYTO_TRUSTED_LLM_HOSTS environment variable to whitelist permitted custom API gateways.\n- Establish firewall rules to restrict outbound HTTP/HTTPS traffic to trusted LLM endpoints only.\n\n**Remediation Steps:**\n1. Pull and deploy the latest version (2.26.6+) of Flyto2 Core.\n2. Audit current configuration files and system environments for exposed API keys.\n3. Define FLYTO_TRUSTED_LLM_HOSTS in your runner environments if you utilize self-hosted or proxy model endpoints.\n\n## References\n\n- [Insecure Credential Forwarding in Flyto2 Core](https://github.com/flytohub/flyto-core/security/advisories/GHSA-qq9q-xgm3-xv9g)\n- [Fix Insecure Credential Forwarding Commit](https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc)\n- [Flyto2 Core Release Tag v2.26.6](https://github.com/flytohub/flyto-core/releases/tag/v2.26.6)\n- [NVD - CVE-2026-67425](https://nvd.nist.gov/vuln/detail/CVE-2026-67425)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67425) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-31T00:01:11.875348Z"}]}