Authenticated SSRF via unguarded outbound request modules
Published Jul 29, 2026 · Updated Jul 29, 2026
Server-side request forgery in Flyto2 Core before 2.26.7 allows remote authenticated users to access internal services via crafted URLs. Multiple HTTP-emitting modules issue outbound requests to caller-controlled destinations without invoking validate_url_with_env_config and return response bodies. Workflow-author credentials are required; exploitation can read cloud metadata and internal responses or send requests to internal APIs.
Summary
What happened
Server-side request forgery in Flyto2 Core before 2.26.7 allows remote authenticated users to access internal services via crafted URLs. Multiple HTTP-emitting modules issue outbound requests to caller-controlled destinations without invoking validate_url_with_env_config and return response bodies. Workflow-author credentials are required; exploitation can read cloud metadata and internal responses or send requests to internal APIs.
The record
- CVE
- CVE-2026-67428
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Flyto2
- Product
- Flyto2 Core
- Classifications
- CWE-918, CAPEC-664, T1552.005, T1090
- Attack vector
- network
- Privileges
- authenticated
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.7
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-pgwh-4jj4-qm8v authenticated MCP proof of conceptfunctional · 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