mljar mercury Missing Authorization Flaw (CVE-2026-111058) Rated CVSS 9.8
A newly published critical vulnerability in mljar mercury carries a CVSS score of 9.8. Here is what is affected and how to respond.
Key points
- CVE-2026-111058 affects mljar mercury.
- CVSS 9.8 (Critical).
- No exploitation confirmed yet.
mljar mercury is affected by CVE-2026-111058, a missing authorization that the National Vulnerability Database rates 9.8 out of 10.
At a glance
- CVE
- CVE-2026-111058
- Product
- mljar mercury
- CVSS
- 9.8 Critical
- Weakness
- missing authorization
- 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. Prior to 3.2.6, default tokenless deployments allow anonymous clients to create Jupyter kernels and send execute_request messages containing arbitrary Python. The endpoint blocklist does not cover /api/kernels, and the websocket wrapper previously tracked idle activity without authorizing executable messages. This issue is fixed in version 3.2.6.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Mljar | mercury | < 3.2.6 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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-111058
- 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-111058?
CVE-2026-111058 is a missing authorization vulnerability in mljar mercury.
How severe is CVE-2026-111058?
It has a CVSS score of 9.8 Critical.
Is CVE-2026-111058 being exploited?
There is no public confirmation of exploitation at the time of publication.
