Remote Code Execution in Mercury Framework

Executive Summary

This vulnerability in Mercury, a Python framework for sharing Jupyter notebooks, allows anonymous users to create Jupyter kernels and execute arbitrary Python code without authentication. The issue exists because the endpoint blocklist does not cover /api/kernels and the websocket wrapper does not properly authorize executable messages. This flaw was fixed in version 3.2.6.

Useful 0 Not Useful 0

Detection Guidance

Check Mercury version with pip show mercury or mercury --version. If version is below 3.2.6, the system is vulnerable. Inspect network traffic for unauthorized access to /api/kernels endpoint or unexpected kernel creation requests.

Useful 0 Not Useful 0

Impact Analysis

An attacker could exploit this to run malicious Python code on your system, potentially stealing data, installing malware, or disrupting services. Since it allows arbitrary code execution, the impact depends on the permissions of the Mercury service. Systems with sensitive data or critical operations are at higher risk.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles or HIPAA's security requirements. Organizations may face compliance breaches if attackers exfiltrate personal or health data due to the lack of authentication controls.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade Mercury to version 3.2.6 or later immediately. If upgrading is not possible, restrict access to the /api/kernels endpoint and enable token-based authentication to prevent anonymous kernel creation.

Useful 0 Not Useful 0