CVE-2026-39987Active Exploitation(coreweave / marimo)

CRITICALCVSS 9.8 · CRITICALCISA KEV

Exploitation observed; activity peaked at 27 mentions and remains active

Immediate actions

  • Patch coreweave marimo systems immediately
  • Assume compromise if assets are exposed
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: Immediate (within 24h)

NVD 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.

9.0/ 10 priority

Sources & remediation

Listed in the CISA Known Exploited Vulnerabilities catalog. Federal remediation due date: 2026-05-07. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Weakness type (CWE)
CWE-306

Priority

CRITICAL

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

DECLINING

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • marimo

Threat summary

  • Active exploitation appears in 210 classified signals
  • Public PoC and exploit tooling are both present
  • Patch or workaround signal is available
  • 275 mentions across 58 observed days

What's happening

  • Active exploitation reported across 210 signals
  • Exploit tool or code specified in 19 signals
  • PoC mentioned or linked in 25 signals
  • Patch or workaround mentioned in 55 signals
  • Technical details provided in 166 signals
  • Disclosure: 31 classified signals
  • General: 16 classified signals
  • Peaked 56d ago at 27 mentions (2026-04-10); latest day: 3
  • 275 total mentions across 58 days

Affected systems

Vendors
Products
marimo

Deep dive

Activity timeline275 mentions / 58d
07142027Mentions · 2026-04-09: 4Mentions · 2026-04-10: 27Mentions · 2026-04-11: 18Mentions · 2026-04-12: 14Mentions · 2026-04-13: 17Mentions · 2026-04-14: 4Mentions · 2026-04-15: 5Mentions · 2026-04-16: 6Mentions · 2026-04-17: 8Mentions · 2026-04-18: 7Mentions · 2026-04-19: 2Mentions · 2026-04-20: 5Mentions · 2026-04-21: 1Mentions · 2026-04-22: 1Mentions · 2026-04-23: 5Mentions · 2026-04-24: 9Mentions · 2026-04-25: 2Mentions · 2026-04-28: 2Mentions · 2026-04-29: 3Mentions · 2026-04-30: 3Mentions · 2026-05-13: 1Mentions · 2026-05-15: 3Mentions · 2026-05-17: 1Mentions · 2026-05-18: 3Mentions · 2026-05-25: 1Mentions · 2026-05-26: 2Mentions · 2026-05-28: 2Mentions · 2026-05-29: 19Mentions · 2026-05-30: 15Mentions · 2026-05-31: 6Mentions · 2026-06-01: 6Mentions · 2026-06-02: 3Mentions · 2026-06-03: 1Mentions · 2026-06-04: 17Mentions · 2026-06-05: 2Mentions · 2026-06-06: 1Mentions · 2026-06-08: 2Mentions · 2026-06-09: 3Mentions · 2026-06-12: 3Mentions · 2026-06-16: 3Mentions · 2026-06-18: 5Mentions · 2026-06-22: 1Mentions · 2026-07-09: 1Mentions · 2026-07-19: 2Mentions · 2026-08-02: 1Mentions · 2026-08-16: 1Mentions · 2026-08-29: 1Mentions · 2026-09-11: 2Mentions · 2026-09-12: 4Mentions · 2026-09-13: 1Mentions · 2026-09-14: 1Mentions · 2026-09-15: 8Mentions · 2026-09-16: 1Mentions · 2026-09-17: 3Mentions · 2026-09-18: 1Mentions · 2026-09-24: 1Mentions · 2026-10-02: 1Mentions · 2026-10-07: 3PoC Mentioned / Linked · 2026-04-09: 1PoC Mentioned / Linked · 2026-04-10: 3PoC Mentioned / Linked · 2026-04-11: 1PoC Mentioned / Linked · 2026-04-12: 1PoC Mentioned / Linked · 2026-04-13: 1PoC Mentioned / Linked · 2026-04-15: 1PoC Mentioned / Linked · 2026-04-18: 1PoC Mentioned / Linked · 2026-04-20: 1PoC Mentioned / Linked · 2026-04-24: 1PoC Mentioned / Linked · 2026-04-25: 1PoC Mentioned / Linked · 2026-04-28: 1PoC Mentioned / Linked · 2026-05-15: 1PoC Mentioned / Linked · 2026-05-26: 1PoC Mentioned / Linked · 2026-05-29: 1PoC Mentioned / Linked · 2026-05-30: 2PoC Mentioned / Linked · 2026-05-31: 2PoC Mentioned / Linked · 2026-06-01: 1PoC Mentioned / Linked · 2026-06-16: 1PoC Mentioned / Linked · 2026-09-12: 1PoC Mentioned / Linked · 2026-09-17: 1PoC Mentioned / Linked · 2026-09-18: 1Exploit Tool / Code · 2026-04-12: 2Exploit Tool / Code · 2026-04-15: 1Exploit Tool / Code · 2026-04-17: 1Exploit Tool / Code · 2026-04-18: 1Exploit Tool / Code · 2026-04-24: 2Exploit Tool / Code · 2026-05-29: 4Exploit Tool / Code · 2026-05-30: 2Exploit Tool / Code · 2026-06-01: 1Exploit Tool / Code · 2026-06-16: 1Exploit Tool / Code · 2026-09-12: 1Exploit Tool / Code · 2026-09-15: 2Exploit Tool / Code · 2026-09-17: 1Active Exploitation · 2026-04-09: 1Active Exploitation · 2026-04-10: 27Active Exploitation · 2026-04-11: 16Active Exploitation · 2026-04-12: 14Active Exploitation · 2026-04-13: 15Active Exploitation · 2026-04-14: 3Active Exploitation · 2026-04-15: 5Active Exploitation · 2026-04-16: 6Active Exploitation · 2026-04-17: 8Active Exploitation · 2026-04-18: 6Active Exploitation · 2026-04-19: 1Active Exploitation · 2026-04-20: 1Active Exploitation · 2026-04-21: 1Active Exploitation · 2026-04-22: 1Active Exploitation · 2026-04-23: 4Active Exploitation · 2026-04-24: 5Active Exploitation · 2026-04-25: 2Active Exploitation · 2026-04-28: 2Active Exploitation · 2026-04-29: 1Active Exploitation · 2026-05-15: 3Active Exploitation · 2026-05-26: 2Active Exploitation · 2026-05-28: 2Active Exploitation · 2026-05-29: 15Active Exploitation · 2026-05-30: 13Active Exploitation · 2026-05-31: 6Active Exploitation · 2026-06-01: 5Active Exploitation · 2026-06-02: 3Active Exploitation · 2026-06-03: 1Active Exploitation · 2026-06-04: 15Active Exploitation · 2026-06-05: 1Active Exploitation · 2026-06-06: 1Active Exploitation · 2026-06-08: 2Active Exploitation · 2026-06-09: 3Active Exploitation · 2026-06-12: 2Active Exploitation · 2026-06-16: 1Active Exploitation · 2026-06-18: 2Active Exploitation · 2026-07-09: 1Active Exploitation · 2026-08-02: 1Active Exploitation · 2026-08-29: 1Active Exploitation · 2026-09-11: 1Active Exploitation · 2026-09-14: 1Active Exploitation · 2026-09-15: 5Active Exploitation · 2026-09-16: 1Active Exploitation · 2026-09-17: 2Active Exploitation · 2026-09-24: 1Patch / Workaround · 2026-04-09: 2Patch / Workaround · 2026-04-10: 7Patch / Workaround · 2026-04-11: 6Patch / Workaround · 2026-04-12: 1Patch / Workaround · 2026-04-13: 6Patch / Workaround · 2026-04-14: 3Patch / Workaround · 2026-04-15: 2Patch / Workaround · 2026-04-16: 2Patch / Workaround · 2026-04-17: 3Patch / Workaround · 2026-04-18: 2Patch / Workaround · 2026-04-20: 1Patch / Workaround · 2026-04-23: 1Patch / Workaround · 2026-04-24: 1Patch / Workaround · 2026-04-28: 1Patch / Workaround · 2026-05-18: 1Patch / Workaround · 2026-05-25: 1Patch / Workaround · 2026-05-30: 4Patch / Workaround · 2026-06-02: 2Patch / Workaround · 2026-06-12: 1Patch / Workaround · 2026-06-16: 1Patch / Workaround · 2026-07-19: 1Patch / Workaround · 2026-09-11: 1Patch / Workaround · 2026-09-14: 1Patch / Workaround · 2026-09-15: 3Patch / Workaround · 2026-09-24: 1Technical Details · 2026-04-09: 4Technical Details · 2026-04-10: 24Technical Details · 2026-04-11: 12Technical Details · 2026-04-12: 13Technical Details · 2026-04-13: 15Technical Details · 2026-04-14: 4Technical Details · 2026-04-15: 5Technical Details · 2026-04-16: 3Technical Details · 2026-04-17: 3Technical Details · 2026-04-18: 2Technical Details · 2026-04-19: 2Technical Details · 2026-04-20: 5Technical Details · 2026-04-23: 5Technical Details · 2026-04-24: 6Technical Details · 2026-04-25: 2Technical Details · 2026-04-28: 2Technical Details · 2026-04-29: 2Technical Details · 2026-04-30: 1Technical Details · 2026-05-13: 1Technical Details · 2026-05-17: 1Technical Details · 2026-05-18: 3Technical Details · 2026-05-25: 1Technical Details · 2026-05-26: 1Technical Details · 2026-05-28: 2Technical Details · 2026-05-29: 4Technical Details · 2026-05-30: 7Technical Details · 2026-05-31: 1Technical Details · 2026-06-01: 1Technical Details · 2026-06-02: 2Technical Details · 2026-06-04: 5Technical Details · 2026-06-06: 1Technical Details · 2026-06-09: 1Technical Details · 2026-06-12: 2Technical Details · 2026-06-16: 3Technical Details · 2026-06-18: 4Technical Details · 2026-07-09: 1Technical Details · 2026-07-19: 2Technical Details · 2026-08-29: 1Technical Details · 2026-09-11: 1Technical Details · 2026-09-12: 1Technical Details · 2026-09-14: 1Technical Details · 2026-09-15: 5Technical Details · 2026-09-16: 1Technical Details · 2026-09-17: 2Technical Details · 2026-09-24: 104-0904-1404-1904-2405-1305-2606-0106-0606-1808-1609-1409-2410-07
Signal classification6 categories
Active Exploitation
20876.8%
Disclosure
3111.4%
General
165.9%
Patch
124.4%
Exploit
31.1%
PoC
10.4%
Referenced assets170 URLs
By indicator
Classification over time
DateTotalLabels
2026-04-094
Active Exploitation1Disclosure2Patch1
2026-04-1027
Active Exploitation26Patch1
2026-04-1118
Active Exploitation16Disclosure2
2026-04-1214
Active Exploitation14
2026-04-1317
Active Exploitation15Disclosure1Patch1
2026-04-144
Active Exploitation3Patch1
2026-04-155
Active Exploitation5
2026-04-166
Active Exploitation6
2026-04-178
Active Exploitation8
2026-04-187
Active Exploitation6Disclosure1
2026-04-192
Active Exploitation1Disclosure1
2026-04-205
Active Exploitation1Disclosure3Patch1
2026-04-211
Active Exploitation1
2026-04-221
Active Exploitation1
2026-04-235
Active Exploitation4Disclosure1
2026-04-249
Active Exploitation5Disclosure3General1
2026-04-252
Active Exploitation2
2026-04-282
Active Exploitation2
2026-04-293
Active Exploitation1General1Patch1
2026-04-303
Disclosure1General2
2026-05-131
Patch1
2026-05-153
Active Exploitation3
2026-05-171
Disclosure1
2026-05-183
Disclosure3
2026-05-251
Patch1
2026-05-262
Active Exploitation2
2026-05-282
Active Exploitation2
2026-05-2919
Active Exploitation15Disclosure3General1
2026-05-3015
Active Exploitation13Disclosure1General1
2026-05-316
Active Exploitation6
2026-06-016
Active Exploitation5General1
2026-06-023
Active Exploitation3
2026-06-031
Active Exploitation1
2026-06-0417
Active Exploitation15Disclosure1General1
2026-06-052
Active Exploitation1General1
2026-06-061
Active Exploitation1
2026-06-082
Active Exploitation2
2026-06-093
Active Exploitation3
2026-06-123
Active Exploitation1Disclosure1Patch1
2026-06-163
Active Exploitation1Exploit1Patch1
2026-06-185
Active Exploitation2Disclosure2General1
2026-06-221
General1
2026-07-091
Active Exploitation1
2026-07-192
Disclosure1Patch1
2026-08-021
Active Exploitation1
2026-08-161
General1
2026-08-291
Active Exploitation1
2026-09-112
Active Exploitation1General1
2026-09-124
Disclosure1Exploit1General2
2026-09-131
Disclosure1
2026-09-141
Active Exploitation1
2026-09-158
Active Exploitation5Disclosure1General1Patch1
2026-09-161
Active Exploitation1
2026-09-173
Active Exploitation2Exploit1
2026-09-181
PoC1
2026-09-241
Active Exploitation1
Full discourse20 posts
  • Rishi@rxerium
    Active Exploitation

    🚨 Pre-Auth RCE vuln tagged as CVE-2026-39987 (CVSS 9.3) seeing active exploitation in the wild as reported by Vulncheck and Bleeping Computer. Passively scan infrastructure to find potentially vulnerable instances: https://github.com/rxerium/rxerium-templates/blob/main/2026/CVE-2026-39987.yaml An unauthenticated attacker can obtain a full interactive root shell on the server via a single WebSocket connection. No user interaction or authentication token is required, even when authentication is enabled on the marimo instance. Patched version is 0.23.0 as per the advisory: https://github.com/marimo-team/marimo/security/advisories/GHSA-2679-6mx9-h9xc

    Post summary

    The post confirms that CVE-2026-39987, a pre‑authentication RCE via WebSocket, is actively being exploited in the wild, offers a scanning resource, and references the patch version and advisory.

    878239526236.9K
    3.8K followersView on X
  • NullSecurityX@NullSecurityX
    Disclosure

    A pre-auth attacker can open a single WebSocket connection and obtain a fully interactive root shell. Due to missing auth checks in the handler, marimo exposes RCE without tokens or user interaction, even when auth is enabled. CVE-2026-39987 https://t.co/OVdAYcTCmn

    Post summary

    The post reveals a pre‑authentication WebSocket‑based RCE in marimo that yields a root shell, but does not mention a PoC link, exploit code, or active attacks, and no patch or mitigation is discussed.

    231025512417.9K
    12.3K followersView on X
  • The Hacker News@TheHackersNews
    Active Exploitation

    ⚠️ Attackers used an LLM agent for post-exploitation after breaching a public Marimo notebook via CVE-2026-39987, a pre-auth RCE flaw affecting versions ≤0.20.4. The intrusion stole cloud credentials, retrieved an SSH key from AWS Secrets Manager, and exfiltrated a PostgreSQL database via eight SSH sessions in under two minutes. Full report: https://thehackernews.com/2026/05/attackers-use-llm-agent-for-post.html

    Post summary

    Attackers leveraged CVE‑2026‑39987, a pre‑auth RCE in Marimo notebooks, to exfiltrate credentials and database data using an LLM agent, demonstrating active exploitation in the wild.

    6210691011.7K
    1.9M followersView on X
  • The Hacker News@TheHackersNews
    Active Exploitation

    ⚠️ Marimo CVE-2026-39987 gave attackers a full shell with no authentication. A missing check in /terminal/ws allowed remote code execution on exposed systems. Exploitation began within 9 hours of disclosure—no PoC needed. 🔗 Details here → https://thehackernews.com/2026/04/marimo-rce-flaw-cve-2026-39987.html

    Post summary

    CVE-2026-39987 in Marimo enables unauthenticated RCE, with exploitation reported within hours of disclosure and no PoC or patch details provided.

    2153481310.9K
    1.7M followersView on X
  • 秋风@q1uf3ng
    Patch

    CVE+++ CVE-2026-39987 @marimo_io Super fast response, great to work with. https://marimo-team.notion.site/Security-Release-CWE-306-Remote-Code-Execution-via-Terminal-WebSocket-Authentication-Bypass-33cdbf71a058806fa9b5e1fc5d72fb25 https://t.co/PtReG7gcv1

    Post summary

    The tweet references CVE-2026-39987 and links to a vendor security release that provides patch details and technical information, but no PoC, exploit code, or active exploitation is mentioned.

    24147811.7K
    2.2K followersView on X
  • CISA Cyber@CISACyber
    Active Exploitation

    🛡️ We added Marimo remote code execution vulnerability CVE-2026-39987 to our Known Exploited Vulnerabilities Catalog. Visit https://go.dhs.gov/Z3Q for more information. https://t.co/QZuPkWv5RE

    Post summary

    The tweet announces that CVE-2026-39987, a remote code execution flaw in Marimo, has been added to the Known Exploited Vulnerabilities Catalog, indicating it is being actively exploited, but it offers minimal technical or mitigation details.

    61423037.1K
    299.5K followersView on X
  • Dark Web Informer@DarkWebInformer
    Disclosure

    ‼️Root in One Request: Pre-Auth RCE in Marimo (CVE-2026-39987) https://darkwebinformer.com/root-in-one-request-pre-auth-rce-in-marimo-cve-2026-39987/

    Post summary

    A new pre‑authenticated remote code execution vulnerability (CVE‑2026‑39987) in Marimo has been disclosed, with basic type details but no exploit code, patch, or evidence of active exploitation.

    0603475.6K
    223.7K followersView on X
  • yousukezan@yousukezan
    Active Exploitation

    オープンソースのPythonノート環境Marimoに致命的脆弱性が発覚し、公表からわずか10時間以内に実際の攻撃が確認された。認証不要で遠隔操作が可能な深刻な問題である。 問題はCVE-2026-39987(CVSS 9.3)で、0.20.4までの全バージョンに影響する。原因は/terminal/wsのWebSocketエンドポイントに認証検証がなく、攻撃者が資格情報なしで接続しフル機能のシェルを取得できる点にある。本来必要なvalidate_auth()が呼ばれず、動作モード確認のみで接続が許可されていた。Sysdigの観測では公開後9時間41分で攻撃が始まり、攻撃者は即座に.envファイルやSSH鍵の探索を実施した。活動は人手による操作とみられ、複数回接続しながら情報収集を進めていた。修正は0.23.0で提供済みだが、公開直後から悪用される現実が改めて示された。 https://thehackernews.com/2026/04/marimo-rce-flaw-cve-2026-39987.html

    Post summary

    CVE-2026-39987 in Marimo caused unauthenticated remote code execution actively exploited within 10 hours of disclosure, and a patch (v0.23.0) is available for the vulnerability.

    01301783.2K
    14.3K followersView on X
  • OrcaRouter 🐳@OrcaRouter
    Active Exploitation

    That was EchoLeak. And the 2026 leak wall is worse: • Chat & Ask AI — 300M private messages from 25M users, wide open (Firebase misconfig) • Sears — 3.7M AI chat logs + call recordings exposed • marimo (CVE-2026-39987) — an AI agent went from one CVE to dumping an entire internal database in under 2 minutes

    Post summary

    The tweet reports that the marimo CVE‑2026‑39987 was used in the wild, enabling an AI agent to extract a complete internal database within two minutes.

    1201975.3K
    11.9K followersView on X
  • Florian Hansemann@CyberWarship
    Disclosure

    ''Resecurity | Marimo Pre-Auth RCE via Unauthenticated WebSocket Terminal (CVE-2026-39987)'' #infosec #pentest #redteam #blueteam https://www.resecurity.com/blog/article/marimo-pre-auth-rce-via-unauthenticated-websocket-terminal-cve-2026-39987

    Post summary

    A blog post announces a new pre‑authentication RCE vulnerability in Marimo accessed through an unauthenticated WebSocket terminal, detailing the exploit vector but not yet reporting any active exploitation or available patch.

    1401473.5K
    88.5K followersView on X
  • Gray Hats@the_yellow_fall
    Active Exploitation

    Unauthenticated RCE in marimo (CVE-2026-39987) exploited in the wild in record time. Attackers gained root access in under 10 hours. Patch to v0.23.0 now! #marimo #PythonSecurity #RCE #InfoSec #CVE202639987 #ZeroDay https://securityonline.info/marimo-terminal-rce-cve-2026-39987-exploited-in-wild/ https://t.co/RhZGDcSswI

    Post summary

    CVE‑2026‑39987 was actively exploited, granting attackers root in under 10 hours, and a patch (v0.23.0) is now available.

    240172995
    12.3K followersView on X
  • Gray Hats@the_yellow_fall
    Active Exploitation

    Analyze the Marimo CVE-2026-39987 exploit. Learn how an autonomous AI agent weaponized this flaw to exfiltrate internal database credentials. #Marimo #CVE202639987 #AIAgent #Cyberattack #Sysdig #ThreatIntel https://meterpreter.org/marimo-cve-2026-39987-exploit/ https://t.co/ddrR3nWuL0

    Post summary

    The post claims that CVE‑2026‑39987 was weaponized by an autonomous AI agent to exfiltrate database credentials, providing a link that likely hosts exploit code, indicating active exploitation in the wild.

    0401161.0K
    12.5K followersView on X
  • Vivek | Cybersecurity@VivekIntel
    General

    Attackers Use LLM Agent for Post-Exploitation After Marimo CVE-2026-39987 Exploit https://thehackernews.com/2026/05/attackers-use-llm-agent-for-post.html?m=1

    Post summary

    The tweet references an article about attackers using an LLM agent after exploiting Marimo CVE-2026-39987, but provides no concrete technical, PoC, exploit, or mitigation details.

    1101051.1K
    17.5K followersView on X
  • elhacker.NET@elhackernet
    Active Exploitation

    Atacantes aprovechan CVE-2026-39987 para difundir puerta trasera basada en blockchain mediante Hugging Face https://blog.elhacker.net/2026/04/atacantes-aprovechan-cve-2026-39987.html

    Post summary

    Attackers are actively exploiting CVE-2026-39987 to deploy a blockchain‑based backdoor via Hugging Face, as reported in the headline.

    0401211.8K
    140.9K followersView on X
  • Nicolas Krassas@Dinosn
    Active Exploitation

    Marimo RCE Flaw CVE-2026-39987 Exploited Within 10 Hours of Disclosure https://thehackernews.com/2026/04/marimo-rce-flaw-cve-2026-39987.html

    Post summary

    The article reports that the Marimo RCE vulnerability (CVE‑2026‑39987) was actively exploited within ten hours of its disclosure, but it does not provide a PoC, patch information, or false‑positive clarification.

    030921.8K
    157.5K followersView on X
  • Nicolas Krassas@Dinosn
    Active Exploitation

    Attackers Use LLM Agent for Post-Exploitation After Marimo CVE-2026-39987 Exploit https://thehackernews.com/2026/05/attackers-use-llm-agent-for-post.html

    Post summary

    Attackers reportedly used an LLM agent for post‑exploitation after exploiting Marimo CVE‑2026‑39987, indicating real‑world exploitation of the vulnerability.

    020831.5K
    158.6K followersView on X
  • Nicolas Krassas@Dinosn
    Disclosure

    Marimo Pre-Auth RCE via Unauthenticated WebSocket Terminal (CVE-2026-39987) https://www.resecurity.com/blog/article/marimo-pre-auth-rce-via-unauthenticated-websocket-terminal-cve-2026-39987

    Post summary

    A blog article discloses a pre‑authentication remote code execution flaw (CVE‑2026‑39987) in Marimo’s WebSocket terminal, but offers no evidence of active exploitation, patch, or PoC code in the text itself.

    030801.7K
    158.1K followersView on X
  • White Rabbitx 🏴‍☠️@TheRabbitPy
    Active Exploitation

    Attackers exploited a Marimo vulnerability (CVE-2026-39987) to get initial access. Then they deployed an LLM agent to do post-exploitation. Let that sink in: An AI agent is now poking through compromised networks, making decisions, escalating privileges … autonomously. The attack surface just gained a brain. We spent years teaching LLMs to help developers write secure code. Attackers taught theirs to break in instead. Welcome to the new arms race 🤝

    Post summary

    Attackers used CVE-2026-39987 for initial access and deployed an autonomous LLM agent for post‑exploitation, indicating the CVE is actively exploited in the wild.

    31060322
    1.8K followersView on X
  • ExploitGrid@exploitgrid

    ExploitGrid Daily Digest 🚨 Top Exploits: CVE-2025-57819 (CVSS: 10) FreePBX CVE-2026-105134 (CVSS: 10) Ahsay CVE-2026-40281 (CVSS: 10) gotenberg CVE-2024-40453 (CVSS: 9.8) CVE-2026-39987 (CVSS: 9.3) marimo-team ..🧵👇

    11061289
    370 followersView on X
  • Rectifyq@_rectifyq
    Active Exploitation

    [Threat][MY]🟡CVE-2026-39987 update: How attackers weaponized marimo to deploy a blockchain botnet via HuggingFace Type: Broad-based Date: 15 Apr 2026 Refer: https://www.sysdig.com/blog/cve-2026-39987-update-how-attackers-weaponized-marimo-to-deploy-a-blockchain-botnet-via-huggingface #rectifyq #cti #threatintel #threatintelligence #malaysia #infosec

    Post summary

    The post announces that CVE-2026-39987 has been actively exploited by attackers who weaponized the marimo plugin to launch a blockchain botnet through HuggingFace, indicating ongoing real‑world use of the vulnerability.

    14040736
    820 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appcoreweavemarimo-python-

Explore more