CVE-2026-67428

Deferred Deferred - Pending Action

Flyto2 Core SSRF via Unvalidated URL Fetch

Publication date: 2026-07-29

Last updated on: 2026-07-30

Assigner: GitHub, Inc.

Description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, HTTP-emitting modules including src/core/modules/third_party/developer/http/requests.py, core.api.http_get, core.api.http_post, graphql.query, graphql.mutation, monitor.http_check, communication.slack_send, notification.discord.send_message, notification.slack.send_message, notification.teams.send_message, ai.vision_analyze, verify.visual_diff, browser.proxy_rotate, and the agent and llm inline base_url branch fetch caller-controlled URLs without validate_url_with_env_config, allowing SSRF to internal or metadata endpoints. This issue is fixed in version 2.26.7.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-30

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-67428

Affected Vendors & Products

Vendor	Product	Version / Range
flyto2	core	to 2.26.7 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in Flyto2 Core versions before 2.26.7. It allows HTTP-emitting modules to fetch URLs controlled by the attacker without proper validation. The flaw exists in multiple components like HTTP request handlers, API endpoints, GraphQL operations, and messaging integrations.

Detection Guidance

Detecting this SSRF vulnerability requires checking for unvalidated URL fetching in HTTP-emitting modules. Inspect Python files like src/core/modules/third_party/developer/http/requests.py for calls to functions such as http_get, http_post, graphql.query, or monitor.http_check. Look for direct URL handling without validate_url_with_env_config checks.

Impact Analysis

An attacker could exploit this to make the server send requests to internal systems or metadata endpoints, potentially accessing sensitive data, internal services, or cloud provider metadata. This could lead to data breaches, unauthorized access, or service disruption depending on the server's environment.

Compliance Impact

This SSRF vulnerability could violate compliance requirements by enabling unauthorized access to sensitive data or systems. GDPR may be impacted if personal data is exposed, while HIPAA could be violated if protected health information is accessed. Organizations must address this to maintain regulatory compliance.

Mitigation Strategies

Upgrade Flyto2 Core to version 2.26.7 or later immediately. Review all HTTP-emitting modules for URL handling logic and ensure validate_url_with_env_config is enforced. Block internal or metadata endpoint access via network segmentation and firewall rules.

Hi! I’m here to help you understand CVE-2026-67428. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70