Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1

consciousness-explorer / sublinear-time-solver MCP export_state has an arbitrary file write

CVE-2026-55609GHSA-xc9g-j69q-37xw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (consciousness-explorer 1.1.2; sublinear-time-solver 1.6.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-55609: 0.17% estimated exploitation activity in the next 30 days; percentile 6.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 exportstate (and importstate) 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/authorizedkeys, 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xc9g-j69q-37xw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55609

Advisory: consciousness-explorer / sublinear-time-solver MCP export_state has an arbitrary file write
IDs: CVE-2026-55609, GHSA-xc9g-j69q-37xw
Record: https://patchnext.com/advisories/cve-2026-55609 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: consciousness-explorer 1.1.2; sublinear-time-solver 1.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm consciousness-explorer: affected < 1.1.2; fixed in 1.1.2
- npm sublinear-time-solver: affected < 1.6.0; fixed in 1.6.0

## Suggested inspection (read-only)
- `npm ls consciousness-explorer --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls sublinear-time-solver --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on consciousness-explorer, sublinear-time-solver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xc9g-j69q-37xw (GitHub-reviewed advisory GHSA-xc9g-j69q-37xw lists affected ranges: npm consciousness-explorer >=0 =0 <1.6.0)

Commands are suggestions: review each one before running it.

Loading voting…