Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7
Tag: unauthenticated-rce (25 articles)Clear

Ruflo AI agent platform exposed 233 tools through an unauthenticated MCP bridge

Noma Labs found a critical flaw in Ruflo, an open-source platform for orchestrating swarms of AI agents that acts as a harness for coding agents like Claude Code and Codex. Tracked as CVE-2026-59726 and scored 10.0, the flaw is that Ruflo's default Docker deployment exposed its Model Context Protocol bridge to the network with no authentication, offering 233 callable tools. A single unauthenticated request could invoke a shell command tool to run code in the bridge container, read AI provider API keys, steal stored conversations, and poison the platform's persistent agent memory, which can steer future outputs even after the attacker leaves. The flaw is in Ruflo, not in the coding agents.

Check
If you run Ruflo, formerly Claude Flow, update to version 3.16.3 or later, and confirm its MCP bridge is not bound to a network-reachable interface.
Affected
Teams running Ruflo before 3.16.3 with the default Docker deployment (CVE-2026-59726); an unauthenticated network attacker can run commands, steal AI provider keys and conversations, and poison persistent agent memory.
Fix
Update Ruflo, rotate AI provider API keys, rebuild affected containers from clean images, inspect the agent memory store for unfamiliar instructions, and keep MCP bridges bound to loopback and behind authentication.

Unpatched Fastjson flaw lets a single JSON request run code on Spring Boot apps

Security firms ThreatBook and Imperva report attackers targeting a critical flaw in Fastjson, Alibaba's widely used JSON library for Java. On affected Spring Boot applications, a malicious JSON request can execute code without authentication, running with the privileges of the Java process. Tracked as CVE-2026-16723 with an Alibaba-assigned score of 9.0, the confirmed chain needs Fastjson 1.2.68 through 1.2.83, a Spring Boot executable fat-JAR, a network-reachable path that feeds attacker-controlled JSON to the parser, and SafeMode left at its disabled default. Notably, the AutoType feature can stay off and no classpath gadget is required. As of July 25, Alibaba had not shipped a fixed 1.x version.

Check
Inventory Java services for Fastjson 1.x on the classpath, identify any endpoint that parses untrusted JSON, and enable SafeMode now rather than waiting for a fixed release.
Affected
Spring Boot applications packaged as fat-JARs using Fastjson 1.2.68 through 1.2.83 with SafeMode disabled (CVE-2026-16723); an unauthenticated JSON request reaches code execution, and no fixed 1.x version exists yet.
Fix
Enable SafeMode by setting fastjson.parser.safeMode to true, or switch to the noneautotype build, restrict network paths that parse untrusted JSON, and plan migration off Fastjson 1.x.

Cl0p affiliates hit exposed Windchill and FlexPLM through an unauthenticated flaw

Cl0p affiliates are exploiting internet-exposed PTC Windchill and FlexPLM product lifecycle platforms through an unauthenticated remote code execution flaw, in a data theft extortion campaign. Product lifecycle management systems track a product from design to retirement and hold computer-aided design files, bills of materials, engineering data, and workflows, making them a concentrated store of intellectual property for manufacturers in automotive, aerospace, defense, medical, and electronics. Cl0p's established pattern is mass exploitation of one enterprise product followed by extortion over stolen data rather than encryption. PTC patched a critical deserialization flaw in the Windchill data management component earlier this year that has already seen exploitation.

Check
Identify any Windchill or FlexPLM instance reachable from the internet, confirm it is on a patched release, and place it behind access controls rather than leaving it directly exposed.
Affected
Manufacturers running internet-exposed PTC Windchill or FlexPLM; unauthenticated code execution lets Cl0p steal design files, bills of materials, and engineering intellectual property for extortion.
Fix
Patch and restrict access to product lifecycle platforms, require multi-factor authentication, monitor for bulk downloads and unusual export activity, and confirm what intellectual property these systems hold before an incident.

Hugging Face's LeRobot robotics framework has an unpatched flaw that lets remote attackers run code with no authentication (CVE-2026-25874)

Researchers disclosed a critical unauthenticated remote code execution flaw in Hugging Face's LeRobot, the open-source framework used to train and deploy ML models on physical robots. CVE-2026-25874 sits in the framework's web interface, which by default listens on all network interfaces with no authentication - quick for demos, but a hard fail when the demo box ends up on a corporate network. There is no patch yet. Hugging Face has been notified but hasn't released a fix. Particularly serious because LeRobot is usually attached to actual robotic hardware, so a compromise can mean unsafe physical actions.

Check
If your team uses Hugging Face LeRobot anywhere, take the web interface off any reachable network and bind it to localhost-only until a patch is released.
Affected
All current versions of Hugging Face LeRobot with the web interface enabled. CVE-2026-25874, unauthenticated RCE, no patch available. Acute risk for research labs, robotics startups, and university labs running LeRobot demos where the host has any network reachability. Manufacturing or warehouse environments using LeRobot for production robotics are at the highest risk because compromise can drive physical actions.
Fix
Bind LeRobot's web interface to 127.0.0.1 only and tunnel through SSH for remote access. If localhost-only isn't workable, put the interface behind an authenticated reverse proxy (nginx with basic auth, Cloudflare Access, Tailscale). Block direct internet access to any LeRobot host at the firewall. Watch the LeRobot GitHub for the patch. Don't run LeRobot on the same host as production robotic control systems.

Attackers actively exploiting critical unauthenticated file upload flaw in Breeze Cache WordPress plugin on 400,000 sites (CVE-2026-3844)

Wordfence has seen more than 170 live exploit attempts against CVE-2026-3844, a critical unauthenticated arbitrary file upload in the Breeze Cache WordPress plugin from Cloudways. Breeze has roughly 400,000 active installations, making this one of the larger exposure events of the month. The flaw lives in the fetch_gravatar_from_remote function, which fetches avatar images from an arbitrary remote URL and saves them locally without validating the downloaded file's MIME type - so an attacker can point it at a .php payload and drop a webshell directly into a web-accessible directory. The attack is only possible when the 'Host Files Locally - Gravatars' add-on is enabled, which is not the default, but any site that turned it on for performance reasons is wide open. Cloudways shipped the fix as Breeze 2.4.5 earlier this week; as of publication only about 138,000 of the 400,000 installations had downloaded the patched version, leaving hundreds of thousands of sites exposed to a pre-auth RCE with 9.8 CVSS.

Check
Check every WordPress installation you run or manage (including marketing microsites, staff personal sites on corporate subdomains, and legacy tenant sites) for the Breeze Cache plugin and its version.
Affected
Breeze Cache WordPress plugin versions 2.4.4 and earlier, but only when the 'Host Files Locally - Gravatars' sub-feature has been enabled. CVSS 9.8. Discovered by security researcher Hung Nguyen (bashu). If you do not run that sub-feature the plugin is not currently exploitable via this bug, but the fix should still be applied immediately.
Fix
Update Breeze Cache to version 2.4.5 immediately across every site that uses it. If you cannot update straight away, disable the 'Host Files Locally - Gravatars' option or temporarily deactivate the plugin entirely. After patching, hunt the site's wp-content/uploads/cache directory and similar writable paths for recently-created .php files and files with mismatched MIME types, check for new WordPress admin users, and review web server logs for POSTs to the Breeze gravatar endpoint from the exploitation window. Confirm no webshell has been planted before declaring the site clean.