← Back
CVE-2026-46616
medium
CVSS 5.4
Open Redirect in Umbraco.Cms (CVE-2026-46616)
Summary
vulnerability in Umbraco.Cms (CVE-2026-46616). Risk of unauthorized operations or information disclosure. Exploitable via ``UmbLoginStatusController``. Mitigation: upgrade to `17.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46616** has been found in Umbraco.Cms.
Attackers can target a specific entry point like ``UmbLoginStatusController`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Umbraco.Cms to **17.4.0** or later.
If unsure, ask your IT team or search "Umbraco.Cms CVE-2026-46616" on the vendor's site.
CVE-2026-46616 (Umbraco.Cms) — CWE-601 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `UmbLoginStatusController` / `UmbProfileController` / `UmbRegisterController` / `RedirectUrl`
Patched: `17.4.0` — 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-601) exists in Umbraco.Cms. Attackers reach the vulnerable code path via ``UmbLoginStatusController`` without authentication.
📍 Affected scope
Umbraco.Cms — . Attack surface: `UmbLoginStatusController` / `UmbProfileController` / `UmbRegisterController` / `RedirectUrl`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **17.4.0**.
🛡️ 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 'Umbraco.Cms' .` 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 'Umbraco.Cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Umbraco.Cms` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Umbraco.Cms to 17.4.0ステージング環境で 17.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
Umbraco.Cms
[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.0-rc"},{"fixed":"17.4.0"}]}]