CVE-2026-35533: CWE-284: Improper Access Control in jdx mise
mise manages dev tools like node, python, cmake, and terraform. From 2026.2.18 through 2026.4.5, mise loads trust-control settings from a local project .mise.toml before the trust check runs. An attacker who can place a malicious .mise.toml in a repository can make that same file appear trusted and then reach dangerous directives such as [env] _.source, templates, hooks, or tasks.
AI Analysis
Technical Summary
The vulnerability in jdx mise arises because the software loads trust-control settings from a local .mise.toml file before the trust verification process completes. This allows an attacker who can place a malicious .mise.toml file in a repository to have that file treated as trusted. Consequently, the attacker can leverage this trust to execute potentially dangerous directives including environment variable source injection, templates, hooks, or tasks. The affected versions are from 2026.2.18 through 2026.4.5. The CVSS 3.1 vector indicates the attack requires local access with high attack complexity, no privileges, and user interaction, but results in high confidentiality, integrity, and availability impact.
Potential Impact
Successful exploitation allows an attacker with the ability to place a malicious .mise.toml file in a repository to bypass trust controls and execute dangerous directives. This can lead to full compromise of confidentiality, integrity, and availability of the affected system or environment where mise is used. The vulnerability is rated high severity with a CVSS score of 7.8.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should restrict write access to repositories and carefully control who can add or modify .mise.toml files to prevent malicious files from being introduced. Avoid running mise in environments where untrusted users can place or modify project files.
CVE-2026-35533: CWE-284: Improper Access Control in jdx mise
Description
mise manages dev tools like node, python, cmake, and terraform. From 2026.2.18 through 2026.4.5, mise loads trust-control settings from a local project .mise.toml before the trust check runs. An attacker who can place a malicious .mise.toml in a repository can make that same file appear trusted and then reach dangerous directives such as [env] _.source, templates, hooks, or tasks.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jdx mise arises because the software loads trust-control settings from a local .mise.toml file before the trust verification process completes. This allows an attacker who can place a malicious .mise.toml file in a repository to have that file treated as trusted. Consequently, the attacker can leverage this trust to execute potentially dangerous directives including environment variable source injection, templates, hooks, or tasks. The affected versions are from 2026.2.18 through 2026.4.5. The CVSS 3.1 vector indicates the attack requires local access with high attack complexity, no privileges, and user interaction, but results in high confidentiality, integrity, and availability impact.
Potential Impact
Successful exploitation allows an attacker with the ability to place a malicious .mise.toml file in a repository to bypass trust controls and execute dangerous directives. This can lead to full compromise of confidentiality, integrity, and availability of the affected system or environment where mise is used. The vulnerability is rated high severity with a CVSS score of 7.8.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should restrict write access to repositories and carefully control who can add or modify .mise.toml files to prevent malicious files from being introduced. Avoid running mise in environments where untrusted users can place or modify project files.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-03T02:15:39.281Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d5743aaaed68159a661746
Added to database: 4/7/2026, 9:16:42 PM
Last enriched: 4/7/2026, 9:31:09 PM
Last updated: 4/8/2026, 12:43:44 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.