CVE-2026-111057
CVE-2026-111057 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-185.
Key facts
- Severity: Critical (CVSS 3.x base score 10.0)
- EPSS exploit prediction: 0% (38th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-185
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-111057?
- 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.
- How severe is CVE-2026-111057?
- CVE-2026-111057 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-111057 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-111057?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2026-111057 published?
- CVE-2026-111057 was published on 2026-10-19.
References
- https://github.com/mljar/mercury/commit/8c467129037ee9df269d543ac217ffd33b97bf3f
- https://github.com/mljar/mercury/releases/tag/v3.2.4
- https://github.com/mljar/mercury/security/advisories/GHSA-f8c7-rwf9-fmgm
Other CWE-185 vulnerabilities
- CVE-2024-52289 — Critical (CVSS 9.8): authentik is an open-source identity provider. Redirect URIs in the OAuth2 provider in authentik are checked by RegEx…
- CVE-2019-12798 — Critical (CVSS 9.8): An issue was discovered in Artifex MuJS 1.0.5. regcompx in regexp.c does not restrict regular expression program size,…
- CVE-2026-25896 — Critical (CVSS 9.3): fast-xml-parser allows users to validate XML, parse XML to JS object, or build XML from JS object without C/C++ based…
- CVE-2026-4296 — High (CVSS 8.8): An incorrect regular expression vulnerability was identified in GitHub Enterprise Server that allowed an attacker to…
- CVE-2026-111755 — High (CVSS 8.2): follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until…
- CVE-2018-17984 — High (CVSS 7.8): An unanchored /[a-z]{2}/ regular expression in ISPConfig before 3.1.13 makes it possible to include arbitrary files,…