ETK-2026-2649Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.description
Mercury standalone versions after 3.0 through 3.2.11 expose Jupyter configuration, settings, export, and terminal-related routes outside intended restrictions. An anonymous user of a public-mode server can alter shared configuration or settings and access notebook exports; if an existing terminal is available, they can connect to it and execute commands. Terminal command execution requires anonymous public-mode access and a pre-existing terminal.
mitigation
Upgrade Mercury to 3.2.12 or later, then restart running servers and replace deployed runtime images. Until upgraded, require authentication and disable terminal access; do not rely only on blocking the terminal REST API.
fixed in 3.2.12
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-26 09:15Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-2649
{ "etk_id": "ETK-2026-2649", "cve_id": null, "display_id": "ETK-2026-2649", "ghsa_id": "GHSA-jgh7-p4h3-836h", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Improper route access control in Mercury standalone mode", "summary": "Mercury standalone versions after 3.0 through 3.2.11 expose Jupyter configuration, settings, export, and terminal-related routes outside intended restrictions. An anonymous user of a public-mode server can alter shared configuration or settings and access notebook exports; if an existing terminal is available, they can connect to it and execute commands. Terminal command execution requires anonymous public-mode access and a pre-existing terminal.", "mitigation": "Upgrade Mercury to 3.2.12 or later, then restart running servers and replace deployed runtime images. Until upgraded, require authentication and disable terminal access; do not rely only on blocking the terminal REST API.", "vendor": "pip", "product": "mercury", "affected": [ { "affected_notes": [], "affected_ranges": [ "> 3.0, <= 3.2.11" ], "ecosystem": "pip", "fixed_versions": [ "3.2.12" ], "package_name": "mercury", "purl": "pkg:pypi/mercury" } ], "cwes": [ 306 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 14.13306225, "t0_at": null, "signals": { "check": { "at": "2026-10-26T13:26:34.856693+00:00", "days": -0.19623153652777778, "is_lower_bound": true, "measured_at": "2026-10-26T18:09:09.316295+00:00", "url": null }, "trigger_signal": { "at": "2026-10-26T09:15:57+00:00", "days": -0.3702808038078704, "is_lower_bound": true, "measured_at": "2026-10-26T18:09:09.316295+00:00", "url": "https://github.com/mljar/mercury/security/advisories/GHSA-jgh7-p4h3-836h" } } }
published 2026-10-26 13:12Z
last change 2026-10-26 17:59Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.