CVE-2026-69197 json
Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion
published last mo. modified last mo. also EUVD-2026-81902 , GHSA-wr57-hqmp-fgvh
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- nuget Umbraco.Cms 13.15.1, 17.5.3, 18.0.2
- umbraco umbraco_cms 13.15.1, 17.5.3, 18.0.2
- github.com/umbraco/Umbraco-CMS@26312a3 commit
- github.com/umbraco/Umbraco-CMS@5360e2a commit
- github.com/umbraco/Umbraco-CMS@a9649da commit
- github.com/umbraco/Umbraco-CMS/releases/tag/release-13.15.1 release
- github.com/umbraco/Umbraco-CMS/releases/tag/release-17.5.3 release
- github.com/umbraco/Umbraco-CMS/releases/tag/release-18.0.2 release
Is CVE-2026-69197 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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 |
| CNA | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Umbraco.Cms | >=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 |
Affected products
- umbraco Umbraco-CMS
Classification
References
-
github.com
/umbraco/Umbraco-CMS/commit/26312a3f717a0f33bb3d7d28b14bef3592bdb0fe
web
-
github.com
/umbraco/Umbraco-CMS/commit/5360e2a9681ce2d0024be374e80339260bcc2511
web
-
github.com
/umbraco/Umbraco-CMS/commit/a9649da4e5a0786db7688bd6b5036a21df26b015
web
-
github.com
/umbraco/Umbraco-CMS/security/advisories/GHSA-wr57-hqmp-fgvh
web
-
github.com
/umbraco/Umbraco-CMS/releases/tag/release-13.15.1
web
-
github.com
/umbraco/Umbraco-CMS/releases/tag/release-17.5.3
web
-
github.com
/umbraco/Umbraco-CMS/releases/tag/release-18.0.2
web
-
github.com
/umbraco/Umbraco-CMS
package
Sources
- CVE List CVE-2026-69197
- GitHub Advisory GHSA-wr57-hqmp-fgvh
- NVD CVE-2026-69197
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.