SECURITYHIGHCVE-2026-62848

CVE-2026-62848: Metalama Visual Studio Integration Unsafe Named-Pipe Deserialization

Metalama's Windows Visual Studio integration deserializes named-pipe messages without restricting CLR types, enabling local code execution (CVSS 7.3).

Dylan H.

Security Team

October 31, 2026
2 min read
CVE-2026-62848: Metalama Visual Studio Integration Unsafe Named-Pipe Deserialization

Affected Products

  • Metalama 2023.0.101-rc through 2025.1.18, 2026.0.25 and 2026.1.19 (Windows Visual Studio integration)

Summary

CVE-2026-62848 affects Metalama, an open-source Roslyn-based patterns and architecture toolkit for C#. It was published to the NVD on October 30, 2026 with a CVSS score of 7.3.

Details

From 2023.0.101-rc until 2025.1.18, 2026.0.25 and 2026.1.19, the Windows Visual Studio integration deserializes local named-pipe messages without restricting which CLR types can be instantiated. Unsafe deserialization of this kind lets a process able to write to the pipe cause attacker-chosen types to be instantiated inside the Visual Studio-side process.

ItemValue
CVECVE-2026-62848
CVSS7.3
VectorLocal named pipe
AffectedMetalama Visual Studio integration on Windows, versions listed above

Impact

A local, lower-privileged process on a developer workstation or build host could run code in the context of the developer's Visual Studio session, reaching source code, signing material and cloud credentials.

Remediation

  1. Update Metalama to a release newer than the affected builds; check the project's security advisory for the exact fixed versions.
  2. Until updated, avoid running untrusted processes on machines where the Metalama Visual Studio extension is active, including shared build hosts.
  3. Inventory developer workstations and CI agents that have the extension installed.

References