Answer in brief
CVE-2026-69197 records a High severity (CVSS 0.0) vulnerability in Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion. The current sources do not mark it as known exploited. The current feed maps umbraco/Umbraco-CMS (generic), Umbraco.Cms (nuget), Umbraco.Cms (nuget), Umbraco.Cms (nuget). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps umbraco/Umbraco-CMS (generic), Umbraco.Cms (nuget), Umbraco.Cms (nuget), Umbraco.Cms (nuget). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| umbraco/Umbraco-CMSgeneric | >=12.0.0 <13.15.1 || >=14.0.0-rc1 <17.5.3 || >=18.0.0 <18.0.2 | 13.15.1, 17.5.3, 18.0.2 |
| Umbraco.Cmsnuget | >=12.0.0,<13.15.1 | 13.15.1 |
| Umbraco.Cmsnuget | >=14.0.0-rc1,<17.5.3 | 17.5.3 |
| Umbraco.Cmsnuget | >=18.0.0,<18.0.2 | 18.0.2 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.