← Back
CVE-2026-26171
Vulnerability in dotnet (CVE-2026-26171)
Summary
vulnerability in dotnet (CVE-2026-26171). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8.0.26, 9.0.15, 10.0.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-26171** has been found in dotnet.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade dotnet to **8.0.26, 9.0.15, 10.0.6** or later.
If unsure, ask your IT team or search "dotnet CVE-2026-26171" on the vendor's site.
CVE-2026-26171 (dotnet) — CWE-400 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `8.0.26, 9.0.15, 10.0.6` — 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-400) exists in dotnet.
📍 Affected scope
dotnet — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.0.26, 9.0.15, 10.0.6**.
🛡️ 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 'dotnet' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dotnet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dotnet` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dotnet to 8.0.26, 9.0.15, 10.0.6ステージング環境で 8.0.26, 9.0.15, 10.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
dotnet
[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.0.26"},{"introduced":"9.0.0"},{"fixed":"9.0.15"},{"introduced":"10.0.0"},{"fixed":"10.0.6"}]}]
Bitnami
dotnet-sdk
[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.0.26"},{"introduced":"9.0.0"},{"fixed":"9.0.15"},{"introduced":"10.0.0"},{"fixed":"10.0.6"}]}]
Bitnami
powershell
[{"type":"SEMVER","events":[{"introduced":"7.5.0"},{"fixed":"7.5.6"},{"introduced":"7.6.0"},{"fixed":"7.6.1"}]}]
NuGet
System.Security.Cryptography.Xml
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-26171
- package https://github.com/dotnet/runtime
- web https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26171
- web https://github.com/dotnet/runtime/security/advisories/GHSA-w3x6-4m5h-cxqf
- web https://github.com/dotnet/announcements/issues/389