mljar mercury Improper Access Control Flaw (CVE-2026-111057) Rated CVSS 10
A newly published critical vulnerability in mljar mercury carries a CVSS score of 10. Here is what is affected and how to respond.
Key points
- CVE-2026-111057 affects mljar mercury.
- CVSS 10 (Critical).
- No exploitation confirmed yet.
A critical improper access control tracked as CVE-2026-111057 has been published in the National Vulnerability Database for mljar mercury, with a CVSS base score of 10.
At a glance
- CVE
- CVE-2026-111057
- Product
- mljar mercury
- CVSS
- 10 Critical
- Weakness
- improper access control
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Mljar | mercury | >= 3.0.0, < 3.2.4 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-111057
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-111057?
CVE-2026-111057 is a improper access control vulnerability in mljar mercury.
How severe is CVE-2026-111057?
It has a CVSS score of 10 Critical.
Is CVE-2026-111057 being exploited?
There is no public confirmation of exploitation at the time of publication.
