CVE-2026-33646
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 · uneditedmise manages dev tools like node, python, cmake, and terraform. Prior to 2026.3.10, mise processes .tool-versions files through the Tera template engine during parsing, with the exec() function registered, enabling arbitrary command execution. Unlike .mise.toml files, .tool-versions files are not subject to trust verification in non-paranoid mode. This means an attacker can place a malicious .tool-versions file in a git repository, and when a victim with mise activated cds into the directory, arbitrary commands execute without any trust prompt. This vulnerability is fixed in 2026.3.10.
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 confidencemise processes .tool-versions files through the Tera template engine with the exec() function enabled, allowing arbitrary command execution. Unlike .mise.toml files, .tool-versions files bypass trust verification in non-paranoid mode, enabling attackers to execute commands by placing malicious .tool-versions files in git repositories that victims clone and navigate to with mise activated.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed mise versionRun 'mise --version' or 'mise -V' to determine the currently installed versionAffected if Version is earlier than 2026.3.10 (e.g., 2026.3.9, 2026.2.x, etc.)
-
Check paranoid mode statusRun 'mise config get paranoid' or inspect the configuration file (~/.config/mise/config.toml or project .mise.toml) for the 'paranoid' settingAffected if Paranoid mode is disabled or not set to true (non-paranoid mode)
-
Locate .tool-versions files in useSearch for .tool-versions files in the current working directory and parent directories using 'ls -la' or find the project root with 'mise dir'Affected if A .tool-versions file exists in a directory that was cloned from a git repository or obtained from an untrusted source
You are affected if you are running mise versions before 2026.3.10, have paranoid mode disabled, and navigate to directories containing .tool-versions files from potentially untrusted git repositories.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate mise to version 2026.3.10 or later to patch the vulnerability. Consider using paranoid mode as an additional safeguard until the update is deployed.
2026.3.10
- Check the current installed version of mise by running: mise --version
- Upgrade mise to version 2026.3.10 or later by following the installation instructions at https://github.com/jdx/mise
- Verify the upgrade was successful by running: mise --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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