CVE-2026-69197

Umbraco-CMS · Vulnerability

CVSS 4.0 8.7 HIGHEUVD CVSS 4.0 8.7 CVSS 4.0 · [email protected] · Secondary 8.7 HIGHCVSS_V4 Publisher rating HIGHFixed by Umbraco.Cms 13.15.1 Fixed by Umbraco.Cms 17.5.3 Fixed by Umbraco.Cms 18.0.2KEV status unknown

Original advisory

cve-program · CVE-2026-69197

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-81902

Published

Read the publisher's advisory

nvd · CVE-2026-69197

Published

Read the publisher's advisory

osv · GHSA-wr57-hqmp-fgvh

Published

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 via reference expansion. ### Impact Confidential, member-gated content (e.g. pricing, internal documents, gated articles) referenced by any publicly readable node is disclosed to unauthenticated clients. No write/integrity or availability impact. Highest impact when the Delivery API is publicly readable (DeliveryApi:PublicAccess: true). Still exploitable, at reduced severity, when the Delivery API is gated by the org-wide API key (the key holder still bypasses per-node Public Access). ### Patches 13.15.1, 17.5.3, 18.0.2 ### References https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/headless-and-apis/content-delivery-api

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-69197

Published

Umbraco-CMS

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "umbraco",
                    "product": "Umbraco-CMS",
                    "versions": [
                        {
                            "version": ">= 12.0.0, < 13.15.1",
                            "status": "affected"
                        },
                        {
                            "version": ">= 14.0.0-rc1, < 17.5.3",
                            "status": "affected"
                        },
                        {
                            "version": ">= 18.0.0, < 18.0.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-81902

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 17, 2026, 3:44:24 PM

dateUpdated: Sep 17, 2026, 5:23:18 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-69197

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-200 · CWE-862

Original publisher date fields

published: 2026-09-17T16:17:41.010

lastModified: 2026-09-30T17:51:56.193

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-wr57-hqmp-fgvh

Published

Umbraco.Cms

NuGet

ECOSYSTEM · introduced 12.0.0 → fixed 13.15.1

85 versions listed as affected

12.0.0, 12.0.1, 12.1.0, 12.1.0-rc, 12.1.1, 12.1.2, 12.2.0, 12.2.0-rc, 12.3.0, 12.3.0-rc, 12.3.1, 12.3.10, 12.3.2, 12.3.3, 12.3.4, 12.3.5, 12.3.6, 12.3.7, 12.3.8, 12.3.9, 13.0.0, 13.0.0-rc1, 13.0.0-rc2, 13.0.0-rc3, 13.0.0-rc4, 13.0.0-rc5, 13.0.1, 13.0.2, 13.0.3, 13.1.0, 13.1.0-rc, 13.1.1, 13.10.0, 13.10.0-rc, 13.10.1, 13.11.0, 13.11.0-rc, 13.11.0-rc2, 13.12.0, 13.12.0-rc, 13.12.0-rc2, 13.12.1, 13.13.0, 13.13.0-rc, 13.13.0-rc2, 13.13.0-rc3, 13.13.1, 13.14.0, 13.14.0-rc, 13.14.0-rc2, 13.14.0-rc3, 13.15.0, 13.15.0-rc, 13.2.0, 13.2.0-rc, 13.2.1, 13.2.2, 13.3.0, 13.3.0-rc, 13.3.1, 13.3.2, 13.4.0, 13.4.0-rc, 13.4.0-rc2, 13.4.1, 13.5.0, 13.5.0-rc, 13.5.1, 13.5.2, 13.5.3, 13.6.0, 13.6.0-rc, 13.6.0-rc2, 13.7.0, 13.7.0-rc, 13.7.1, 13.7.2, 13.8.0, 13.8.0-rc, 13.8.1, 13.9.0, 13.9.0-rc, 13.9.1, 13.9.2, 13.9.3

Umbraco.Cms

NuGet

ECOSYSTEM · introduced 14.0.0-rc1 → fixed 17.5.3

111 versions listed as affected

14.0.0, 14.0.0-rc1, 14.0.0-rc2, 14.0.0-rc3, 14.0.0-rc4, 14.0.0-rc5, 14.1.0, 14.1.0-rc, 14.1.0-rc2, 14.1.1, 14.1.2, 14.2.0, 14.2.0-rc, 14.2.0-rc2, 14.2.0-rc3, 14.3.0, 14.3.0-rc, 14.3.1, 14.3.2, 14.3.3, 14.3.4, 15.0.0, 15.0.0-rc1, 15.0.0-rc2, 15.0.0-rc3, 15.0.0-rc4, 15.1.0, 15.1.0-rc, 15.1.0-rc2, 15.1.1, 15.1.2, 15.2.0, 15.2.0-rc, 15.2.1, 15.2.2, 15.2.3, 15.3.0, 15.3.0-rc, 15.3.0-rc2, 15.3.1, 15.4.0, 15.4.0-rc, 15.4.0-rc2, 15.4.1, 15.4.2, 15.4.3, 15.4.4, 16.0.0, 16.0.0-rc, 16.0.0-rc2, 16.0.0-rc3, 16.0.0-rc4, 16.0.0-rc5, 16.0.0-rc6, 16.1.0, 16.1.0-rc, 16.1.1, 16.2.0, 16.2.0-rc, 16.2.0-rc2, 16.3.0, 16.3.0-rc, 16.3.0-rc2, 16.3.0-rc3, 16.3.0-rc4, 16.3.1, 16.3.2, 16.3.3, 16.3.4, 16.4.0, 16.4.0-rc, 16.4.0-rc2, 16.4.1, 16.5.0, 16.5.0-rc, 16.5.1, 17.0.0, 17.0.0-beta, 17.0.0-rc1, 17.0.0-rc2, 17.0.0-rc3, 17.0.0-rc4, 17.0.1, 17.0.2, 17.1.0, 17.1.0-rc, 17.2.0, 17.2.0-rc, 17.2.0-rc2, 17.2.1, 17.2.2, 17.3.0, 17.3.0-rc, 17.3.0-rc2, 17.3.0-rc3, 17.3.1, 17.3.2, 17.3.3, 17.3.4, 17.3.5, 17.4.0, 17.4.0-rc, 17.4.0-rc2, 17.4.0-rc3, 17.4.1, 17.4.2, 17.5.0, 17.5.0-rc, 17.5.0-rc2, 17.5.1, 17.5.2

Umbraco.Cms

NuGet

ECOSYSTEM · introduced 18.0.0 → fixed 18.0.2

2 versions listed as affected

18.0.0, 18.0.1

Original source record · Cite this exact observation · Complete original publisher JSON