CVE-2026-111057: Mercury: Unauthenticated Remote Code Execution in /api/terminals - access control bypass

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-19).

Weakness: CWE-185: Incorrect Regular Expression; CWE-284: Improper Access Control

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-17112, EUVD-2026-104419, GHSA-f8c7-rwf9-fmgm

VEDAS cluster: VEDAS:DIVINEDUSK

Exploit Observer links 6 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (6)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (5)

Catalogue entries, not exploit evidence.

4 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
mljar mercuryversion >= 3.0.0, < 3.2.4Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: pypi mercury, сообщество_свободного_программного_обеспечения mercury.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

Mercury - Improper Access Control

In mljar Mercury from 3.0.0 until 3.2.4, a missing comma in the anonymous endpoint BLOCKED_PATTERNS list concatenates the `/lab` and `/api/terminals` regular-expression literals, so requests to `/api/terminals` bypass the blocklist and reach Jupyter Server’s terminal API. An unauthenticated attacker can create an interactive operating-system terminal and execute commands as the Mercury process.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /api/terminals); it decides using dsl matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-111057.yaml
Show the template (39 lines)
yaml
id: CVE-2026-111057

info:
  name: "Mercury - Improper Access Control"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    In mljar Mercury from 3.0.0 until 3.2.4, a missing comma in the anonymous endpoint
    BLOCKED_PATTERNS list concatenates the `/lab` and `/api/terminals` regular-expression
    literals, so requests to `/api/terminals` bypass the blocklist and reach Jupyter Server's
    terminal API. An unauthenticated attacker can create an interactive operating-system
    terminal and execute commands as the Mercury process.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-111057&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=mercury&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 10.0
    cve-id: CVE-2026-111057
    cwe-id: CWE-284
  metadata:
    verified: false
  tags: cve,cve2026,mercury,auth-bypass
http:
  - raw:
      - |
        POST /api/terminals HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {}

    matchers:
      - type: dsl
        dsl:
          - 'contains_all(body, "\"name\"", "\"last_activity\"")'
          - 'contains(content_type, "application/json")'
          - 'status_code == 200 || status_code == 201'
        condition: and

CVE-2026-111057.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-111057 Mercury - Improper Access Control. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-111057 Mercury - Improper Access Control"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/terminals"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-111057; reference:url,https://www.exploit.observer/?keyword=CVE-2026-111057&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=mercury&match=exact; sid:1080400; rev:1;)

CVE-2026-111057.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.