dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-55448

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges 8 weeks old

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
mise manages dev tools like node, python, cmake, and terraform. From 2026.3.15 until 2026.6.4, mise loads github.credential_command from local project config before any trust decision, then executes that value with sh -c when resolving a GitHub token. An attacker who can place a .mise.toml in a repository can execute arbitrary shell commands when the victim runs a GitHub-related mise command and no higher-priority GitHub token environment variable is set. This vulnerability is fixed in 2026.6.4.

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

The vulnerability allows command injection through mise's local project configuration. An attacker who can place a malicious .mise.toml file with a github.credential_command can execute arbitrary shell commands when victims run GitHub-related mise commands without a higher-priority token environment variable set. The fix requires not loading credential_command from untrusted local configs before trust validation.

MitigationUpdate mise to version 2026.6.4 or later. Avoid placing .mise.toml files in untrusted repositories and use environment variables (e.g., GITHUB_TOKEN) for GitHub credentials instead of configuration files.

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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Check mise version
    Run `mise --version` or `mise -V` to get the installed version number
    Affected if Version is earlier than 2026.6.4
  2. Locate .mise.toml files
    Search for .mise.toml files in the current directory and parent directories: `find . -name '.mise.toml' -o -name 'mise.toml'`
    Affected if A .mise.toml file exists in the project or any parent directory
  3. Inspect for github.credential_command
    Open the found .mise.toml files and look for a [github] or [github.credential_command] section, or search with `grep -r 'credential_command' .mise.toml`
    Affected if The file contains a github.credential_command configuration directive
  4. Check for higher-priority token
    Verify if GITHUB_TOKEN, MISE_GITHUB_TOKEN, or GH_TOKEN environment variables are set by running `env | grep -iE 'GITHUB_TOKEN|MISE_GITHUB_TOKEN|GH_TOKEN'`
    Affected if No GitHub token environment variable is set (the credential_command would be used as fallback)
  5. Verify trust validation status
    Check if the directory is marked as trusted by mise: `mise trust --list` or look for .mise.toml trust markers
    Affected if The directory with the .mise.toml is NOT marked as trusted by mise

You are affected if running mise version < 2026.6.4 with an untrusted local .mise.toml containing github.credential_command while lacking a GITHUB_TOKEN environment variable.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update mise to version 2026.6.4 or later. Avoid placing .mise.toml files in untrusted repositories and use environment variables (e.g., GITHUB_TOKEN) for GitHub credentials instead of configuration files.

Recommended fix High confidence

2026.6.4

  1. Upgrade mise to version 2026.6.4 or later by running the appropriate installation command for your system (e.g., mise self-update, brew upgrade mise, or downloading from the official releases)
  2. Verify the installation was successful by running: mise --version
  3. Ensure GitHub token authentication uses environment variables (GITHUB_TOKEN or GITHUB_TOKEN_FILE) rather than relying on credential_command from config files
  4. Review any project .mise.toml files for suspicious github.credential_command entries before running mise commands in untrusted repositories

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55448 — 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-55448 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