CVE-2026-62848: Metalama: Unsafe deserialization over Metalama's Visual Studio inter-process named pipe enables local code execution
Metalama uses a local named-pipe channel to communicate between its Visual Studio processes — the Visual Studio UI process (devenv), the out-of-process Roslyn code-analysis process, and the CodeLens process. This channel deserialized messages from the pipe without restricting which CLR types could be instantiated. A local process able to write to the pipe can send a crafted message that instantiates arbitrary .NET types — a deserialization primitive in the same class as BinaryFormatter (CWE-502), and a well-known gadget-chain code-execution vector.
The flaw is present, via two successive serializers, in every Metalama release from the first public version (2023.0) up to and including 2026.1.18, and is fixed in 2026.1.19.
The pipe name is predictable: Metalama_{role}_{processId}_{hash(PackageVersion)}, derived from the public package version and a locally-enumerable process id. This channel is used by the Visual Studio integration only (Windows named pipes); it is not used for command-line / MSBuild builds.
References
- github.com/advisories/GHSA-h26j-4vp7-x9w2
- github.com/metalama/Metalama/commit/5b4ced29f2b25631cc2e44d05b0fd5fe838b6cbe
- github.com/metalama/Metalama/commit/d97f52e1b53ffe4176b2b05c56ffdf1ccd2f53a9
- github.com/metalama/Metalama/pull/1651
- github.com/metalama/Metalama/releases/tag/release/2025.1.18
- github.com/metalama/Metalama/releases/tag/release/2026.0.25
- github.com/metalama/Metalama/releases/tag/release/2026.1.19
- github.com/metalama/Metalama/security/advisories/GHSA-h26j-4vp7-x9w2
- nvd.nist.gov/vuln/detail/CVE-2026-62848
Code Behaviors & Features
Detect and mitigate CVE-2026-62848 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →