CVE-2026-62847
HIGHDescription
Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. Prior to 2025.1.18, 2026.0.25 and 2026.1.19, Metalama.Framework and Metalama.Tool load and execute compile-time assemblies, auxiliary executable tools and embedded helper assemblies from predictable temporary directories. On `Linux` and `macOS`, the default `Path.GetTempPath()` location is world-writable, and existing artifacts are trusted based on sentinel or `.completed` marker files rather than integrity verification. A local unprivileged user on a shared machine or CI/build agent can pre-create the deterministic directory structure and plant a malicious DLL with the matching sentinel. When a higher-privileged developer or build account subsequently builds, Metalama skips regeneration and executes the planted artifact in the compiler, IDE or MSBuild process as the building user. This permits cross-user privilege escalation, reading source and secrets, supply-chain tampering with build output, or disrupting builds. Default Windows per-user temporary directories are protected by ACLs and are not affected. Deployer-selected insecure cache locations are outside the vulnerability's scope. This issue is fixed in versions 2025.1.18, 2026.0.25 and 2026.1.19.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-377 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-5224 | Critical | 9.8 | 4.5% | - | Fix |
| CVE-2026-20204 | High | 7.1 | 3.1% | - | Fix |
| CVE-2018-3710 | High | 7.8 | 2.8% | - | Fix |
| CVE-2017-16024 | Medium | 6.5 | 2.5% | - | Fix |
| CVE-2012-2666 | Critical | 9.8 | 1.9% | - | - |
| CVE-2018-16494 | High | 8.8 | 1.9% | - | Fix |
Common questions
How do I fix CVE-2026-62847?
No published fix for CVE-2026-62847 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-62847?
CVE-2026-62847 has a CVSS v3 base score of 8.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-62847
Markdown
[](https://tridentstack.com/cve/CVE-2026-62847)HTML
<a href="https://tridentstack.com/cve/CVE-2026-62847"><img src="https://tridentstack.com/cve/badge/CVE-2026-62847.svg" alt="CVE-2026-62847"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-30.