Quantum Secular Labs / Blog / Advisories

CVE-2026-111057: Mercury: Command injection

CVE-2026-111057 is rated critical with a CVSS v3.1 base score of 10.0. Per its scoring, it can be exploited over the network, without authentication, without any user interaction. The scored impact on confidentiality, integrity and availability is the highest available.

Vulnerability description

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

Severity breakdown

CVSS v3.1 10.0: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack vector: Network. Exploitable remotely over the network, with no need for local or physical access.
Attack complexity: Low. No special conditions; the attack can be repeated reliably.
Privileges required: None. No account or prior access is needed.
User interaction: None. No action from any user is needed.
Scope: Changed. Impact reaches beyond the vulnerable component to other resources.
Confidentiality impact: High. Total loss of confidentiality; sensitive data can be fully disclosed.
Integrity impact: High. Total loss of integrity; data or system state can be fully modified.
Availability impact: High. Total loss of availability; the component can be shut down.

Underlying weakness

CWE-185: Incorrect Regular Expression

The product specifies a regular expression in a way that causes data to be improperly matched or compared.

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.