Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55609 high CVSS 7.1

Vulnerability in consciousness-explorer (CVE-2026-55609)

Summary

Vulnerability in consciousness-explorer (CVE-2026-55609). Data can be tampered with by attackers. Exploitable via export_state. Mitigation: upgrade to 1.1.2 or later.

Original description

The description as published by the source.

Impact

An arbitrary file write vulnerability (CWE-73, External Control of File Name or Path) exists in the consciousness-explorer component of sublinear-time-solver. The MCP export_state (and import_state) tool accepted a user-supplied filepath argument and passed it directly to fs.writeFileSync / fs.readFileSync without constraining the destination or rejecting path traversal. An attacker able to invoke the MCP tool could write or overwrite any file accessible to the server process (e.g. ~/.ssh/authorized_keys, application files), leading to integrity loss and potential service disruption.

The same sink class was present in the main solver MCP server (saveVectorToFile / loadVectorFromFile).

Affected versions

  • consciousness-explorer < 1.1.2
  • sublinear-time-solver < 1.6.0
  • sublinear (crates.io) < 0.2.0

Patches

  • consciousness-explorer@1.1.2
  • sublinear-time-solver@1.6.0
  • sublinear@0.2.0

State/vector files are now confined to a dedicated directory (overridable via $CONSCIOUSNESS_EXPLORER_STATE_DIR / $SUBLINEAR_SOLVER_VECTOR_DIR), a basename-only contract is enforced (rejecting separators, .., NUL/control chars, hidden files, and Windows reserved names), and files are opened with O_NOFOLLOW | O_CLOEXEC mode 0o600. Covered by 14 regression tests in tests/consciousness/safe-path.test.mjs.

Breaking change: callers must now pass a basename, not an absolute path.

Workarounds

Do not expose the MCP server to untr…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55609 has been found in consciousness-explorer.
Attackers can target a specific entry point like export_state over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade consciousness-explorer to 1.1.2 or later.
If unsure, ask your IT team or search "consciousness-explorer CVE-2026-55609" on the vendor's site.

CVE-2026-55609 (consciousness-explorer) — CWE-73 / CVSS v3 7.1
Attack vector: local / no user interaction
Attack surface: export_state / import_state / filepath / fs.writeFileSync
Patched: 1.1.2 — apply immediately
Workaround: Do not expose the MCP server to untrusted clients; restrict export_state to trusted local users; run the server under a low-privilege account with a restricted working directory.
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.

❓ What is the problem

A vulnerability (CWE-73) exists in consciousness-explorer. Attackers reach the vulnerable code path via export_state.

📍 Affected scope

Check the vendor advisory for the affected versions of consciousness-explorer. Attack surface: export_state / import_state / filepath / fs.writeFileSync.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.1.2.

🛡️ Workaround

Workaround: Do not expose the MCP server to untrusted clients; restrict export_state to trusted local users; run the server under a low-privilege account with a restricted working directory.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'consciousness-explorer' . 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. 1
    Identify exposure identify 
    grep -r 'consciousness-explorer' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で consciousness-explorer を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Do not expose the MCP server to untrusted clients; restrict `export_state` to trusted local users; run the server under a low-privilege account with a restricted working directory.

    パッチが適用されるまでの応急処置として、Do not expose the MCP server to untrusted clients; restrict export_state to trusted local users; run the server under a low-privilege account with a restricted working directory. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade consciousness-explorer to 1.1.2

    ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm consciousness-explorer
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
npm sublinear-time-solver
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.6.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details