Skip to content

A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.

docs: Update security docs for 0.23.0 and outline SOP (#9114)

Dylan Madisetti6f81094fae08
diff --git a/SECURITY.md b/SECURITY.md
index 40557a8b51..28b431d4b3 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -2,12 +2,29 @@
marimo is committed to providing a secure environment for notebook development and application deployment. For a comprehensive overview of marimo's security model and features, see our [Security documentation](https://docs.marimo.io/security/).
+## Supported Versions
+
+We provide security patches for the latest stable release only. We encourage all users to stay on the latest version.
+
## Reporting a Vulnerability
To report a security vulnerability, [please draft an advisory through
-Github](https://github.com/marimo-team/marimo/security/advisories/new), or
+GitHub](https://github.com/marimo-team/marimo/security/advisories/new), or
email the marimo team; security [at] marimo [dot] io.
+Please include:
+- A description of the vulnerability and its potential impact
+- Steps to reproduce or a proof-of-concept
+- Any suggested mitigations if known
+
+### What to Expect
+
+- **Acknowledgement**: We will respond within 3 business days to confirm receipt
+- **Triage**: We will assess severity and scope within 7 days
+- **Patch & disclosure**: We aim to release a fix and publish a CVE/advisory simultaneously, typically within 90 days of the initial report
+
+We will keep you informed throughout the process and credit you in the advisory unless you prefer to remain anonymous.
+
### What Warrants a Security Advisory
We issue CVEs and security advisories when:
@@ -44,5 +61,7 @@ We would like to acknowledge and thank the following individuals for their respo
- @devgi
- @W-M-T (Ward Theunisse)
- @doredry
+ - @q1uf3ng from OneKey Anzen Lab
+ - @Fushuling @RacerZ-fighting
Your contributions help keep marimo safe for the entire community. We encourage security researchers to report issues and welcome your help in making marimo more secure.
diff --git a/docs/security.md b/docs/security.md
index fc72bedb12..2cf69f280d 100644
--- a/docs/security.md
+++ b/docs/security.md
@@ -133,6 +133,8 @@ For general questions about marimo, see our [FAQ](faq.md) or join us on [Discord
<ul>
<li><strong><a href="https://github.com/marimo-team/marimo/security/advisories/GHSA-xjv7-6w92-42r7">[GHSA-xjv7-6w92-42r7]</a></strong>: Unauthenticated proxy vulnerability in matplotlib endpoint. The <code>/mpl/[port]/[route]</code> endpoint allowed external attackers to reach internal services. Affected versions 0.9.20 through 0.16.3. Fixed in 0.16.4. </li>
+ <li><strong><a href="https://github.com/marimo-team/marimo/security/advisories/GHSA-2679-6mx9-h9xc">[GHSA-2679-6mx9-h9xc]</a></strong>: Remote code execution via unauthenticated terminal access in edit mode. The terminal panel did not require authentication, allowing unauthenticated users to execute arbitrary commands on instances of <code>marimo edit</code> exposed to the internet. <strong>Run mode (<code>marimo run</code>) is not affected.</strong> Affected versions 0.7.10 through 0.22.x. Fixed in 0.23.0. See <a href="https://links.marimo.app/cwe-306-terminal-ws-auth-bypass">our advisory</a> for more information.</li>
+
<li><strong>[molab-0]</strong>: iframe sandbox escape via markdown render. In molab, an attacker could exploit a vulnerability in the iframe sandboxing to escape the iframe and execute code in the parent context. Fixed in molab deployment on 2025-10-19.</li>
</ul>