dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7645

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in ruvnet sublinear-time-solver 1.5.0. Affected by this vulnerability is the function export_state of the file src/consciousness-explorer/mcp/server.js of the component MCP Interface. The manipulation results in path traversal. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability exists in the export_state function of the MCP server interface in ruvnet sublinear-time-solver v1.5.0. The function fails to properly sanitize user-supplied file paths, allowing an attacker to use '../' sequences to access files outside the intended directory. This can be exploited remotely, and a public exploit is available.

MitigationImplement strict input validation on the export_state function to ensure path parameters cannot contain directory traversal sequences ('../' or '..\'). Use allowlist-based validation or resolve paths and verify they remain within an allowed base directory before file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ruvnet sublinear-time-solver is installed
    Look for the software in your system using package managers (pip list, npm list, or system package queries depending on installation method), or check for the application binary/executable in common installation directories.
    Affected if The software is not present on the system.
  2. Determine installed version
    Run the version command for the installed package (e.g., pip show ruvnet-sublinear-time-solver, or check --version flag of the binary). Compare the version number to v1.5.0.
    Affected if The installed version is exactly v1.5.0.
  3. Verify MCP server interface is enabled
    Inspect the application configuration files or command-line arguments to confirm the MCP server component is active. Look for flags like --mcp-server, --enable-mcp, or configuration entries enabling the MCP interface.
    Affected if The MCP server interface is disabled or not configured.
  4. Confirm export_state function is accessible
    Check the MCP server API endpoints or function exports. The export_state function must be exposed via the MCP interface for the vulnerability to be exploitable. Review the MCP server route definitions or OpenAPI/spec documentation.
    Affected if The export_state function is not exposed or not reachable via the MCP interface.
  5. Test for path traversal vulnerability in export_state
    Send a request to the export_state endpoint with a path containing '../' sequences (e.g., ../../etc/passwd or ../../config.json). Observe if the server returns file contents from outside the intended export directory.
    Affected if The application returns file contents from paths outside the intended export directory when '../' sequences are used.

You are affected if ruvnet sublinear-time-solver v1.5.0 is installed with the MCP server interface enabled and the export_state function exposed, and the path traversal test reveals files outside the intended directory are accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the export_state function to ensure path parameters cannot contain directory traversal sequences ('../' or '..\'). Use allowlist-based validation or resolve paths and verify they remain within an allowed base directory before file operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data