# Metalama: Unsafe deserialization over Metalama's Visual Studio inter-process named pipe enables local code execution

Advisory record · `GHSA-h26j-4vp7-x9w2`

- **Identifiers:** `GHSA-h26j-4vp7-x9w2` · `CVE-2026-62848`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html) · [CWE-913](https://cwe.mitre.org/data/definitions/913.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-913](https://agentprime.io/advisories/tag/cwe-913.md)
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Nov 2026, 16:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `Metalama.Framework` (NuGet): affected `>=2026.1.0-preview, <2026.1.19 || <2025.1.18 || >=2026.0.1-preview, <2026.0.25`; fixed in `2026.1.19`, `2025.1.18`, `2026.0.25`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.3 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 30 Oct 2026, 21:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-62848)
- 3 Nov 2026, 16:37 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-h26j-4vp7-x9w2)
- 3 Nov 2026, 16:45 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h26j-4vp7-x9w2)

## Sources

- [GitHub Advisory Database: GHSA-h26j-4vp7-x9w2](https://github.com/advisories/GHSA-h26j-4vp7-x9w2)
- [OSV: GHSA-h26j-4vp7-x9w2](https://osv.dev/vulnerability/GHSA-h26j-4vp7-x9w2)
- <https://github.com/metalama/Metalama/security/advisories/GHSA-h26j-4vp7-x9w2>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-62848>
- <https://github.com/metalama/Metalama/pull/1651>
- <https://github.com/metalama/Metalama/commit/5b4ced29f2b25631cc2e44d05b0fd5fe838b6cbe>
- <https://github.com/metalama/Metalama/commit/d97f52e1b53ffe4176b2b05c56ffdf1ccd2f53a9>
- <https://github.com/metalama/Metalama>
- <https://github.com/metalama/Metalama/releases/tag/release/2025.1.18>
- <https://github.com/metalama/Metalama/releases/tag/release/2026.0.25>
- <https://github.com/metalama/Metalama/releases/tag/release/2026.1.19>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h26j-4vp7-x9w2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h26j-4vp7-x9w2/>. Everything for agents: <https://agentprime.io/llms.txt>.