Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-39987-Marimo-Preauth-RCE — Security research and SOC investigation of CVE-2026-39987 using Docker, Nginx, Linux process monitoring, Splunk SIEM, and SPL detection rules. | Kitploit
Tools/GitHubGitHub/laremontada12/cve-2026-39987-marimo-preauth-rce
Container SecurityVulnerability AnalysisWeb Application ExploitationPenetration TestingLearning & EducationLabs & Practice
GitHublaremontada12/cve-2026-39987-marimo-preauth-rce

CVE-2026-39987-Marimo-Preauth-RCE

Share

Security research and SOC investigation of CVE-2026-39987 using Docker, Nginx, Linux process monitoring, Splunk SIEM, and SPL detection rules.

View Repository
12513 days agoNot yet reviewed

CVE-2026-39987 – Marimo Pre-authentication RCE Research

Security research and experimental validation of CVE-2026-39987, a missing authentication vulnerability affecting Marimo's terminal WebSocket endpoint.

This project documents the vulnerability's root cause, local reproduction results, official security patch, and regression testing in controlled Docker environments.

1. Vulnerability Overview

FieldDetails
CVECVE-2026-39987
ProductMarimo
Vulnerability TypeMissing Authentication / Pre-authentication RCE
CWECWE-306
SeverityCritical
Affected Version Tested0.20.4
Patched Version Tested0.23.0
Affected Endpoint/terminal/ws
Security AdvisoryGHSA-2679-6mx9-h9xc

The vulnerability arises from missing authentication validation in Marimo's terminal WebSocket endpoint.

In the affected implementation, terminal availability and application mode are checked without properly validating the connecting client's identity.

This can expose server-side terminal functionality to unauthenticated clients under vulnerable configurations.

2. Research Objectives

The project focused on:

  • Understanding the affected Marimo component.
  • Building isolated vulnerable and patched Docker environments.
  • Identifying the vulnerability's root cause.
  • Analyzing WebSocket authentication and connection flows.
  • Reviewing the official security patch.
  • Recording local experimental evidence.
  • Running official security regression tests.
  • Documenting mitigation recommendations.

3. Lab Environment

ComponentConfiguration
Host Operating SystemWindows 11
Container PlatformDocker Desktop
Vulnerable EnvironmentMarimo 0.20.4
Patched EnvironmentMarimo 0.23.0
Container PythonPython 3.12
Regression TestingPython 3.13, pytest
Network ScopeLocalhost only

Both Marimo versions were deployed in separate Docker environments.

The research was performed on locally controlled systems.

4. Experimental Results

Vulnerable Version – Marimo 0.20.4

A local experiment was conducted against the vulnerable terminal WebSocket endpoint without supplying authentication credentials.

The recorded experiment produced server-side command output inside the vulnerable Docker container.

Observed execution context:

uid=0(root) gid=0(root) groups=0(root)

Additional observations identified the container's hostname and working directory.

These findings are consistent with successful reproduction of the reported pre-authentication RCE vulnerability in the isolated lab.

The observed root privileges were limited to the container execution environment. They do not demonstrate privilege escalation or compromise of the Windows host.

Experimental evidence:

Vulnerable version – command output

Patched Version – Marimo 0.23.0

A manual unauthenticated connection attempt was performed against the patched terminal WebSocket endpoint.

Observed result:

WebSocketBadStatusException
Handshake status 403 Forbidden

The server rejected the connection during the WebSocket handshake.

Experimental evidence:

Patched version – connection rejected

5. Security Regression Testing

Two official Marimo authentication regression tests were executed against the Marimo 0.23.0 source code.

Security TestResult
test_terminal_ws_unauthorizedPASSED
test_terminal_ws_wrong_tokenPASSED

Pytest summary:

2 passed
34 deselected

These tests validate expected authentication-rejection behavior in the test environment.

The automated tests used Starlette's TestClient and were run separately from the Docker-based manual verification.

Evidence:

Official regression test results

6. Root Cause and Patch Analysis

The affected Marimo 0.20.4 terminal WebSocket endpoint lacked the authentication validation introduced by the official security patch.

The patch adds an authentication check before allowing terminal WebSocket processing when authentication is enabled.

The research examined:

  • Terminal WebSocket endpoint implementation.
  • Authentication validation behavior.
  • Vulnerable and authenticated WebSocket flows.
  • Official patch changes in terminal.py.
  • Authentication regression tests in test_terminal.py.

Official Patch: Marimo PR #9098

7. Technical Documentation

DocumentDescription
Marimo OverviewApplication and vulnerability background
Root Cause AnalysisMissing authentication validation
WebSocket Flow AnalysisConnection flow diagrams
Patch Diff AnalysisOfficial security patch analysis
Security ValidationManual experiments and regression testing
Security Research ReportConsolidated technical findings
Mitigation and RecommendationsRemediation and defensive measures

8. Mitigation

The recommended remediation is to upgrade affected Marimo installations to version 0.23.0 or a newer maintained release.

Additional defensive recommendations include:

  • Restricting access to development servers.
  • Avoiding unnecessary public exposure of terminal functionality.
  • Running the application with least privilege.
  • Enforcing authentication on sensitive WebSocket endpoints.
  • Maintaining automated authentication regression tests.

See mitigation.md for details.

9. Research Scope and Limitations

This project was conducted for educational and authorized security research.

Testing was limited to isolated localhost environments.

The vulnerable-version experimental results were recorded locally and have not been independently reproduced by a separate researcher.

The research did not demonstrate host operating-system compromise or privilege escalation beyond the container process's existing privileges.

Only two selected official regression tests were executed. The full Marimo test suite was not run.

10. References

  • GitHub Security Advisory – GHSA-2679-6mx9-h9xc
  • Official Security Patch – PR #9098
  • Marimo Official Repository
  • Additional Research References

Research focus: Vulnerability analysis, controlled experimental validation, WebSocket authentication, source-code review, and security patch verification.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    938
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    556
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    352
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    343
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    336
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    291

Explore all tools

Browse our collection of tools

View all tools →