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.
Original description
The description as published by the source.
Impact
Some of the Surface Controllers in the CMS provide to support member related operations fail to validate redirect URLs, making Razor templates that derive 'RedirectUrl' from user-controlled query parameters vulnerable to malicious redirect attacks.
Patches
The issue is resolved in versions 17.4.0 and 13.14.0.
Workarounds
If users cannot upgrade immediately, they can mitigate the issue in their own site by ensuring every Razor form that posts to UmbLoginStatusController, UmbProfileController or UmbRegisterController passes a concrete, trusted RedirectUrl into Html.BeginUmbracoForm's route values.
For example:
@using (Html.BeginUmbracoForm(
"HandleLogout",
new { RedirectUrl = Model.Url() }))
{
Log out
}
Resources
https://github.com/umbraco/Umbraco-CMS/pull/22565
https://github.com/umbraco/Umbraco-CMS/pull/22561
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-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.
A vulnerability (CWE-601) exists in Umbraco.Cms. Attackers reach the vulnerable code path via UmbLoginStatusController without authentication.
Check the vendor advisory for the affected versions of Umbraco.Cms. Attack surface: UmbLoginStatusController / UmbProfileController / UmbRegisterController / RedirectUrl.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 17.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Umbraco.Cms to 17.4.0ステージング環境で 17.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com