https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 19:17:15 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-111057 <p>Mercury is a Python framework for sharing Jupyter notebooks as web applications and dashboards. From 3.0.0 until 3.2.4, a missing comma in BLOCKED_PATTERNS concatenates the /lab and /api/terminals regular-expression literals. Requests to /api/terminals therefore bypass the anonymous endpoint blocklist and reach Jupyter Server&#39;s terminal API. An unauthenticated attacker can use the resulting interactive operating-system shell to execute commands and access data available to the Mercury process. This issue is fixed in version 3.2.4.</p> <p>Mercury is a Python framework for sharing Jupyter notebooks as web applications and dashboards. From 3.0.0 until 3.2.4, a missing comma in BLOCKED_PATTERNS concatenates the /lab and /api/terminals regular-expression literals. Requests to /api/terminals therefore bypass the anonymous endpoint blocklist and reach Jupyter Server&#39;s terminal API. An unauthenticated attacker can use the resulting interactive operating-system shell to execute commands and access data available to the Mercury process. This issue is fixed in version 3.2.4.</p> https://db.gcve.eu/vuln/fkie_cve-2026-111057 https://db.gcve.eu/vuln/ghsa-f8c7-rwf9-fmgm <p><strong>Affected:</strong> PyPI: mercury</p> <p>### Summary A missing comma in `mercury_app/block_handler.py`&#39;s `BLOCKED_PATTERNS` list causes the blocklist to fail to cover the `/api/terminals` endpoint. As a result, any unauthenticated attacker can spawn a full, interactive OS-level shell on the host running Mercury.</p> <p>### Details The blocklist in `mercury_app/block_handler.py` is defined as: ``` BLOCKED_PATTERNS = [ # JupyterLab UI + API r&#34;/lab(?!/(?:extensions/|api/settings(?:/|$)|api/translations(?:/|$)))(?:/.*)?&#34; r&#34;/api/terminals(?:/.*)?&#34;, r&#34;/api/shutdown(?:/.*)?&#34;, r&#34;/files(?:/.*)?&#34;, ] ``` The missing comma between the first and the second line causes Python to merge the rules, therefore the actual list that is blocked looks like this:</p> <p>/lab...(?:/.`*`)?/api/terminals(?:/.`*`)? (the first two lines joined together) /api/shutdown(?:/.`*`)? /files(?:/.`*`)?</p> <p>A direct request to `/api/terminals` does not match any of the 3 blocklist rules and is therefore **not blocked**, reaching Jupyter Server&#39;s built-in terminal API, which spawns a real OS shell accessible over a WebSocket connection. No authentication, account, session or pre-existing access to Mercury is required.</p> <p>### PoC Testing was performed on a local Docker deployment (https://runmercury.com/deploy/dockerfile/), Mercury version 3.2.3, default configuration. **Step 1 - spawn a terminal:**</p> <p>``` curl -i -X POST http://localhost:8888/api/terminals ``` Response: `{&#34;name&#34;: &#34;1&#34;, &#34;last_activity&#34;: &#34;...&#34;}`</p> <p>**Step 2 - connect to the terminal and e…</p> <p><strong>Affected:</strong> PyPI: mercury</p> <p>### Summary A missing comma in `mercury_app/block_handler.py`&#39;s `BLOCKED_PATTERNS` list causes the blocklist to fail to cover the `/api/terminals` endpoint. As a result, any unauthenticated attacker can spawn a full, interactive OS-level shell on the host running Mercury.</p> <p>### Details The blocklist in `mercury_app/block_handler.py` is defined as: ``` BLOCKED_PATTERNS = [ # JupyterLab UI + API r&#34;/lab(?!/(?:extensions/|api/settings(?:/|$)|api/translations(?:/|$)))(?:/.*)?&#34; r&#34;/api/terminals(?:/.*)?&#34;, r&#34;/api/shutdown(?:/.*)?&#34;, r&#34;/files(?:/.*)?&#34;, ] ``` The missing comma between the first and the second line causes Python to merge the rules, therefore the actual list that is blocked looks like this:</p> <p>/lab...(?:/.`*`)?/api/terminals(?:/.`*`)? (the first two lines joined together) /api/shutdown(?:/.`*`)? /files(?:/.`*`)?</p> <p>A direct request to `/api/terminals` does not match any of the 3 blocklist rules and is therefore **not blocked**, reaching Jupyter Server&#39;s built-in terminal API, which spawns a real OS shell accessible over a WebSocket connection. No authentication, account, session or pre-existing access to Mercury is required.</p> <p>### PoC Testing was performed on a local Docker deployment (https://runmercury.com/deploy/dockerfile/), Mercury version 3.2.3, default configuration. **Step 1 - spawn a terminal:**</p> <p>``` curl -i -X POST http://localhost:8888/api/terminals ``` Response: `{&#34;name&#34;: &#34;1&#34;, &#34;last_activity&#34;: &#34;...&#34;}`</p> <p>**Step 2 - connect to the terminal and e…</p> https://db.gcve.eu/vuln/ghsa-f8c7-rwf9-fmgm