CVE-2026-62848

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-11-03. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-114449 (ENISA EUVD) · GHSA-h26j-4vp7-x9w2 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. 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. The pipe connects devenv, the out-of-process Roslyn code-analysis process and the CodeLens process, and has the predictable name Metalama_{role}_{processId}_{hash(PackageVersion)}. Releases from the first public 2023.0 line through 2026.0.x use Newtonsoft.Json with TypeNameHandling.All; the later SerializationBinder only remaps assembly names, and BindToType resolves arbitrary wire-supplied types without an allow-list. Releases 2026.1.0 through 2026.1.18 use typeless MessagePack with TypelessObjectResolver and likewise instantiate arbitrary types. A same-user local process able to write to the pipe can send crafted messages that lead to arbitrary code execution with confidentiality, integrity and availability impacts inside the affected Visual Studio process. Default Windows pipe ACLs limit writers to the same logged-in user, so this does not escalate privileges or cross a security boundary; command-line and MSBuild-only builds do not use the channel. The maintained Metalama + PostSharp extension is affected from 2024.1 through 2026.1.4, while earlier Metalama-free PostSharp versions are unaffected. The retired Metalama and Caravela extensions remain affected and require removal or migration. The framework issue is fixed in versions 2025.1.18, 2026.0.25 and 2026.1.19; the maintained Metalama + PostSharp Visual Studio extension is fixed in version 2026.1.5. The retired Metalama and Caravela extensions require removal or migration.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

November 6, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit d97f52e1b53f (metalama/Metalama)

Patch available: metalama/Metalama release/2026.1.19 (contains commit d97f52e1b53f)

https://github.com/metalama/Metalama/commit/d97f52e1b53ffe4176b2b05c56ffdf1ccd2f53a9
GitHub commit Patch Available

commit 5b4ced29f2b2 (metalama/Metalama)

Patch available: metalama/Metalama release/2025.1.18 (contains commit 5b4ced29f2b2)

https://github.com/metalama/Metalama/commit/5b4ced29f2b25631cc2e44d05b0fd5fe838b6cbe
GitHub advisoryMentions a patch (unverified)

Unsafe deserialization over Metalama's Visual Studio inter-process named pipe enables local code execution · Advisory · metalama/Metalama · GitHub

https://github.com/metalama/Metalama/security/advisories/GHSA-h26j-4vp7-x9w2

Vendor Advisories for CVE-2026-62848(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetMetalama.Framework @ 2026.0.25 (fixes >= 2026.0.1-preview, < 2026.0.25)—ghsa
nugetMetalama.Framework @ 2026.1.19 (fixes >= 2026.1.0-preview, < 2026.1.19)—ghsa
nugetMetalama.Framework @ 2025.1.18 (fixes < 2025.1.18)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
Metalama.Framework2026.0.1-preview ... 2026.0.9-rc (24 versions)
  • 2026.1.0-preview up to 2026.1.19: fixed in 2026.1.19
  • every version up to 2025.1.18: fixed in 2025.1.18
  • 2026.0.1-preview up to 2026.0.25: fixed in 2026.0.25
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-06 19:27 UTCEchelonGraph re-scored
  8. 2026-11-06 19:27 UTCGHSA enrichmentGHSA-h26j-4vp7-x9w2 · GitHub severity HIGH · GitHub CVSS 7.3
  9. 2026-11-06 18:23 UTCEchelonGraph re-scored
  10. 2026-11-06 18:23 UTCGHSA enrichmentGHSA-h26j-4vp7-x9w2 · GitHub severity HIGH · GitHub CVSS 7.3
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-11-02 19:46 UTCEchelonGraph re-scored
  16. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-30 22:02 UTCENISA EUVD ID recordedEUVD-2026-114449 · Source: ENISA EUVD
  20. 2026-10-30 21:26 UTCEchelonGraph re-scored
  21. 2026-10-30 20:29 UTCEchelonGraph re-scoredFirst assessed: 7.3 HIGH
  22. 2026-10-30 20:28 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

NuGet:Metalama.Framework

Frequently asked(5)

What is CVE-2026-62848?
CVE-2026-62848 is a high-severity vulnerability; its CVE record was published on October 30, 2026. Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. 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. The pipe connects…
When was the CVE record for CVE-2026-62848 published?
The CVE record for CVE-2026-62848 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-62848 actively exploited?
CVE-2026-62848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62848?
CVE-2026-62848 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62848?
A fix for CVE-2026-62848 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62848 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62848

Explore →

Is Your Infrastructure Affected by CVE-2026-62848?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs