CVE-2026-46616: Umbraco.Cms: Open Redirect Vulnerability in Surface Controllers

Published May 21, 2026
·
Updated

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:

cshtml @using (Html.BeginUmbracoForm<UmbLoginStatusController>( "HandleLogout", new { RedirectUrl = Model.Url() })) { <button type="submit">Log out</button> }

Resources

https://github.com/umbraco/Umbraco-CMS/pull/22565 https://github.com/umbraco/Umbraco-CMS/pull/22561

Other sources

Umbraco is an ASP.NET CMS. Prior to versions 13.14.0 and 17.4.0, 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. This issue has been patched in versions 13.14.0 and 17.4.0.

MITRE

Affected Software

4 affected componentsFixes available
nuget/Umbraco.Cms>=17.3.0-rc<17.4.0
17.4.0
nuget/Umbraco.Cms<13.14.0
13.14.0
Umbraco Umbraco CMS<13.14.0
Umbraco Umbraco CMS>=14.0.0<17.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade nuget/Umbraco.Cms to a version that resolves this vulnerability.

    Fixed in 17.4.0
  2. Upgrade

    Upgrade nuget/Umbraco.Cms to a version that resolves this vulnerability.

    Fixed in 13.14.0
  3. Configuration

    Ensure every Razor form that posts to UmbLoginStatusController, UmbProfileController, or UmbRegisterController provides a concrete, trusted RedirectUrl in the Html.BeginUmbracoForm route values (do not pass RedirectUrl derived directly from user-controlled query parameters). For example, pass a Model.Url() or other server-validated URL as the RedirectUrl route value.

    Razor forms (Html.BeginUmbracoForm) RedirectUrl = concrete, trusted URL

Event History

May 21, 2026
Advisory Published
via GitHub·07:58 PM
Data Sourced
via GitHub·07:58 PM
DescriptionSeverityWeaknessAffected Software
Jun 10, 2026
CVE Published
via MITRE·03:56 PM
Data Sourced
via MITRE·03:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-46616?

CVE-2026-46616 has a medium severity rating of 5.4.

2

What risks are associated with CVE-2026-46616?

CVE-2026-46616 allows for malicious redirect attacks due to improper validation of redirect URLs.

3

How do I fix CVE-2026-46616?

The issue in CVE-2026-46616 is resolved in the latest version of Umbraco.Cms.

4

Which versions of Umbraco.Cms are affected by CVE-2026-46616?

CVE-2026-46616 affects versions of Umbraco.Cms that do not implement the latest security patches.

5

When was CVE-2026-46616 published?

CVE-2026-46616 was published on May 21, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203