CriticalCVE-2026-39987

    marimo Affected by Pre-Auth Remote Code Execution via Terminal WebSocket Authentication Bypass (CVE-2026-39987)

    Published In CISA KEV since Sources: CVE.org, OSV

    What is affected, what to do

    marimo is a reactive Python notebook. Prior to 0.23.0, Marimo has a Pre-Auth RCE vulnerability.

    The vulnerability is being actively exploited; treat it as a priority. Update Marimo to version 0.23.0. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Marimo lt *..0.23.0
    Fixed in
    • Marimo 0.23.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, OSV

    99.56 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.95

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    245.01 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.56 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.95
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-306

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable without authentication or user interaction and hands the attacker an interactive shell directly — exploitation needs nothing more than a WebSocket client, which places it among the CVEs with a very high likelihood of exploitation. Typical targets are data-science and ML environments, research servers and hastily provisioned cloud VMs running marimo in edit mode on an open interface; these hosts often carry privileged cloud and database credentials, making the bug a launch point for data theft, cryptomining and lateral movement. CISA does not flag known ransomware use, but that does not lower the severity: treat any unpatched instance reachable from untrusted networks as an emergency (fix within hours), and localhost-only developer installs as a near-term item in the regular patch cycle.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Locate every marimo deployment — pip show marimo / pip list | grep -i marimo across venvs, containers and shared notebook servers, plus a network sweep for marimo's default port 2718 (unless overridden via --port). Edit-mode instances (marimo edit) are the primary concern, since /terminal/ws only checks run mode and platform support before accepting a connection.
      • Patch: Upgrade to marimo 0.23.0 or later (pip install --upgrade "marimo>=0.23.0"), rebuild container images and restart running processes. All versions prior to 0.23.0 are affected.
      • Cut exposure now: Stop any marimo server reachable from the internet or from user VLANs until patched, or restrict it via host firewall to 127.0.0.1 or an admin network. Never bind to 0.0.0.0 (--host 0.0.0.0) without an authenticating proxy in front.
      • Compromise assessment: For every exposed instance, review web server/proxy logs for requests to /terminal/ws. Any hit from an unknown source IP means treat the host as compromised: isolate it and preserve evidence (memory image, shell history, /tmp, crontabs, ~/.ssh/authorized_keys).
      • Rotate credentials: Notebook hosts routinely hold cloud keys, database passwords and API tokens (environment variables, .env, ~/.aws/credentials, ~/.config). For every exposed, unpatched instance, rotate all secrets reachable from that host — whether or not access has been confirmed.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Move data-science/notebook hosts into a dedicated segment; allow inbound access to port 2718 (or the configured port) only via jump host or VPN. Restrict egress to required package repositories and data sources to frustrate reverse shells and exfiltration.
      • Reverse proxy/WAF: Front marimo with a reverse proxy (nginx, Traefik, Envoy) enforcing authentication (OIDC/SSO, mTLS). Until patched, hard-block WebSocket upgrades on /terminal/ws, e.g. nginx: location ^~ /terminal/ws { return 403; }.
      • IPS rule: Suricata/Snort signature matching HTTP requests with URI /terminal/ws and Upgrade: websocket towards notebook segments from non-approved source networks — alert everywhere, block where inline.
      • Endpoint hardening: Run marimo as a dedicated unprivileged service account with no sudo and no Docker socket access; in containers use --read-only, never --privileged, and drop capabilities. Serve production apps with marimo run rather than marimo edit.
      • IAM/least privilege: Provision only short-lived, narrowly scoped credentials on notebook hosts (workload identity, time-bound STS tokens) instead of long-lived admin keys.
    3. Runbook step 3

      Detection rules

      • Web/proxy logs: Requests to /terminal/ws returning HTTP 101 (Switching Protocols) from source IPs outside the allowlist. SPL: index=proxy uri_path="/terminal/ws" status=101 NOT src_ip IN (<admin_nets>) | stats count by src_ip, dest, _time.
      • Network telemetry (Zeek/Suricata): Zeek http.log entries with uri == "/terminal/ws" and an upgrade header, or websocket.log sessions to notebook hosts; correlate with new outbound connections from those hosts to unfamiliar IPs (e.g. 4444, 1337, 443) shortly after the WebSocket handshake.
      • Process ancestry (EDR, Sysmon for Linux EID 1, auditd execve): python/marimo → bash/sh → curl, wget, nc, base64, chmod +x, python -c. Sigma shape: ParentImage|endswith: '/python3' AND ParentCommandLine|contains: 'marimo' AND Image|endswith: ['/curl','/wget','/nc','/bash']. Legitimate terminal use by data scientists produces the same chain — correlate with the WebSocket source IP.
      • Persistence and credential access: auditd watches (-w ~/.ssh/authorized_keys -p wa, -w /etc/crontab -p wa) plus reads of ~/.aws/credentials, .env files and /proc/*/environ by shell children of the marimo service.
      • Cloud audit logs: API calls using the notebook host's credentials from foreign source IPs, or unusual calls such as GetCallerIdentity, ListBuckets, or new IAM key creation (CloudTrail, Azure Activity Log, GCP Audit Logs).

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    marimo is a reactive Python notebook. Prior to 0.23.0, Marimo has a Pre-Auth RCE vulnerability. The terminal WebSocket endpoint /terminal/ws lacks authentication validation, allowing an unauthenticated attacker to obtain a full PTY shell and execute arbitrary system commands. Unlike other WebSocket endpoints (e.g., /ws) that correctly call validate_auth() for authentication, the /terminal/ws endpoint only checks the running mode and platform support before accepting connections, completely skipping authentication verification. This vulnerability is fixed in 0.23.0.

    Source: NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    marimo-teammarimo
    • < 0.23.0
    • 0.23.0
    coreweavemarimo
    • < 0.23.0
    • 0.23.0
    pypimarimo
    • 0.1.40
    • 0.3.11
    • 0.10.12
    • 0.7.14
    • 0.6.18
    • 0.7.10
    • 0.19.9
    • 0.10.18
    • 0.8.21
    • 0.6.14
    • 0.1.7
    • 0.1.26
    • 0.8.10
    • 0.1.87
    • 0.4.11
    • 0.8.1
    • 0.13.8
    • 0.1.78
    • 0.1.33
    • 0.9.32
    • 0.11.11
    • 0.1.79
    • 0.16.0
    • 0.7.20
    • 0.2.8
    • 0.1.5
    • 0.1.1
    • 0.18.2
    • 0.6.12
    • 0.9.25
    • 0.9.10
    • 0.11.29
    • 0.3.10
    • 0.1.88
    • 0.12.7
    • 0.1.58
    • 0.9.13
    • 0.13.2
    • 0.11.24
    • 0.6.15
    • 0.18.0
    • 0.11.3
    • 0.14.4
    • 0.11.2
    • 0.9.11
    • 0.11.28
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-306Missing Authentication for Critical Function

      Base

      The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

      Entry at MITRE CWE-306

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Reference tagged as exploitgithub.com (opens in a new tab)PoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)CVE-2026-39987-Marimo-RCE (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987-Marimo-Preauth-RCE (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987_POC (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cohort-htb (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987-PoC (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987.py (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cve-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987-Poc (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987_PoC (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-39987-POC (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • github.commarimo-team/marimo/security/advisories/GHSA-2679-6mx9-h9xcweb, x_refsource_CONFIRM, Exploit, Mitigation, Vendor advisory
    • NVD (NIST)vuln/detail/CVE-2026-39987advisory
    • github.commarimo-team/marimo/pull/9098web, x_refsource_MISC, Issue tracking, Patch
    • github.commarimo-team/marimo/commit/c24d4806398f30be6b12acd6c60d1d7c68cfd…web, x_refsource_MISC, Patch
    • github.commarimo-team/marimopackage
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39987web
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-39987web, government-resource, US government resource
    • sysdig.comblog/marimo-oss-python-notebook-rce-from-disclosure-to-exploita…web, Third-party advisory, Exploit, Third-party advisory
    • pypi.orgproject/marimopackage
    • GitHub Security Advisoriesadvisories/GHSA-2679-6mx9-h9xcadvisory

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-39987
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-39987"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-39987.svg?lang=en" alt="CVE-2026-39987 – NEOSEC Intel" height="20"></a>