Voltar ao radar
ANÁLISE DE VULNERABILIDADE

CVE-2026-49869

Kestra OSS OS Command Injection Vulnerability

PRIORIDADE CYBERBOX60MÉDIA
CVSS10.0CRITICAL
EPSS1.9%percentil 78.7
EXPLORAÇÃO ATIVASIM2 de setembro de 2026
PRAZO CISA5 de setembro de 2026referência operacional
VISÃO TÉCNICA

O que sabemos.

Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in Kestra OSS uses request.getPath().endsWith("/configs") to whitelist the public configuration endpoint from Basic Auth. Because the check is a suffix match rather than an exact path match, any API path whose last segment is configs bypasses authentication entirely. An unauthenticated remote attacker can exploit this to create and execute arbitrary workflows without credentials. Because Kestra ships with script execution plugins (plugin-script-shell, plugin-script-python, etc.) enabled by default, this directly results in unauthenticated Remote Code Execution as root inside the Kestra worker container. This vulnerability is fixed in 1.0.45 and 1.3.21.

PUBLICAÇÃO26 de junho de 2026
ÚLTIMA MODIFICAÇÃO3 de setembro de 2026
VETORCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
ORIENTAÇÃO DA FONTE

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Plano de resposta recomendado.

  1. 01

    Trate esta vulnerabilidade como prioridade imediata: há registro de exploração ativa no catálogo KEV.

  2. 02

    Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

  3. 03

    Correlacione indicadores e tentativas de exploração com a telemetria de endpoint, identidade, rede e aplicações.

  4. 04

    Valide a correção com uma nova varredura e registre a evidência de remediação.

CLASSIFICAÇÕES CWECWE-78CWE-184CWE-287CWE-918