{"answers":{"affected":"2 open source packages ship an affected version, including mise. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35533 exists.","fix":"Upgrade mise to 2026.6.4 or later.","what":"CVE-2026-35533 is a high-severity vulnerability in jdx mise, published on 7 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-35533 and fix it if it is affected.\n\nWhat it is: CVE-2026-35533 is a high-severity vulnerability in jdx mise, published on 7 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35533 exists.\n\nAffected packages and fixed versions:\n- mise (crates.io): affected from 2026.2.18; fixed in 2026.6.4\n- mise (crates.io): affected from 2026.2.18; fixed in 2026.6.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-35533/ (Markdown: https://insights.sbomify.com/CVE-2026-35533/index.md)","id":"CVE-2026-35533","markdown":"https://insights.sbomify.com/CVE-2026-35533/index.md","name":"CVE-2026-35533","record":{"aliases":["GHSA-436v-8fw5-4mj8"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Dev tool manager","requires_auth":"none","summary":"Attackers can bypass trust checks in mise by placing a malicious config file, enabling execution of dangerous directives like hooks or tasks.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mise","vendor":"jdx"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mise has a local settings bypass config trust checks","id":"CVE-2026-35533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"ChurchCRM has Stored XSS in PersonView.php via Facebook Field Attribute Injection","id":"CVE-2026-35534"},"packages":[{"ecosystem":"crates.io","fixed":["2026.6.4"],"introduced":["2026.2.18"],"last_affected":[],"package":"mise","purl":null,"source":"GHSA-436v-8fw5-4mj8"},{"ecosystem":"crates.io","fixed":["2026.6.4"],"introduced":["2026.2.18"],"last_affected":[],"package":"mise","purl":"pkg:cargo/mise","source":"GHSA-436v-8fw5-4mj8"}],"prev":{"headline":"Incus blind SSRF via image import preflight HEAD request","id":"CVE-2026-35527"},"products":["mise"],"published":"2026-04-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["jdx"]},"summary":"Attackers can bypass trust checks in mise by placing a malicious config file, enabling execution of dangerous directives like hooks or tasks.","url":"https://insights.sbomify.com/CVE-2026-35533/"}