Homepage

flyto-core@2.25.23

The open-source execution engine for AI agents. 468 modules, MCP-native, triggers, queue, versioning, metering.

  • latest version

    2.27.0

  • latest non vulnerable version

    2.27.0

  • first published

    7 months ago

  • latest version published

    15 hours ago

  • licenses detected

  • View flyto-core package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the flyto-core package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Server-side Request Forgery (SSRF)

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the 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/llm inline base_url branch modules, which perform outbound requests to client-controlled URLs without proper validation. An attacker can access sensitive internal resources and potentially obtain cloud metadata credentials or interact with internal APIs by supplying crafted URLs to these modules.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • H
    Server-side Request Forgery (SSRF)

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the http.get, http.request, and http.batch modules when redirects are followed without per-hop revalidation. An attacker can access internal resources and sensitive data by hosting a public URL that redirects to internal addresses, which are then accessed by the affected modules without proper validation.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • H
    External Control of File Name or Path

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to External Control of File Name or Path via the image.download process and other file-writing modules, which allow attacker-controlled parameters for both the output directory and file path. An attacker can write arbitrary files to any location accessible by the process, potentially overwriting sensitive files or introducing malicious code, by supplying crafted parameters and hosting malicious content at a controlled URL.

    How to fix External Control of File Name or Path?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • H
    Protection Mechanism Failure

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Protection Mechanism Failure in the variable resolution process. An attacker can access sensitive environment variables by injecting ${env.VAR} expressions into workflow parameters or step values, which are then resolved without policy checks or allowlists. This allows exfiltration of secrets such as API keys or tokens by embedding them into outbound requests handled by permitted modules.

    How to fix Protection Mechanism Failure?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • H
    Insufficiently Protected Credentials

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Insufficiently Protected Credentials via the base_url parameter in the llm.chat, ai.model, llm.agent, and vector.connector processes. An attacker can obtain sensitive environment-derived API keys by supplying a malicious base_url that causes the application to send authorization headers to an attacker-controlled server.

    How to fix Insufficiently Protected Credentials?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • H
    Server-side Request Forgery (SSRF)

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the run process. An attacker can access internal resources and exfiltrate sensitive internal secrets by sending crafted requests to the exposed endpoint with a controlled callback_url parameter.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade flyto-core to version 2.26.7 or higher.

    [,2.26.7)
    • M
    Server-side Request Forgery (SSRF)

    flyto-core is an A workflow engine with 412 built-in modules. Trace every step. Replay from any point.

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the validate_url_ssrf process. An attacker can access internal or sensitive resources by submitting specially crafted URLs containing IPv6 transition addresses that bypass IP range checks, resulting in the exfiltration of data from internal services.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade flyto-core to version 2.26.3 or higher.

    [,2.26.3)
    Go back to all versions of this package