Metalama.Framework: Metalama allows local code execution through DLL planting in shared temporary directories (CVE-2026-62847)
Description
Metalama.Framework versions before 2026.1.19 load and execute compile-time assemblies and helper tools from predictable temporary directories on Linux and macOS. These directories are world-writable system temp locations, allowing a local unprivileged user to plant malicious DLLs that get executed by higher-privileged build or IDE processes. This results in local privilege escalation and arbitrary code execution. Windows default configurations are not affected due to per-user temp directory protections. The issue is fixed in version 2026.1.19 by relocating caches to per-user application data directories.
CVSS v3.1
Score 8.2high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Metalama.Framework versions prior to 2026.1.19 on Linux and macOS use the world-writable system temporary directory for caching compile-time assemblies, auxiliary tools, and embedded helper assemblies. The presence of a sentinel file causes Metalama to trust and load these artifacts without integrity verification. An unprivileged local user can pre-create the cache directory structure and plant malicious DLLs with matching sentinel files. When a higher-privileged user runs a build, Metalama loads and executes the attacker-supplied assemblies within the compiler or IDE process, leading to arbitrary code execution with the victim's privileges. Windows is not affected due to OS ACL protections on per-user temp directories. The vulnerability is fixed in version 2026.1.19 by moving caches to per-user application data locations, leveraging OS-enforced ownership.
Potential Impact
Allows local privilege escalation on shared POSIX systems by enabling an unprivileged user to execute arbitrary code in the security context of a higher-privileged user running Metalama builds or IDE processes. This can lead to reading sensitive source code or secrets, tampering with build outputs, supply-chain injection, or disruption of build processes. Windows default configurations are not impacted. The CVSS v3.1 score is 8.2 (High), reflecting the cross-user privilege escalation and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available in Metalama.Framework and Metalama.Tool version 2026.1.19. Users should upgrade to this version or later to ensure caches and extraction directories are stored in per-user application data locations, preventing DLL planting attacks. No additional action is required if already running 2026.1.19 or later. Avoid configuring the METALAMA_TEMP environment variable to point to insecure or world-writable locations, as this is a deployment misconfiguration rather than a product defect.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m6wq-39m7-9xpp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-62847"]
- Ecosystems
- ["NuGet"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ad008bc2cdf04f656b917b8
Added to database: 10/14/2026, 22:57:00 UTC
Last enriched: 10/14/2026, 23:05:54 UTC
Last updated: 10/14/2026, 23:05:54 UTC
Views: 7
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.
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.