{"vulnerability": "CVE-2026-6742", "sightings": [{"uuid": "7fafa28f-e803-4c48-b7f4-b7e2bab58e9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67426", "type": "seen", "source": "https://bsky.app/profile/termsofsurrender.bsky.social/post/3mrt66ra3h62g", "content": "Unauthenticated SSRF Turns Flyto2 Into A Secret-Leaking Confessional\nPANIC 88% | Lag 0.0h | CVE-2026-67426 is a critical SSRF in Flyto2 Core. The unauthenticated /run endpoint can exfiltrate r\n#AfterShockIndex\nREAD MORE", "creation_timestamp": "2026-07-30T00:20:19.655037Z"}, {"uuid": "be64f72f-6e34-449d-b0cf-607b2c095fcf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67424", "type": "seen", "source": "https://gist.github.com/alon710/5c4b46a299dac54e7caa99802f7ad9a8", "content": "# CVE-2026-67424: CVE-2026-67424: Server-Side Request Forgery Bypass via Unvalidated Redirects in Flyto2 Core\n\n> **CVSS Score:** 8.5\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67424\n\n## Summary\nAn SSRF vulnerability exists in Flyto2 Core due to improper validation of intermediate HTTP redirect hops. While the initial request target is validated against an SSRF protection policy, the HTTP client library (aiohttp) transparently follows 30x redirects to local, internal, or cloud metadata endpoints without application-level revalidation.\n\n## TL;DR\nFlyto2 Core follows HTTP redirects to private internal subnets without revalidating intermediate URLs, leading to an SSRF vulnerability (CVSS 8.5).\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-918\n- **Attack Vector**: Network\n- **CVSS Base Score**: 8.5\n- **EPSS Score**: 0.00236\n- **EPSS Percentile**: 14.80%\n- **Exploit Status**: poc\n- **KEV Status**: Not listed\n\n## Affected Systems\n\n- Flyto2 Core execution kernel (flyto-core)\n- **flyto-core**: < 2.26.7 (Fixed in: `2.26.7`)\n\n## Mitigation\n\n- Upgrade the flyto-core library to version 2.26.7 or newer to enforce hop-by-hop validation.\n- Apply strict firewall egress rules on runner nodes to block outbound requests to private network subnets.\n- Configure cloud instance metadata services (IMDS) to require session tokens (IMDSv2) to mitigate generic, credential-grabbing SSRF attacks.\n\n**Remediation Steps:**\n1. Identify all active deployments running flyto-core versions older than 2.26.7.\n2. Run the pip upgrade command: pip install --upgrade flyto-core>=2.26.7\n3. Validate the configuration of the SSRF guard utility variables within the environment config file.\n4. Restart active execution runner daemons to load the updated validation logic.\n\n## References\n\n- [GHSA-c9hr-64h3-gxpc: Guarded HTTP modules follow redirects into internal space](https://github.com/flytohub/flyto-core/security/advisories/GHSA-c9hr-64h3-gxpc)\n- [Flyto Core Hardening Commit](https://github.com/flytohub/flyto-core/commit/0a0a528520ec18f5a21f1ddf858a71cc1edfb6e9)\n- [NVD - CVE-2026-67424 Detail](https://nvd.nist.gov/vuln/detail/CVE-2026-67424)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67424) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-30T15:31:53.933647Z"}, {"uuid": "2cf08b77-4424-4ca9-b695-92852fc4af0c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67428", "type": "seen", "source": "https://gist.github.com/alon710/abbfb678b2ea15b959183e89124a0f42", "content": "# CVE-2026-67428: CVE-2026-67428: Server-Side Request Forgery in Flyto2 Core HTTP-Emitting Modules\n\n> **CVSS Score:** 8.5\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67428\n\n## Summary\nFlyto2 Core (flyto-core) prior to version 2.26.7 did not utilize its centralized SSRF validation mechanism ('validate_url_with_env_config') across multiple HTTP-emitting modules. This oversight allowed low-privileged users executing automated workflows to perform Server-Side Request Forgery (SSRF) attacks against internal endpoints, loopback interfaces, and cloud provider metadata services.\n\n## TL;DR\nLow-privileged users can execute arbitrary Server-Side Request Forgery (SSRF) attacks against cloud metadata endpoints and local networks due to unvalidated HTTP-emitting modules in Flyto2 Core.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-918\n- **Attack Vector**: Network (AV:N)\n- **CVSS Score**: 8.5 (High)\n- **EPSS Score**: 0.00337 (26.26th percentile)\n- **Impact**: Server-Side Request Forgery / Internal Reconnaissance / Metadata Exfiltration\n- **Exploit Status**: PoC available, no active exploitation reported\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- flyto-core\n- **flyto-core**: < 2.26.7 (Fixed in: `2.26.7`)\n\n## Mitigation\n\n- Upgrade to flyto-core version 2.26.7 or above\n- Enforce container network sandboxing to prevent egress to private host segments\n- Enforce IMDSv2 on cloud compute hosts with an HTTP hop limit of 1\n\n**Remediation Steps:**\n1. Pull the latest Docker image or package release for flyto-core containing tag 2.26.7\n2. Rebuild worker execution instances to apply updated Python source dependencies\n3. Configure egress routing tables inside container hosts to explicitly drop packets aimed at local loopback interfaces and RFC 1918 networks\n4. Audit workflow system execution logs for keywords matching SSRF_BLOCKED to identify blocked malicious behavior\n\n## References\n\n- [GHSA-pgwh-4jj4-qm8v: Decentralized SSRF in Flyto2 Core](https://github.com/flytohub/flyto-core/security/advisories/GHSA-pgwh-4jj4-qm8v)\n- [Flyto2 Core Release v2.26.7](https://github.com/flytohub/flyto-core/releases/tag/v2.26.7)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67428) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-30T16:30:59.636678Z"}, {"uuid": "268e73a1-e819-442a-ab1f-3ecef2a6ae16", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67424", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-c9hr-64h3-gxpc", "content": "", "creation_timestamp": "2026-07-30T16:35:03.253549Z"}, {"uuid": "3e0d0f92-4ce7-4f48-bbaf-940112f0e3e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67428", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-pgwh-4jj4-qm8v", "content": "", "creation_timestamp": "2026-07-30T16:35:05.627739Z"}, {"uuid": "d413a65c-9112-47fa-a9a7-1901efd88808", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67427", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-hr7p-wg7r-hg9m", "content": "", "creation_timestamp": "2026-07-30T16:35:12.737819Z"}, {"uuid": "bf9e7eaf-55a2-4d7f-9099-08bcdb201581", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67426", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-jx74-cqjv-2c67", "content": "", "creation_timestamp": "2026-07-30T16:35:07.996589Z"}, {"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": "233bdfde-65a7-4a90-bcf4-01f429842f93", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67429", "type": "published-proof-of-concept", "source": "https://github.com/flytohub/flyto-core/security/advisories/GHSA-2956-977x-2w3r", "content": "", "creation_timestamp": "2026-07-30T16:35:15.122895Z"}, {"uuid": "ca6ab918-4af3-4511-b4ac-6e848c0635a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67426", "type": "seen", "source": "https://gist.github.com/alon710/c5ece1b4b71f33d4bb332d0422fd7596", "content": "# CVE-2026-67426: CVE-2026-67426: Unauthenticated Remote Code Execution and Secret Exfiltration in Flyto2 Core\n\n> **CVSS Score:** 9.3\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67426\n\n## Summary\nCVE-2026-67426 is a critical vulnerability in Flyto2 Core prior to version 2.26.7. The standalone flyto-verification service binds to all interfaces (0.0.0.0) on port 8344 and exposes an unauthenticated POST /run endpoint. This endpoint accepts an arbitrary client-controlled callback URL and makes an outbound POST request containing the sensitive internal runner secret in the headers. Attackers can exploit this to retrieve the FLYTO_RUNNER_SECRET and perform Server-Side Request Forgery (SSRF) against internal network targets.\n\n## TL;DR\nThe flyto-verification service exposed an unauthenticated endpoint that sent internal runner secrets to arbitrary callback URLs, facilitating credential exfiltration and SSRF.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-306, CWE-918, CWE-522\n- **Attack Vector**: Network\n- **CVSS Base Score**: 9.3\n- **EPSS Score**: 0.00291 (0.29%)\n- **Exploit Status**: poc\n- **KEV Status**: not listed\n- **Affected Component**: flyto-verification service (port 8344)\n\n## Affected Systems\n\n- Flyto2 Core\n- **flyto-core**: < 2.26.7 (Fixed in: `2.26.7`)\n\n## Mitigation\n\n- Update flyto-core to version 2.26.7 or newer.\n- Bind port 8344 exclusively to local network interfaces or trusted internal container subnets.\n- Configure the FLYTO_VERIFICATION_API_KEY environment variable to enable token comparison checks.\n- Use FLYTO_TRUSTED_CALLBACK_HOSTS to limit authorized callback endpoints.\n\n**Remediation Steps:**\n1. Identify all deployment instances running flyto-core versions prior to v2.26.7.\n2. Modify deployment configuration files or docker-compose files to pull flyto-core:2.26.7 or higher.\n3. Inject environment variable FLYTO_VERIFICATION_API_KEY with a secure, randomly generated alphanumeric string.\n4. Configure the FLYTO_ENGINE_URL and FLYTO_TRUSTED_CALLBACK_HOSTS environment variables to reflect trusted services.\n5. Deploy network security groups or local firewall rules (iptables/ufw) to drop external traffic attempting to connect to TCP port 8344.\n6. Restart the flyto-verification containers to apply the patched binary and environment configurations.\n\n## References\n\n- [National Vulnerability Database record for CVE-2026-67426](https://nvd.nist.gov/vuln/detail/CVE-2026-67426)\n- [CVE Program Record for CVE-2026-67426](https://www.cve.org/CVERecord?id=CVE-2026-67426)\n- [GitHub Security Advisory (GHSA-jx74-cqjv-2c67)](https://github.com/flytohub/flyto-core/security/advisories/GHSA-jx74-cqjv-2c67)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67426) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-30T20:33:08.589232Z"}, {"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": "cd44b5af-8db2-4165-a37d-65117227153a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67427", "type": "seen", "source": "https://gist.github.com/alon710/937397e52a8e0970b2abb603a8f2aff3", "content": "# CVE-2026-67427: CVE-2026-67427: Host Environment Variable Access Policy Bypass via Template Interpolation in Flyto2 Core\n\n> **CVSS Score:** 8.6\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67427\n\n## Summary\nCVE-2026-67427 is a capability bypass vulnerability in the Flyto2 Core workflow execution kernel. Due to a logical inconsistency in how dynamic parameters are resolved, the system evaluates environment variables via template interpolation prior to executing capability filter validation. This permits unprivileged workflow definitions to completely bypass denylist restrictions on the `env.get` module, exfiltrating critical host configurations, API tokens, and credentials via allowed communication channels.\n\n## TL;DR\nA logical separation-of-duty flaw in Flyto2 Core's parser allows workflows to bypass security policies. By embedding '${env.VARIABLE}' template strings inside allowed modules, attackers can extract system-level credentials without trigger-blocking module denylists.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-693 (Protection Mechanism Failure)\n- **Attack Vector**: Network\n- **CVSS v3.1 Score**: 8.6 (High)\n- **EPSS Score**: 0.00339 (Percentile: 26.51%)\n- **Impact**: Information Disclosure (Host Secret Extraction)\n- **Exploit Status**: Proof-of-Concept / Technical Analysis\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- Flyto2 Core\n- **flyto-core**: < 2.26.6 (Fixed in: `2.26.6`)\n\n## Mitigation\n\n- Upgrade flyto-core to version 2.26.6 or higher.\n- Define explicit environment variable boundaries using the newly introduced FLYTO_ENV_VAR_ALLOWLIST variable.\n- Isolate automation container runtimes and limit the configuration variables exposed to host processes.\n\n**Remediation Steps:**\n1. Identify all production and test environments running flytohub/flyto-core versions below 2.26.6.\n2. Update project configuration files and build specifications to require version 2.26.6.\n3. Apply the FLYTO_ENV_VAR_ALLOWLIST environment variable in service deployment manifests to restrict dynamic template resolution.\n4. Review historical workflow execution records and audit logs for patterns resembling dynamic variable interpolation calls.\n\n## References\n\n- [GitHub Security Advisory GHSA-hr7p-wg7r-hg9m](https://github.com/flytohub/flyto-core/security/advisories/GHSA-hr7p-wg7r-hg9m)\n- [Fix Commit d5f89d7](https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc)\n- [Flyto Core v2.26.6 Release Notes](https://github.com/flytohub/flyto-core/releases/tag/v2.26.6)\n- [Official CVE Record](https://www.cve.org/CVERecord?id=CVE-2026-67427)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67427) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-30T23:32:08.881211Z"}, {"uuid": "ee835e43-d448-4cd3-af5b-f2f7b97f1f53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67427", "type": "seen", "source": "https://gist.github.com/alon710/937397e52a8e0970b2abb603a8f2aff3", "content": "# CVE-2026-67427: CVE-2026-67427: Host Environment Variable Access Policy Bypass via Template Interpolation in Flyto2 Core\n\n> **CVSS Score:** 8.6\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67427\n\n## Summary\nCVE-2026-67427 is a capability bypass vulnerability in the Flyto2 Core workflow execution kernel. Due to a logical inconsistency in how dynamic parameters are resolved, the system evaluates environment variables via template interpolation prior to executing capability filter validation. This permits unprivileged workflow definitions to completely bypass denylist restrictions on the `env.get` module, exfiltrating critical host configurations, API tokens, and credentials via allowed communication channels.\n\n## TL;DR\nA logical separation-of-duty flaw in Flyto2 Core's parser allows workflows to bypass security policies. By embedding '${env.VARIABLE}' template strings inside allowed modules, attackers can extract system-level credentials without trigger-blocking module denylists.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-693 (Protection Mechanism Failure)\n- **Attack Vector**: Network\n- **CVSS v3.1 Score**: 8.6 (High)\n- **EPSS Score**: 0.00339 (Percentile: 26.51%)\n- **Impact**: Information Disclosure (Host Secret Extraction)\n- **Exploit Status**: Proof-of-Concept / Technical Analysis\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- Flyto2 Core\n- **flyto-core**: < 2.26.6 (Fixed in: `2.26.6`)\n\n## Mitigation\n\n- Upgrade flyto-core to version 2.26.6 or higher.\n- Define explicit environment variable boundaries using the newly introduced FLYTO_ENV_VAR_ALLOWLIST variable.\n- Isolate automation container runtimes and limit the configuration variables exposed to host processes.\n\n**Remediation Steps:**\n1. Identify all production and test environments running flytohub/flyto-core versions below 2.26.6.\n2. Update project configuration files and build specifications to require version 2.26.6.\n3. Apply the FLYTO_ENV_VAR_ALLOWLIST environment variable in service deployment manifests to restrict dynamic template resolution.\n4. Review historical workflow execution records and audit logs for patterns resembling dynamic variable interpolation calls.\n\n## References\n\n- [GitHub Security Advisory GHSA-hr7p-wg7r-hg9m](https://github.com/flytohub/flyto-core/security/advisories/GHSA-hr7p-wg7r-hg9m)\n- [Fix Commit d5f89d7](https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc)\n- [Flyto Core v2.26.6 Release Notes](https://github.com/flytohub/flyto-core/releases/tag/v2.26.6)\n- [Official CVE Record](https://www.cve.org/CVERecord?id=CVE-2026-67427)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67427) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-31T00:01:11.752089Z"}, {"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"}, {"uuid": "2775eb8f-bb88-4e5a-82a8-4af1b4bdd7cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67429", "type": "seen", "source": "https://gist.github.com/alon710/3970c6098c97c0a550d8b2c18182c3ad", "content": "# CVE-2026-67429: CVE-2026-67429: Arbitrary File Write and Path Traversal in Flyto2 Core Modules\n\n> **CVSS Score:** 10.0\n> **Published:** 2026-07-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67429\n\n## Summary\nCVE-2026-67429 is a critical path traversal vulnerability in Flyto2 Core file-writing modules, including image.download and twelve other modules. By exploiting an insecure validation check that relied on user-controlled parameters, unauthenticated remote attackers can bypass directory confinement and write arbitrary files to the file system, leading to remote code execution.\n\n## TL;DR\nA critical path traversal vulnerability in Flyto2 Core allows unauthenticated remote code execution via arbitrary file write due to caller-controlled base directory validation parameters.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-22, CWE-73\n- **Attack Vector**: Network (AV:N)\n- **CVSS Score**: 10.0 (Critical)\n- **EPSS Score**: 0.00494\n- **Impact**: Arbitrary File Write / Remote Code Execution\n- **Exploit Status**: Proof of Concept (PoC) verified\n- **KEV Status**: Not listed\n\n## Affected Systems\n\n- Flyto2 Core\n- **flyto-core**: < 2.26.6 (Fixed in: `2.26.6`)\n\n## Mitigation\n\n- Upgrade Flyto2 Core to version 2.26.6\n- Define FLYTO_SANDBOX_DIR to restrict write permissions\n- Run Flyto2 Core in an unprivileged, read-only container\n\n**Remediation Steps:**\n1. Identify all active instances of Flyto2 Core in the environment.\n2. Apply the patch by upgrading the PyPI package to version 2.26.6.\n3. Configure the FLYTO_SANDBOX_DIR environment variable to enforce static boundaries.\n4. Audit application logs for suspicious directory overrides in image or document module parameters.\n\n## References\n\n- [GitHub Security Advisory GHSA-2956-977x-2w3r](https://github.com/flytohub/flyto-core/security/advisories/GHSA-2956-977x-2w3r)\n- [Fix Commit d5f89d71303e](https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc)\n- [Release Notes v2.26.6](https://github.com/flytohub/flyto-core/releases/tag/v2.26.6)\n- [CVE-2026-67429 Record](https://www.cve.org/CVERecord?id=CVE-2026-67429)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67429) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-07-31T00:31:48.917307Z"}, {"uuid": "27fae5c1-76ce-4b05-a95f-0a19b09be092", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-67422", "type": "published-proof-of-concept", "source": "https://github.com/facelessuser/pymdown-extensions/security/advisories/GHSA-gm37-52c6-37mw", "content": "", "creation_timestamp": "2026-08-07T21:05:02.574875Z"}, {"uuid": "3f992d8b-c0c0-48ea-b23b-552bc0e99fc2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67422", "type": "seen", "source": "https://gist.github.com/alon710/6f3e0768fc0386f4c965af62333fef78", "content": "# CVE-2026-67422: CVE-2026-67422: Regular Expression Denial of Service in pymdown-extensions\n\n> **CVSS Score:** 7.5\n> **Published:** 2026-08-07\n> **Full Report:** https://cvereports.com/reports/CVE-2026-67422\n\n## Summary\nA high-severity Regular Expression Denial of Service (ReDoS) vulnerability in pymdown-extensions versions prior to 11.0.1 affects the Caret, Tilde, BetterEm, and MagicLink inline processors. When parsing user-supplied Markdown content containing malicious sequences of formatting delimiters, the regular expression engine is forced into catastrophic backtracking, resulting in CPU exhaustion and application denial of service.\n\n## TL;DR\nInefficient regular expressions in multiple inline processors of pymdown-extensions allow unauthenticated attackers to cause complete CPU exhaustion and Denial of Service with short, crafted Markdown payloads of fewer than 50 bytes.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-1333\n- **Attack Vector**: Network\n- **CVSS Score**: 7.5 (High)\n- **EPSS Score**: 0.00582 (Percentile: 44.59%)\n- **Impact**: Denial of Service (CPU Exhaustion)\n- **Exploit Status**: Proof-of-Concept Available\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- Applications rendering Markdown using Python Markdown with the pymdown-extensions library.\n- Static site generators and documentation build pipelines utilizing the BetterEm, Caret, Tilde, or MagicLink extensions.\n- **pymdown-extensions**: < 11.0.1 (Fixed in: `11.0.1`)\n\n## Mitigation\n\n- Upgrade pymdown-extensions to version 11.0.1 or higher.\n- Implement maximum character limits on untrusted Markdown inputs at the application layer.\n- Configure WAF rules to detect and block abnormally long sequences of formatting delimiters.\n\n**Remediation Steps:**\n1. Identify all environments containing the pymdown-extensions package.\n2. Update the dependency using your package manager, for example: pip install --upgrade pymdown-extensions>=11.0.1.\n3. Verify the installed version is 11.0.1 or higher using pip show pymdown-extensions.\n4. Deploy the updated application to production and monitor CPU usage patterns.\n\n## References\n\n- [GitHub Security Advisory GHSA-gm37-52c6-37mw](https://github.com/facelessuser/pymdown-extensions/security/advisories/GHSA-gm37-52c6-37mw)\n- [Patch Commit c684985](https://github.com/facelessuser/pymdown-extensions/commit/c68498598d7b13011bb4571350b6e3612a4ce44b)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-67422) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-08T02:32:35.100867Z"}, {"uuid": "11420815-a22e-4d7d-8aa4-a507ddf5178c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67422", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3msovkh6vgj24", "content": "\ud83d\udfe0 CVE-2026-67422 - High (7.5)\n\npymdown-extensions is a collection of extensions for the Python Markdown library. In versions up ...\n\nhttps://www.thehackerwire.com/vulnerability/CVE-2026-67422/\n\n#infosec #cybersecurity #CVE #vulnerability #security #patchstack", "creation_timestamp": "2026-08-10T01:00:22.263783Z"}, {"uuid": "4d2dee30-c092-4a1f-9633-d9fc7f13b3bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67422", "type": "seen", "source": "https://bsky.app/profile/termsofsurrender.bsky.social/post/3msoxgsu4xc2m", "content": "Another Markdown Hole, Another Marathon Through the Cathedral of Delay\nPANIC 56% | Lag 0.0h | CVE-2026-67422 is a high-severity vulnerability in pymdown-extensions that can expose systems using \n#AfterShockIndex\nREAD MORE", "creation_timestamp": "2026-08-10T01:34:31.551003Z"}, {"uuid": "4ffd1832-2cad-4625-a97f-c6dfce0a7411", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-6742", "type": "seen", "source": "https://bsky.app/profile/atomicedge.bsky.social/post/3mq4v7uy7qi2k", "content": "CVE-2026-6742 advanced-iframe (CVSS Score 6.4) \n\n#WordPress plugin #vulnerability #cybersecurity #wordpressfirewall #hacking #wpsecurity #atomicedge #cybersecurity #malware #vulnerabilityresearch #cve #redteam #proofofconcept", "creation_timestamp": "2026-07-08T10:16:07.873055Z"}, {"uuid": "c954dc1c-a876-4e81-9e97-ac10f793a051", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67426", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mrsoxxxgxn2i", "content": "CVE-2026-67426 - flyto-core\nAn outdated version of Flyto2 Core allows unauthorized access to internal data, potentially exposing sensitive information. This issue is fixed in version 2.26.7, so update to\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#flytocore #flytohub #CVE #infosec", "creation_timestamp": "2026-07-29T19:48:05.685807Z"}, {"uuid": "9b13c4ab-14b6-412c-9053-4fc045d36f35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67429", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mrsp3jcbsn23", "content": "CVE-2026-67429 - flyto-core\nFlyto2 Core, a software used for automation and AI workflows, had a security issue that allowed attackers to write files to any location on the computer. This issue has been\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#flytocore #flytohub #CVE #infosec", "creation_timestamp": "2026-07-29T19:50:04.642248Z"}, {"uuid": "6a20f75e-d0e3-4a1e-b0db-5925a5a216fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67428", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mrspokmwlf2g", "content": "\ud83d\udfe0 CVE-2026-67428 - High (8.5)\n\nFlyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, HTTP-e...\n\nhttps://www.thehackerwire.com/vulnerability/CVE-2026-67428/\n\n#infosec #cybersecurity #CVE #vulnerability #security #patchstack", "creation_timestamp": "2026-07-29T20:00:43.921356Z"}, {"uuid": "4e517408-d243-4ca6-b1f5-5a26e7abc262", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67429", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mrsporaviy2l", "content": "\ud83d\udd34 CVE-2026-67429 - Critical (10)\n\nFlyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, image....\n\nhttps://www.thehackerwire.com/vulnerability/CVE-2026-67429/\n\n#infosec #cybersecurity #CVE #vulnerability #security #patchstack", "creation_timestamp": "2026-07-29T20:00:51.706347Z"}, {"uuid": "6ddb2cca-01da-478d-9314-f6f596e19166", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-67426", "type": "seen", "source": "https://bsky.app/profile/hugovalters.bsky.social/post/3mrt25heosm2u", "content": "CVE-2026-67426 - Critical SSRF in Flyto2 Core. Unauthenticated /run endpoint allows runner secret exfiltration. CVSS 9.3. Update to 2.26.7 immediately. #CVE #infosec #Flyto2\n\nhttps://www.valtersit.com/cve/CVE-2026-67426/", "creation_timestamp": "2026-07-29T23:08:00.842957Z"}]}