SurrealDB credential disclosure in CLI help output
Affects SurrealDB 1.0.0 before 4.0.0 when the SURREAL_PASS or SURREAL_TOKEN environment variables are set, as in container deployments. Fixed in 4.0.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.0
- Who is exposed
- Specific setups only
Summary
Written by a model
SurrealDB 1.0.0 before 4.0.0 prints SURREAL_PASS and SURREAL_TOKEN environment variable values in clear text in the --help and -h output of CLI commands such as surreal start, sql, import, export, and mcp, because the arguments do not set clap's hide_env_values. Anyone who later sees that terminal output, for example in shell logs, CI logs, or screen shares, can obtain root database credentials.
Who should check
Teams running SurrealDB 1.0.0 through 3.x, including Rust crate users of surrealdb, and operators whose containers pass SURREAL_PASS or SURREAL_TOKEN as environment variables.
“Affecting surrealdb >= 1.0.0, < 4.0.0”
What to do
Check whether your setup matches what the bug needs.
Affects SurrealDB versions from 1.0.0 before 4.0.0. SURREAL_PASS or SURREAL_TOKEN environment variables are set, as in container deployments. The --help or -h output of the affected CLI commands is run and shown.Upgrade to a fixed version: 4.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134289 (SurrealDB 1.0.0 before 4.0.0 Credential Disclosure via CLI Help Output), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134289 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 1.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Affects SurrealDB versions from 1.0.0 before 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-credential-disclosure-via-cli-help-output)
- SURREAL_PASS or SURREAL_TOKEN environment variables are set, as in container deployments. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-whfh-76h8-2r66)
- The --help or -h output of the affected CLI commands is run and shown. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-whfh-76h8-2r66)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, high-privilege login, a user action.
CISA KEV: CVE-2026-134289 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134289 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-whfh-76h8-2r66
- https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-credential-disclosure-via-cli-help-output
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134289
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134289"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach10/20Affects crates.io packages
- Severity4.1/10CVSS 4.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
Impact
- Widely usedsurrealdb has 46.1k weekly downloads. crates.io
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · surrealdb/surrealdb · Advisory GHSA-whfh-76h8-2r66 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134289 |
| Record | NVD · CVE-2026-134289 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-1.0.0-before-4.0.0-credential-disclosure-via-cli-help-output |
Questions about CVE-2026-134289
Is CVE-2026-134289 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The --help and -h output of seven SurrealDB CLI commands shows the current values of credential environment variables in clear text. Anyone who sees that terminal output, such as in shell logs, CI logs, or screen shares, can obtain root database credentials, the SURREAL_PASS and SURREAL_TOKEN values.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134289?
surrealdb (crates.io): from 1.0.0 before 4.0.0.
Source: cve.now feed data
Am I affected, and how do I check?
Affects SurrealDB versions from 1.0.0 before 4.0.0. The exposure needs SURREAL_PASS or SURREAL_TOKEN to be set, as in container deployments where a Kubernetes Secret or docker run -e puts them in the environment, and the --help or -h output of the affected commands to be run and shown. The version can be checked with the SurrealDB version command, and the environment can be checked for those two variables.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134289?
Upgrade SurrealDB to version 4.0.0 or later, which is the fixed version listed for this vulnerability.
Source: vulncheck.com, github.com
Related
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
- CVE-2026-134293SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks
- CVE-2026-121417SurrealDB before 3.3.0 Use-After-Free via affinitypool spawn_local in KV Backends
- CVE-2026-134291SurrealDB 3.0.0 before 4.0.0 Path Traversal via Filesystem Bucket Symlinks
- CVE-2026-134294SurrealDB 3.0.0 before 4.0.0 Path Traversal via Windows Backslashes in Bucket Keys
- CVE-2026-134295SurrealDB 3.0.0 before 4.0.0 Path Traversal in Direct Filesystem Buckets
No corrections so far. Something wrong on this page? Report an error.