Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| flytohub | flyto-core | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Flytohub | Flyto-core |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c9hr-64h3-gxpc | Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.293% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Flytohub
Flytohub flyto-core |
|
| Vendors & Products |
Flytohub
Flytohub flyto-core |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, the HTTP modules http.get, http.request, and http.batch in src/core/modules/atomic/http/get.py, src/core/modules/atomic/http/request.py, and src/core/modules/atomic/http/batch.py validate only the initial URL, then follow redirects with allow_redirects=True and without per-hop Location revalidation, allowing a public URL to redirect into internal address space and return the internal response body. This issue is fixed in version 2.26.7. | |
| Title | Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|