Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

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

CVE-2026-73247GHSA-r56g-q4p6-m3p6

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven io.kestra:kestra-core

    Affected
    < 2.0.0
    Fixed in
    2.0.0

  • Maven io.kestra:core

    Affected
    <= 1.3.31
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-73247: 0.41% estimated exploitation activity in the next 30 days; percentile 34.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The Pebble template engine's http() function in Kestra OSS accepts user-controlled URLs without any validation, allowing Server-Side Request Forgery (SSRF) attacks. An unauthenticated attacker can import a malicious Flow YAML and execute it to access internal services, cloud metadata endpoints (AWS 169.254.169.254), or localhost services. The vulnerability affects all Kestra OSS deployments with default configuration. Details The root cause is in core/src/main/java/io/kestra/core/runners/pebble/functions/HttpFunction.java (lines 77-106): 1. No URL validation: User input is passed directly to URI.create() with no checks for private IPs, internal hosts, or restricted schemes 2. No IP filtering: Missing checks for 10.0.0.0/8, 192.168.0.0/16, 169.254.169.254, 127.0.0.1 3. No scheme restriction: file://, gopher:// schemes are not blocked 4. No authentication required: TenantValidationFilter.java only checks tenant == "main" — no authentication 5. Unconditional registration:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-r56g-q4p6-m3p6

  2. Revision 1 · created ·

    Published from osv record GHSA-r56g-q4p6-m3p6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73247

Advisory: Kestra: SSRF via Pebble http() function allows unauthenticated access to internal services & cloud metadata
IDs: CVE-2026-73247, GHSA-r56g-q4p6-m3p6
Record: https://patchnext.com/advisories/cve-2026-73247 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: io.kestra:kestra-core 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.kestra:kestra-core: affected < 2.0.0; fixed in 2.0.0
- Maven io.kestra:core: affected <= 1.3.31

## Suggested inspection (read-only)
- Maven io.kestra:kestra-core: check the installed version with your package manager.
- Maven io.kestra:core: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.kestra:kestra-core, io.kestra:core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r56g-q4p6-m3p6 (OSV record GHSA-r56g-q4p6-m3p6 lists affected ranges: Maven io.kestra:core >=0 =0 <2.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-r56g-q4p6-m3p6 (GitHub-reviewed advisory GHSA-r56g-q4p6-m3p6 lists affected ranges: Maven io.kestra:core >=0 =0 <2.0.0)

Commands are suggestions: review each one before running it.

Loading voting…