Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 17, 2026

CVE-2026-111057 Scanner

CVE-2026-111057 Scanner - Remote Code Execution (RCE) vulnerability in Mercury

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
10.0
CVSScritical
Exploitable remotely over the internet · no authentication required.
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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
mercuryby mljar
>= 3.0.0, < 3.2.4
Updated Nov 17, 2026View on NVD →
Detail

Mercury is widely used as a platform for building and deploying machine learning models. It allows developers and organizations to integrate data handling, model training, and deployment within a seamless environment. Users leverage its capabilities to visualize data, run scripts, and share results through interactive dashboards and applications. It's commonly adopted by data scientists, analysts, and developers for automating workflows and deploying data-driven applications. The tool aims to streamline machine learning operations, enhance collaboration, and provide an intuitive interface for complex computational tasks. With a user-friendly design, Mercury is accessible to both technical and non-technical users for efficient project execution in the field of data science.

The Remote Code Execution (RCE) vulnerability in Mercury arises due to the improper handling of requests to the Jupyter Server API, which is part of Mercury's backend infrastructure. This specific issue exists due to a missing comma in the BLOCKED_PATTERNS list of the Python script mercury_app/block_handler.py. As a result, the JupyterLab rule and /api/terminals rule are inadvertently merged into a single regular expression. Consequently, unauthenticated users can directly access the /api/terminals endpoint, which leads to execution of arbitrary commands on the server. This flaw critically underlines the necessity for rigorous input validation and proper configuration management within software platforms. The exploitability of this vulnerability necessitates immediate attention for all affected versions.

Technically, the vulnerability is rooted in how Mercury's endpoint handling inadvertently exposes the Jupyter Server's terminal API without requiring authentication. The vulnerable endpoints include /api/terminals, which, when accessed, can allow attackers to pass operating system commands directly to the server. This misconfiguration arises because the Python script improperly concatenates two rules into a regular expression, failing to block unauthorized access. The critical flaw lies in the missing comma separator, compromising the script's logic intended to regulate terminal access. Consequently, attackers exploiting this vulnerability can gain administrative privileges to run commands as the Mercury user. The oversight emphasizes the need for vigilance in managing regular expressions and access control configurations.

Exploitation of this vulnerability may have severe consequences, allowing malicious actors to execute arbitrary commands on the host server. Such actions can lead to unauthorized access to sensitive data, installation of malware, and potentially gaining control over the entire system. This could result in data breaches, disruptions in service, and compromise of the Mercury system and its deployed applications. Moreover, it poses a significant threat to any connected or dependent services or databases. Protecting against this vulnerability is critical to safeguarding the integrity and confidentiality of the affected systems. Immediate patching and updating to a non-vulnerable version are essential to mitigate these risks.

REFERENCES

Solution Advice
  • Upgrade Mercury to version 3.2.4 or later to eliminate the vulnerability.
  • Regularly review and test your systems for any similar configuration flaws.
  • Implement robust input validation to identify and prevent unauthorized access patterns.
  • Enhance logging and monitoring to detect and respond to suspicious API access attempts.
  • Regularly audit code for security vulnerabilities, especially around access control logic.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.