CVE-2026-134289

SurrealDB CLI help exposed credentials for MCP and other commands

SurrealDB · SurrealDB CLI · MCP and ML commands

First documented disclosure · Review checkpoint

Summary

CLI help could print passwords and tokens inherited from environment variables.

Severity and exploitation evidence

Medium · 4.1/10 · CVSS 4.0. Severity source.

Exploitation not established: The reviewed sources document a weakness or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Credential arguments omitted clap hide_env_values, exposing SURREAL_PASS and SURREAL_TOKEN in help output.

Conditions required

A user runs help with a secret populated in the environment and the output reaches another person through logs, screenshots or support material.

Potential impact

Accidental disclosure of database credentials to recipients of the output.

Affected versions and configurations

CNA: 1.0.0 before 4.0.0. The maintainer tested 2.7.0 and 3.2.0–3.3.4, inspected earlier argument definitions, and notes that 2.7.0 has no MCP subcommand.

Fix and mitigation status

4.0.0; correction 2afc241798 hides environment values on the affected credential arguments.

Practical next steps

Upgrade to 4.0.0 and rotate any credentials exposed in shared help output.

Operating lesson

Help and diagnostics must redact secrets even when the operator already possesses them.

Evidence and limits

Original advisory and correction November 3; CNA ingestion November 21. The advisory describes seven CLI commands, including MCP and ML import/export. This is an accidental disclosure boundary, not escalation for the user already able to read the environment. VulnCheck assigns CVSS 4.0 4.1 and CVSS 3.1 4.0; the maintainer labels the issue Low. The referenced commit and 4.0.0 release were reviewed. Apparent PR numbers 2035/2042 resolve to unrelated older issues, so they were not used to backdate either SurrealDB disclosure.

Sources