Metalama
Monthly
Unsafe deserialization in Metalama's Visual Studio design-time named-pipe channel lets a process already running as the same logged-in Windows user send a crafted message that instantiates arbitrary .NET types and achieves code execution inside devenv, the out-of-process Roslyn code-analysis process, or the CodeLens process. Affected are Metalama.Framework NuGet releases from 2023.0.101-rc onward (fixed in 2025.1.18, 2026.0.25 and 2026.1.19), the maintained 'Metalama + PostSharp' Visual Studio extension 2024.1 through 2026.1.4 (fixed in 2026.1.5), and all versions of the retired Metalama and Caravela extensions, which will not be patched. Because default Windows pipe ACLs only allow same-user writers, this is not a privilege escalation and command-line/MSBuild-only builds are unaffected; no public exploit code is identified at time of analysis and there is no CISA KEV entry.
Unsafe deserialization in Metalama's Visual Studio design-time named-pipe channel lets a process already running as the same logged-in Windows user send a crafted message that instantiates arbitrary .NET types and achieves code execution inside devenv, the out-of-process Roslyn code-analysis process, or the CodeLens process. Affected are Metalama.Framework NuGet releases from 2023.0.101-rc onward (fixed in 2025.1.18, 2026.0.25 and 2026.1.19), the maintained 'Metalama + PostSharp' Visual Studio extension 2024.1 through 2026.1.4 (fixed in 2026.1.5), and all versions of the retired Metalama and Caravela extensions, which will not be patched. Because default Windows pipe ACLs only allow same-user writers, this is not a privilege escalation and command-line/MSBuild-only builds are unaffected; no public exploit code is identified at time of analysis and there is no CISA KEV entry.