# Marimo RCE Exploited in Hours: Critical Python Notebook Vulnerability Demands Immediate Patching


A severe remote code execution vulnerability in Marimo, a popular open-source Python notebook environment, has already been actively exploited in the wild within hours of disclosure. Security researchers at Sysdig detected the exploitation attempts targeting the flaw, underscoring the urgency for users to apply patches immediately.


## The Threat


Marimo, which provides an interactive Python environment for data science and computational analysis, contains a critical pre-authentication remote code execution vulnerability that allows attackers to execute arbitrary code on vulnerable systems without requiring valid credentials. The flaw was disclosed publicly on 2026-04-10, and within ten hours, threat actors began leveraging the vulnerability in active attacks—a remarkably fast weaponization timeline that reflects both the severity of the issue and the attacker community's interest in Marimo deployments.


The vulnerability stems from improper handling of user-supplied input, allowing an unauthenticated attacker to craft malicious requests that trigger code execution in the context of the Marimo process. This is particularly dangerous for organizations using Marimo in shared environments, cloud deployments, or accessible development instances. Data scientists and analysts who rely on Marimo for exploratory work may unknowingly expose their systems and data to compromise.


The rapid exploitation timeline is concerning because it indicates that the attack is straightforward to execute and does not require sophisticated techniques or specialized tools. Organizations operating Marimo instances that are reachable from untrusted networks face immediate risk.


## Severity and Impact


| Attribute | Details |

|-----------|---------|

| CVE Identifier | CVE-2026-39987 |

| CVSS v3.1 Score | 9.3 (Critical) |

| Attack Vector | Network |

| Attack Complexity | Low |

| Privileges Required | None |

| User Interaction | None |

| Authentication Required | No |

| CWE Classification | CWE-94 (Improper Control of Generation of Code) |


A CVSS score of 9.3 places this vulnerability in the critical category. The "Network" attack vector means exploitation is possible remotely over standard network protocols. The "Low" attack complexity indicates that no special conditions or detailed knowledge is required to exploit the flaw. Most significantly, the vulnerability requires neither authentication nor user interaction—any unauthenticated attacker can trigger code execution by sending a specially crafted request to a vulnerable Marimo instance.


## Affected Products


The following versions of Marimo are impacted by CVE-2026-39987:


  • Marimo — all versions prior to and including the current release at the time of disclosure

    • - Version 0.1.x through 0.8.x (all versions)

    - Any installation using the affected codebase


    Users operating Marimo in production or development environments should assume their systems are vulnerable unless they have explicitly deployed a patched version.


    ## Mitigations


    ### Immediate Actions


    1. Apply Security Updates: Check the official Marimo repository and release notes for patched versions. Update Marimo to the latest version as soon as a security patch is released.


    2. Network Segmentation: If immediate patching is not possible, restrict network access to Marimo instances using firewall rules. Only allow trusted internal networks to connect to Marimo ports. Do not expose Marimo instances to the public internet or untrusted networks.


    3. Disable Public Access: If Marimo is running on a web-accessible server, disable external access until a patch is available. Use authentication proxies or VPN access to limit who can reach the application.


    4. Monitor for Exploitation: Enable logging on systems running Marimo and look for suspicious HTTP requests or unexpected process execution. Organizations with security monitoring tools should increase alert sensitivity for the Marimo process.


    5. Audit Deployments: Conduct an inventory of all Marimo instances in your environment. Identify which systems are internet-accessible, which contain sensitive data, and which run with elevated privileges. Prioritize patching those with the highest risk profiles.


    ### Long-Term Recommendations


  • Once patches are available, establish a change management process to deploy updates promptly across all affected systems.
  • Implement network-level intrusion detection signatures for CVE-2026-39987 exploitation attempts.
  • Consider running Marimo in containerized or sandboxed environments with restricted system privileges to limit the impact of code execution.
  • Regularly review open-source dependencies for security vulnerabilities and maintain patch management discipline.

    • ## References


  • Marimo GitHub Repository: https://github.com/marimo-team/marimo
  • CVE-2026-39987: https://nvd.nist.gov/vuln/detail/CVE-2026-39987
  • Sysdig Security Research: https://sysdig.com/blog/ (check for detailed technical analysis)
  • CVSS Calculator: https://www.first.org/cvss/calculator/3.1

    • ---


    Recommendation: Organizations using Marimo should treat this as a priority patch. The combination of critical severity, pre-authentication requirements, and active exploitation in the wild makes this a genuine and immediate threat. Deploying fixes should take precedence over normal change management timelines.