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-111058 has been found in mercury.
Attackers can target a specific entry point like POST /api/kernels over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade mercury to 3.2.6 or later.
If unsure, ask your IT team or search "mercury CVE-2026-111058" on the vendor's site.
CVE-2026-111058 (mercury) — CWE-862 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/kernels / POST /api/terminals / MERCURY_TOKEN / BLOCKED_PATTERNS
Patched: 3.2.6 — 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-862) exists in mercury. Attackers reach the vulnerable code path via POST /api/kernels without authentication.
Check the vendor advisory for the affected versions of mercury. Attack surface: POST /api/kernels / POST /api/terminals / MERCURY_TOKEN / BLOCKED_PATTERNS.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.2.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/kernels requests with malformed payloads or SQL meta-characters. 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
Hunt for indicators of compromisedetect
grep 'POST /api/kernels' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/kernelsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3
Apply patchpatch
Upgrade mercury to 3.2.6ステージング環境で 3.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4
Post-deployment verificationverify
Replay attack against POST /api/kernels on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| pip | mercury |
< 3.2.6 |
3.2.6 |
| PyPI | mercury |
< 3.2.6 |
3.2.6 |
Original description The description as published by the source.
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.
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