CVE-2026-73247

Kestra: SSRF via Pebble http() function allows unauthenticated access to internal services & cloud metadata

Published Aug 11, 2026 CVSS 3.1 · 8.6 High EPSS < 1% KEV · Not listed
Description
Kestra is an open-source, event-driven orchestration platform. Prior to 2.0.0, Kestra's core/src/main/java/io/kestra/core/runners/pebble/functions/HttpFunction.java passes the user-controlled http() uri argument to URI.create() and the server-side HTTP client without restricting private, loopback, or link-local destinations, allowing an unauthenticated attacker to import and execute a flow that accesses internal services or cloud metadata.

Analysis

AI-generated

Technical impact

The vulnerability manifests in the Pebble http() function within Kestra's core code. Prior to version 2.0.0, the function accepts a user‑controlled URI and passes it directly to the URI.create method and the server‑side HTTP client. No validation or restriction is performed to block private, loopback, or link‑local destinations, which allows an unauthenticated attacker to cause the application to request arbitrary internal or cloud‑metadata endpoints.

Affected Systems

Affected systems are instances of the Kestra orchestration platform before version 2.0.0. The product, an open‑source event‑driven workflow engine, is maintained by kestra‑io:kestra. The SSRF flaw exists in all releases released prior to the 2.0.0 milestone, and therefore any deployment running those versions is susceptible.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, yet the EPSS score of <1% suggests that exploitation opportunities are currently rare. The vulnerability is not listed in CISA's KEV catalog. Attackers can trigger the SSRF by creating or importing a flow that invokes the http() function with a crafted URI; because authentication is not required for flow import in the affected builds, the attacker can leverage this vector to reach internal network services or cloud‑metadata endpoints, potentially leaking secrets or executing actions with the application’s permissions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kestra to version 2.0.0 or later to eliminate the unvalidated http() URI handling.
  • If an upgrade is not immediately possible, restrict the http() function or enforce a whitelist of allowed endpoint patterns, and block access to loopback, private, and link‑local addresses at the network or application level.
  • Ensure that any imported or externally supplied flows are authenticated or signed to prevent unauthorized manipulation of the http() function.

Generated by OpenCVE AI on August 12, 2026 at 19:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-r56g-q4p6-m3p6 Kestra: SSRF via Pebble http() function allows unauthenticated access to internal services & cloud metadata
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kestra-io
Kestra-io kestra
Vendors & Products Kestra-io
Kestra-io kestra
Type Values Removed Values Added
Description Kestra is an open-source, event-driven orchestration platform. Prior to 2.0.0, Kestra's core/src/main/java/io/kestra/core/runners/pebble/functions/HttpFunction.java passes the user-controlled http() uri argument to URI.create() and the server-side HTTP client without restricting private, loopback, or link-local destinations, allowing an unauthenticated attacker to import and execute a flow that accesses internal services or cloud metadata.
Title Kestra: SSRF via Pebble http() function allows unauthenticated access to internal services & cloud metadata
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 13, 2026, 2:07 PM
Reserved
Aug 11, 2026, 5:18 PM
Status
Awaiting Analysis
Published
Aug 11, 2026, 10:19 PM
Modified
Oct 24, 2026, 3:10 PM