CVE-2026-111057
Received Received - Intake

Path Traversal in Mercury Framework Allows RCE

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
CVE-2026-111057
EUVD
EUVD-2026-104419

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
mljar mercury >= 3.0.0, < 3.2.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-185 The product specifies a regular expression in a way that causes data to be improperly matched or compared.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Mercury is a Python framework for sharing Jupyter notebooks as web apps. A bug in versions 3.0.0 to 3.2.3 caused a missing comma in a security pattern list. This merged two URL path patterns, allowing unauthenticated access to the terminal API endpoint. Attackers could then execute arbitrary commands on the server with the same permissions as the Mercury process.

Detection Guidance

Check Mercury version with pip show mercury. If version is between 3.0.0 and 3.2.3, the system is vulnerable. Inspect network traffic for unauthorized access to /api/terminals endpoints.

Impact Analysis

If you run Mercury versions 3.0.0 to 3.2.3, an attacker could gain full control of your server. They could steal data, install malware, or use your system for other attacks. The impact includes complete system compromise and data breaches.

Compliance Impact

This vulnerability likely violates GDPR and HIPAA due to unauthorized data access and potential data breaches. It could result in regulatory fines, loss of trust, and legal consequences for failing to protect sensitive data.

Mitigation Strategies

Upgrade Mercury to version 3.2.4 or later immediately. If upgrading is not possible, restrict access to /api/terminals endpoints via firewall rules or reverse proxy configurations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111057. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart