Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62847

Vulnerability in Metalama.Framework (CVE-2026-62847)

Summary

Vulnerability in Metalama.Framework (CVE-2026-62847). Risk of unauthorized operations or information disclosure. Exploitable via METALAMA_TEMP. Mitigation: upgrade to 2026.0.25 or later.

Original description

The description as published by the source.

Summary

Metalama loaded and executed compile-time assemblies, auxiliary executable tools, and embedded helper assemblies from predictable temporary directories. On Linux and macOS the default cache location was the world-writable system temporary directory (Path.GetTempPath(), i.e. /tmp), and previously-generated artifacts were trusted based on the presence of a sentinel/.completed marker file rather than on any integrity verification.

A local, unprivileged user on a shared machine or CI/build agent can pre-create the deterministic cache directory structure and plant a malicious DLL together with the matching sentinel file. When a higher-privileged user (or build/service account) subsequently runs a build, Metalama finds the sentinel, skips regeneration, and loads and executes the attacker-supplied assembly inside the compiler / IDE / MSBuild process.

Affected load-and-execute paths:

  • the cache of compile-time assemblies that Metalama generates from your aspects;
  • auxiliary executable tools that Metalama extracts to a local directory and then launches;
  • embedded .NET helper assemblies that Metalama extracts to a local directory and loads into the build / IDE process.

Impact

Arbitrary code execution in the security context of the building user — i.e. a local privilege escalation across user accounts on shared POSIX systems (multi-user developer machines, CI/build agents). The attacker obtains code execution as the victim without holding the victim's privile…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-62847 has been found in Metalama.Framework.
Attackers can target a specific entry point like METALAMA_TEMP over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Metalama.Framework to 2026.0.25 or later.
If unsure, ask your IT team or search "Metalama.Framework CVE-2026-62847" on the vendor's site.

CVE-2026-62847 (Metalama.Framework) — CWE-377
Attack surface: METALAMA_TEMP
Patched: 2026.0.25 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-377) exists in Metalama.Framework. Attackers reach the vulnerable code path via METALAMA_TEMP.

📍 Affected scope

Check the vendor advisory for the affected versions of Metalama.Framework. Attack surface: METALAMA_TEMP.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2026.0.25.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Metalama.Framework' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Metalama.Framework' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Metalama.Framework を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Metalama.Framework to 2026.0.25

    ステージング環境で 2026.0.25 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget Metalama.Framework
[{"type":"ECOSYSTEM","events":[{"introduced":"2026.0.0-preview"},{"fixed":"2026.0.25"}]}]
nuget Metalama.Tool
[{"type":"ECOSYSTEM","events":[{"introduced":"2026.0.0-preview"},{"fixed":"2026.0.25"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details