Vulnerability in mercury
AI summary
Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.
A vulnerability tracked as CVE-2026-111057 has been found in mercury.
Attackers can target a specific entry point like BLOCKED_PATTERNS over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade mercury to 3.2.4 or later.
If unsure, ask your IT team or search "mercury CVE-2026-111057" on the vendor's site.
CVE-2026-111057 (mercury) — CWE-185 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: BLOCKED_PATTERNS
Patched: 3.2.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-185) exists in mercury. Attackers reach the vulnerable code path via BLOCKED_PATTERNS without authentication.
Check the vendor advisory for the affected versions of mercury. Attack surface: BLOCKED_PATTERNS.
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.
Update to 3.2.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mercury' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'mercury' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mercuryを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade mercury to 3.2.4ステージング環境で 3.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| pip | mercury |
< 3.2.4 |
3.2.4 |
| PyPI | mercury |
≥ 3.0.0, < 3.2.4 |
3.2.4 |
Original description The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com