Quick answers
- Is CVE-2026-111057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111057 being exploited in the wild.
- How severe is CVE-2026-111057?
- Critical severity, with a CVSS score of 10, published 19 October 2026.
- Which products and versions are affected?
- Mljar Mercury 3.0.0 to 3.2.3; mercury (PyPI) >= 3.0.0, <= 3.2.3, ECOSYSTEM:introduced=3.0.0,fixed=3.2.4.
- Is there a fix for CVE-2026-111057?
- Yes. mercury (PyPI): upgrade to 3.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111057 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111057?
- Check whether you run Mljar Mercury or mercury (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mercury (PyPI): upgrade to 3.2.4 or later
pip install "mercury>=3.2.4"
Technical details
The vulnerability stems from a missing comma in the BLOCKED_PATTERNS concatenation that caused /lab and /api/terminals regex literals to merge, allowing requests to /api/terminals to bypass the anonymous endpoint blocklist. An unauthenticated attacker can reach Jupyter Server's terminal API over the network and execute arbitrary OS commands and access data available to the Mercury process.
Affected products
- mljar Mercury 3.0.0 to 3.2.3
Identifiers
- CVE-2026-111057
- GHSA-f8c7-rwf9-fmgm
Timeline
- 2026-10-19: disclosed
- 2026-08-21: patched: Version 3.2.4 released with fix