CVE-2026-73247
Unauthenticated SSRF in Kestra http() lets attackers reach internal/cloud metadata.
Is CVE-2026-73247 being exploited?
Not confirmed. CVE-2026-73247 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-73247?
CVE-2026-73247 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73247?
Yes. A fix has been recorded for CVE-2026-73247. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73247 affect?
CVE-2026-73247 affects Kestra < 2.0.0, Self-hosted Kestra servers, Kubernetes deployments running Kestra. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73247?
Upgrade to Kestra 2.0.0 and restrict outbound egress to metadata/internal IPs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SSRF via http() allowing access to internal services and cloud metadata; may lead to credential theft and RCE by importing malicious flows.
Immediate action required
- affected< 2.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.