Information Disclosure in Umbraco.Cms (CVE-2026-69197)
Summary
Vulnerability in Umbraco.Cms (CVE-2026-69197). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 13.15.1 or later.
Original description
The description as published by the source.
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).
Pat…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-69197 has been found in Umbraco.Cms.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Umbraco.Cms to 13.15.1 or later.
If unsure, ask your IT team or search "Umbraco.Cms CVE-2026-69197" on the vendor's site.
CVE-2026-69197 (Umbraco.Cms) — CWE-200
Patched: 13.15.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Umbraco.Cms.
Check the vendor advisory for the affected versions of Umbraco.Cms.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 13.15.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Umbraco.Cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Umbraco.Cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Umbraco.Cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Umbraco.Cms to 13.15.1ステージング環境で 13.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com