GHSA-43hx-4j66-v486 json
Untrusted project config can place a repository directory first on PATH via trust-exempt `path:` tool version
published 19d ago modified 19d ago
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository jdx/mise. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of jdx/mise: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- jdx mise 2026.10.14
Is GHSA-43hx-4j66-v486 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerInferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| npm | mise | jdx/mise | no versions given |
Affected products
- jdx mise
Classification
- Technology feeds
References
Sources
- Maintainer advisory GHSA-43hx-4j66-v486
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of jdx/mise published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.