Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion

CVE-2026-69197GHSA-wr57-hqmp-fgvh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (umbraco.cms 18.0.2, 17.5.3, 13.15.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • NuGet umbraco.cms

    Affected
    >= 12.0.0, < 13.15.1>= 14.0.0-rc1, < 17.5.3>= 18.0.0, < 18.0.2
    Fixed in
    17.5.3, 13.15.1, 18.0.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-69197: 0.66% estimated exploitation activity in the next 30 days; percentile 51.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The Content Delivery API enforces member / Public Access protection only at the controller layer, against the node that is directly requested. When a public (unprotected) node references a protected node through a Content Picker or Multi-Node Tree Picker (including those nested inside Block List, Block Grid, or Rich Text Editor blocks), the Delivery API expands and serializes the protected node with no access check applied. Similarly, configuration based restrictions based on aliases of allowed or disallowed content types are by-passed for referenced content items that are retrieved via property expansion. As a result, an anonymous / unauthorized caller can retrieve a protected node's: - Name, route, and id — always, even without expansion, and - Full property values — when the request uses ?expand on the picker property. A direct request for the same protected node correctly returns 401 Unauthorized, which makes the leak easy to miss: the protection appears to work, but is bypassed…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-wr57-hqmp-fgvh

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-wr57-hqmp-fgvh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-69197

Advisory: Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion
IDs: CVE-2026-69197, GHSA-wr57-hqmp-fgvh
Record: https://patchnext.com/advisories/cve-2026-69197 (revision 3, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: umbraco.cms 18.0.2, 17.5.3, 13.15.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet umbraco.cms: affected >= 12.0.0, < 13.15.1; >= 14.0.0-rc1, < 17.5.3; >= 18.0.0, < 18.0.2; fixed in 17.5.3, 13.15.1, 18.0.2

## Suggested inspection (read-only)
- NuGet umbraco.cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on umbraco.cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wr57-hqmp-fgvh (OSV record GHSA-wr57-hqmp-fgvh lists affected ranges: NuGet umbraco.cms >=12.0.0 =14.0.0-rc1 =18.0.0 <18.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-wr57-hqmp-fgvh (GitHub-reviewed advisory GHSA-wr57-hqmp-fgvh lists affected ranges: NuGet umbraco.cms >=12.0.0 =14.0.0-rc1 =18.0.0 <18.0.2)

Commands are suggestions: review each one before running it.

Loading voting…