Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

sublinear-time-solver

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1npmPublished

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

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

    Affected
    • npm sublinear-time-solver < 1.6.0
    Fixed in
    1.6.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 1.6.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →