CVE-2026-59726: public exploit for this flaw, what we know
CVE-2026-59726 affects CVE-2026-59726; public exploit code is on Exploit-DB. What happened, who is affected, how far exploitation has gone and where the patch stands.
CVE-2026-59726 at a glance
CVE-2026-59726 is a critical-severity OS Command Injection vulnerability in Ruflo, with a CVSS 3.1 base score of 10. NVD published it on 2026-07-09 and classifies the weakness as CWE-78, CWE-306 and CWE-942. Public exploit code: 1 Exploit-DB entry, with the earliest exploit evidence dated 2026-11-11. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 6.24% (percentile 93.6, scored 2026-11-14). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 3 MITRE ATT&CK techniques across Initial Access, Execution, Stealth, Persistence and Privilege Escalation, inferred from the CWE and the description. Its CVERadar threat level is 59/100.
Full CVE-2026-59726 record: exploitation evidence, ATT&CK chain and every source.
What it is
Ruflo is an agent meta-harness for Claude Code and Codex. Prior to 3.16.3, ruflo's default docker-compose deployment exposed the MCP bridge POST /mcp and POST /mcp/:group endpoints without authentication, allowing an unauthenticated network attacker to invoke tools/call to terminal_execute, obtain a shell in the bridge container, read provider API keys, and poison AgentDB learning-store patterns. This issue is fixed in version 3.16.3.
Who's affected
Anyone running CVE-2026-59726. If the service is reachable from the internet, treat it as the priority.
NVD has not published affected version ranges for this CVE yet. Use the vendor advisory in the sources below to confirm which builds are affected.
Exploitation status
- Exploit-DB: EDB-52705 Ruflo MCP Bridge 3.16.2 - Remote Code Execution (2026-11-11).
Risk
- EPSS (probability of exploitation activity in the next 30 days): 3.02%, higher than 88% of all scored CVEs (as of 2026-11-10).
- CVERadar threat level: 58/100 (see methodology).
- Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1059 Command and Scripting Interpreter (inferred); T1078 Valid Accounts (inferred).
Remediation steps
- Find every instance. List where CVE-2026-59726 runs, including test, DR and forgotten internet-facing systems, and record the installed version.
- Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.
- If you can't patch today, apply the vendor's workaround from the advisory, and take the service off the internet or restrict it to a VPN or allow-list until it is patched.
- Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
- Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
- Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.
Detection hints
- T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to the affected service (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-07-09.
- T1059 Command and Scripting Interpreter: Watch for the service process spawning shells or script interpreters.
- T1078 Valid Accounts: Check for logins from new sources or accounts you did not create.
Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.
Sources
- NVD: CVE-2026-59726 nvd.nist.gov/vuln/detail/CVE-2026-59726
- CVE.org record www.cve.org/CVERecord?id=CVE-2026-59726
- FIRST EPSS (2026-11-10) api.first.org/data/v1/epss?cve=CVE-2026-59726
Track every exploited CVE
Full record for CVE-2026-59726, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.