{"id":45336,"date":"2026-04-12T22:30:12","date_gmt":"2026-04-12T14:30:12","guid":{"rendered":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/12\/critical-marimo-pre-auth-rce-flaw-now-under-active-exploitation\/"},"modified":"2026-04-12T22:30:12","modified_gmt":"2026-04-12T14:30:12","slug":"critical-marimo-pre-auth-rce-flaw-now-under-active-exploitation","status":"publish","type":"post","link":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/12\/critical-marimo-pre-auth-rce-flaw-now-under-active-exploitation\/","title":{"rendered":"Critical Marimo pre-auth RCE flaw now under active exploitation"},"content":{"rendered":"\n

\"Critical<\/p>\n

Hackers started exploiting a critical vulnerability in the Marimo open-source reactive Python notebook platform just 10 hours after its public disclosure.<\/p>\n

The flaw allows remote code execution without authentication in Marimo versions 0.20.4 and earlier. It tracked as CVE-2026-39987<\/a> and GitHub assessed it with a critical score of 9.3 out of 10.<\/p>\n

According to researchers at cloud-security company Sysdig, attackers created an exploit from the information in the developer’s advisory<\/a> and immediately started using it in attacks that exfiltrated sensitive information.<\/p>\n

\"Critical<\/a> <\/div>\n

Marimo is an open-source<\/a> Python notebook environment, typically used by data scientists, ML\/AI practitioners, researchers, and developers building data apps or dashboards. It is a fairly popular project, with 20,000 GitHub stars and 1,000 forks.<\/p>\n

CVE-2026-39987 is caused by the WebSocket endpoint ‘\/terminal\/ws’ exposing an interactive terminal without proper authentication checks, allowing connections from any unauthenticated client.<\/p>\n

This gives direct access to a full interactive shell, running with the same privileges as the Marimo process.<\/p>\n

Marimo disclosed the flaw on April 8 and yesterday released version 0.23.0<\/a> to address it. The developers noted that the flaw affects users who deployed Marimo as an editable notebook, and those who expose Marimo to a shared network using –host 0.0.0.0 while in edit mode.<\/p>\n

Exploitation in the wild<\/h3>\n

Within the first 12 hours after the vulnerability details were disclosed, 125 IP addresses began reconnaissance activity, according to Sysdig.<\/p>\n

Less than 10 hours after the disclosure, the researchers observed the first exploitation attempt in a credential theft operation.<\/p>\n

The attacker first validated the vulnerability by connecting to the \/terminal\/ws endpoint and executing a short scripted sequence to confirm remote command execution, disconnecting within seconds.<\/p>\n

Shortly after, they reconnected and began manual reconnaissance, issuing basic commands such as pwd, whoami, and ls to understand the environment, followed by directory navigation attempts and checks for SSH-related locations.<\/p>\n

Next, the attacker focused on credential harvesting, immediately targeting the .env file and extracting environment variables, including cloud credentials and application secrets. They then attempted to read additional files in the working directory and continued probing for SSH keys.<\/p>\n

\n
\"Critical
Stealing credentials<\/strong>
Source: Sysdig<\/em><\/figcaption><\/figure>\n<\/div>\n

The entire credential access phase was completed in less than three minutes, notes a Sysdig report<\/a> this week.<\/p>\n

Roughly an hour later, the attacker returned for a second exploitation session using the same exploit sequence.<\/p>\n

The researchers say that behind the attack appears to be a “methodical operator” with a hands-on approach, rather than automated scripts, focusing on high-value objectives such as stealing .env credentials and SSH keys.<\/p>\n

The attackers did not attempt to install persistence, deploy cryptominers, or backdoors, suggesting a quick, stealthy operation.<\/p>\n

Marimo users are recommended to upgrade to version 0.23.0 immediately, monitor WebSocket connections to ‘\/terminal\/ws,’ restrict external access via a firewall, and rotate all exposed secrets.<\/p>\n

If upgrading is not possible, an effective mitigation is to block or disable access to the ‘\/terminal\/ws’ endpoint entirely.<\/p>\n