The November 17 Umbraco security update fixes seven vulnerabilities, five rated High and two Moderate. They sit in Umbraco CMS, Umbraco Workflow, Umbraco Commerce, Umbraco Engage and the Umbraco MCP Server SDK. Umbraco published the patches on November 17, the date it gave in a November 12 heads-up, which set the release for 08:00 UTC.
Umbraco’s Security Advisory post for November 17 lists the fixed versions and the steps to take after upgrading. Each issue also has its own GitHub advisory. This post sorts them by what to update first, explains who is exposed, and covers the versions that get no patch.
The short version: if you run a hosted MCP server built on Umbraco’s SDK, update it first. Then patch Workflow and Commerce, and rotate payment gateway secrets if you cannot rule out misuse. Umbraco Cloud upgrades the CMS for you, but not the add-ons or the MCP server. Sites on Umbraco 12, 14 or 15 get no CMS patch and need a major upgrade.
Status as of 4:40 a.m. ET, November 17: all seven advisories are public on GitHub and on Umbraco’s blog. None has a CVE ID yet. Each GitHub advisory reads "No known CVE." They were not yet in GitHub’s global advisory database when we checked.
What the Umbraco security update fixes
| Product | Issue and advisory | Severity | Fixed in |
|---|---|---|---|
| MCP Server SDK | Cross-site request forgery in the hosted server’s consent step (GHSA-9hv2-2794-vp6f) | High, 8.1 | @umbraco-cms/mcp-hosted 1.0.0-beta.48 |
| Workflow | SQL injection in back-office searches (GHSA-7457-w8c8-jh29) | High, 8.1 | 13.5.5, 17.6.0, 18.3.0 |
| Workflow | Content approval bypass (GHSA-vw5g-jmgg-hw78) | High, 7.6 | 13.5.5, 17.6.0, 18.3.0 |
| Commerce | Missing access checks expose payment settings and orders (GHSA-cw69-92rj-fp3r) | High, 8.1 | 13.3.4, 17.2.13, 18.1.13, 19.0.0-rc.2 |
| Engage | Missing authorization in the Engage API (GHSA-gq5w-hprc-q59x) | High, 8.3 | 13.8.3, 17.6.0, 18.3.0 |
| CMS 13 | Delivery API exposes protected content through pickers (GHSA-5pr6-xx84-wp49) | Moderate, 5.3 | 13.16.5 |
| CMS 17 and 18 | Sensitive member data in the members index (GHSA-348f-9mg8-rhv4) | Moderate, 4.9 | 17.8.2, 18.3.2 |
The numbers are CVSS 3.1 base scores from each GitHub advisory. Our guide to reading a CVSS score explains the vector strings. If advisory IDs are new to you, see what a CVE is.
Who is exposed by the Umbraco security update
Five of the seven issues need a back-office login. That sounds reassuring, but many association and nonprofit sites give back-office accounts to dozens of editors, volunteers and agency staff. These bugs let any of those accounts reach data or actions their role was never meant to have.
Two issues can be used without an Umbraco account:
- The hosted MCP server. The person who gains access needs no account. A back-office user with a current sign-in has to open their link.
- The Delivery API on Umbraco 13. Umbraco says "no login is required if the Delivery API is publicly accessible." The Delivery API is off by default.
Umbraco Cloud. Cloud installs the CMS part of the Umbraco security update for you. Umbraco says an automatic upgrade "will be rolled out today" for the CMS fixes. Workflow, Commerce and Engage are add-ons, so Cloud customers must patch them by hand. A hosted MCP server runs outside Umbraco Cloud and also needs a manual upgrade.
Self-hosted sites need every part of the Umbraco security update applied by your team or partner. Use your normal NuGet upgrade path.
Update first: the hosted MCP server
According to the GHSA-9hv2-2794-vp6f advisory, the consent screen in @umbraco-cms/mcp-hosted did not check that an approval came from the person who saw it. Its form token was tied to the MCP client, not to the user’s browser. Anyone could register a client and get such a token without signing in.
If a signed-in back-office user opened an attacker’s link, an unknown MCP client could get a session acting as that user. With default settings, that works if the user signed in or loaded a back-office page in the last 20 minutes. The session can read and change whatever that user can, through the tools the server has turned on. For an administrator, that includes admin actions.
Affected versions are 17.0.0-beta.5 to 17.0.0-beta.29 and 1.0.0-beta.30 to 1.0.0-beta.47. The fix is in 1.0.0-beta.48. The advisory lists no patch for the 17.0.0-beta line, so move to 1.0.0-beta.48.
Umbraco’s hosted MCP documentation says the package prepares an MCP server for Cloudflare Workers. Users sign in as back-office users through OAuth. Sites that do not run a hosted MCP server are not affected. Until you upgrade, Umbraco suggests limiting MCP client registration to clients you trust. It also asks back-office users not to open unexpected links while signed in.
Why a CMS patching its own MCP server matters
This is the first Umbraco security update we have seen with a High fix for its own MCP tooling. In August we looked at what each CMS lets agents do. Umbraco’s hosted server keeps agents in bounds with the user’s own back-office permissions and a consent screen where users approve each MCP client.
This bug sat in that consent step. Permissions still applied, but the approval itself could be forged. The result is an agent session with the user’s full rights.
For agencies building MCP servers for clients, three checks follow from the advisory:
- Know which MCP servers exist and who deployed them. A hosted server may sit in a separate Cloudflare account.
- Limit client registration. The project template lets any MCP client register by default.
- Scope tools. The session gets only the tools the operator enabled, so fewer tools means less damage.
Our post on the first MCP flaw added to CISA’s KEV catalog covers a similar failure in an authentication check. Our look at agent write access in CMS platforms covers the wider picture.
Next: Workflow and Commerce
Umbraco Workflow, SQL injection. Per the GHSA-7457-w8c8-jh29 advisory, several Workflow searches and filters put request values straight into the query text. Any back-office user, not only admins, could read data from the whole Umbraco database. Depending on the database account’s rights, they could also change it. Umbraco says every site on an affected version is exposed, because the approval group search exists on every install.
Umbraco Workflow, approval bypass. The second Workflow advisory, GHSA-vw5g-jmgg-hw78, says permissions were applied only in the back-office screens. Any back-office user could change approval groups and settings, read workflow history, and approve pending changes. After upgrading, check that custom user groups have the Workflow permissions their users need.
Umbraco Commerce. The GHSA-cw69-92rj-fp3r advisory says many back-office API functions only checked that the user was signed in. A user with access to the Content section only could see payment method settings, including the payment gateway’s secret keys. They could also see shopper names, emails and addresses, and gift card codes. A user limited to one store could change orders and payments in other stores.
Upgrade Commerce, then rotate payment gateway secret keys and webhook signing secrets if you cannot rule out misuse. Commerce 19.0.0-rc.1 is also affected, fixed in rc.2.
Then: Engage and the two CMS issues
Umbraco Engage. The GHSA-gq5w-hprc-q59x advisory says Engage applied its permissions in the back-office screens only. Any back-office user could view visitor profiles, including linked members’ names and emails. They could also change Engage tests, personalization and settings. In 17.5.0 and 18.2.0, some functions could publish pending page changes without content permission.
CMS 13, Delivery API. The GHSA-5pr6-xx84-wp49 advisory calls this an incomplete fix for CVE-2026-69197, patched in July. The Delivery API could still return Public Access content, or content types excluded from the API, when referenced through a Content Picker or Multi-Node Tree Picker. Only sites with the Delivery API turned on and such references are affected. This matters most on headless builds. Umbraco 17 and 18 are not affected. Fixed in 13.16.5.
CMS 17 and 18, members index. The GHSA-348f-9mg8-rhv4 advisory says that since 17.4.0, sensitive member properties were stored in the members search index. Users with the Settings and Members sections, but not the Sensitive data group, could read them. Reads only, no changes. Fixed in 17.8.2 and 18.3.2. After upgrading, rebuild the Members index from the Examine Management dashboard. Cloud sites need this step too.
Versions that get no patch
For the CMS, that means sites on 12.x and 14.0.0 to 15.4.4 stay open to the Delivery API issue. Umbraco’s LTS and end-of-life page lists Umbraco 13 at end of life on December 14, 2026. That leaves Umbraco 13 less than a month of support after this Umbraco security update. Our post on .NET 8 end of support and Umbraco 13 covers that deadline.
| Version | Type | Security phase ends | End of life |
|---|---|---|---|
| Umbraco 13 | LTS | Dec 14, 2025 | Dec 14, 2026 |
| Umbraco 17 | LTS | Nov 27, 2027 | Nov 27, 2028 |
| Umbraco 18 | STS | Mar 25, 2027 | Jun 25, 2027 |
| Umbraco 19 (planned) | STS | Sep 10, 2027 | Dec 10, 2027 |
Umbraco 19 is not a reason to wait. Umbraco’s release candidate post says 19.0.0-rc1 shipped November 12, targets .NET 11, and plans a final release on December 10. It is a short-term release, supported until December 2027. For most organizations on 13, Umbraco 17 LTS is the safer target.
How to apply the Umbraco security update
- List what you run. Check the CMS version and every Umbraco add-on in each project, plus any hosted MCP server.
- Patch the hosted MCP server to
@umbraco-cms/mcp-hosted1.0.0-beta.48 and redeploy it. - Patch Workflow, Commerce and Engage through NuGet, including on Umbraco Cloud.
- Patch the CMS on self-hosted sites. On Cloud, confirm the automatic upgrade ran.
- Do the follow-ups. Rebuild the Members index on 17 and 18. Check Workflow user group permissions. Rotate Commerce payment secrets if needed.
- Review accounts. Remove back-office users who no longer need access, and review recent Workflow approvals.
Frequently Asked Questions
What does the November 17 Umbraco security update fix?
Seven vulnerabilities: five High in Workflow (two), Commerce, Engage and the MCP Server SDK, and two Moderate in Umbraco CMS. Umbraco published them on November 17, 2026.
Do these vulnerabilities have CVE IDs?
Not as of 4:40 a.m. ET on November 17. Each GitHub advisory reads “No known CVE.” The Delivery API advisory refers to CVE-2026-69197, the earlier issue it completes.
Does Umbraco Cloud apply the whole Umbraco security update for me?
No. Umbraco Cloud upgrades the CMS automatically. Workflow, Commerce and Engage are add-ons and need a manual upgrade. A hosted MCP server runs outside Cloud and also needs a manual upgrade.
Which issue should I patch first?
The hosted MCP server, if you run one, because the attacker needs no account. Then Workflow and Commerce, which expose database data and payment secrets to any back-office user.
We do not use MCP. Are we affected by the SDK issue?
No. Umbraco says only sites running a hosted MCP server built on @umbraco-cms/mcp-hosted are affected. That includes servers created from the project template.
Can anonymous visitors exploit any of these?
Only the Umbraco 13 Delivery API issue, and only when the Delivery API is on and publicly accessible. The other six need a back-office login, or a signed-in user who opens a link.
We are on Umbraco 15. Is there a patch?
No. Umbraco 12, 14 and 15 are end of life and get no fix for the Delivery API issue. Umbraco recommends a major upgrade to 17 LTS or 18.
Is there anything to do after this Umbraco security update installs?
Yes. Rebuild the Members index on CMS 17 and 18. Check Workflow permissions on custom user groups. Rotate Commerce payment gateway secrets if misuse cannot be ruled out.
Should we wait for Umbraco 19 instead?
No. Umbraco 19 is planned for December 10, 2026, is a short-term release, and Commerce 19.0.0-rc.1 was itself affected. Patch now on your current supported version.