CVEsmetalamaCVE-2026-62847Published Oct 30, 20:23 · Updated Oct 30, 22:13 UTC
8.2
HighCVSS 3.1 · from GitHub_M
CVE-2026-62847

Metalama: Local code execution via DLL planting in world-writable temporary directories (Linux/macOS)

Metalama · CWE-377 · CWE-377
AffectedMetalama
FixNo fix listed yet.
PublishedOct 30, 20:23 · GitHub_M
ScoredOct 30 · 8.2 · GitHub_M
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:06 UTC

What we know

No known exploitation. CISA KEV, checked 22:06 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
An attacker needs local access to the machine. CVSS: local.
Someone has to open, click or run something first. CVSS: user interaction required.
A successful attack can read and change data and take the service down. CVSS: high impact on confidentiality, integrity and availability.
A successful attack gives full control of the affected system. CISA: technical impact total.

Description

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.

From GitHub_M

Affected and fixed versions

ProductAffectedFixed inMetalama< 2025.1.18–Metalama>= 2025.2.0-preview, <= 2025.2.5-rc–Metalama>= 2026.0.0-preview, < 2026.0.25–Metalama>= 2026.1.0-preview, < 2026.1.19–

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

github.com/metalama/Metalama/security/advisories/GHSA-m6wq-39m7-9xpp · github.comrefsource_CONFIRMgithub.com/metalama/Metalama/pull/1650 · github.comrefsource_MISCgithub.com/metalama/Metalama/commit/09911349a916e82194b1cfaa6d0a38acad928fc9 · github.comrefsource_MISCgithub.com/metalama/Metalama/commit/92c4feecfce86d18fcb007ab6d3a1b4383326a2e · github.comrefsource_MISCgithub.com/metalama/Metalama/releases/tag/release/2025.1.18 · github.comrefsource_MISCgithub.com/metalama/Metalama/releases/tag/release/2026.0.25 · github.comrefsource_MISCgithub.com/metalama/Metalama/releases/tag/release/2026.1.19 · github.comrefsource_MISC

Other CVEs in Metalama

All 1 →
7.3Metalama's Visual Studio inter-process named pipe allows unsafe deserialization that enables local code execution · CVE-2026-62848Oct 30