CVE-2026-69197

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (7)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

18.0.2

Patch available: umbraco/Umbraco-CMS release-18.0.2

https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.0.2
github_release Patch Available

17.5.3

Patch available: umbraco/Umbraco-CMS release-17.5.3

https://github.com/umbraco/Umbraco-CMS/releases/tag/release-17.5.3
github_release Patch Available

13.15.1

Patch available: umbraco/Umbraco-CMS release-13.15.1

https://github.com/umbraco/Umbraco-CMS/releases/tag/release-13.15.1
github_commit

commit a9649da4e5a0 (umbraco/Umbraco-CMS)

Fix landed in umbraco/Umbraco-CMS commit a9649da4e5a0 — awaiting tagged release

https://github.com/umbraco/Umbraco-CMS/commit/a9649da4e5a0786db7688bd6b5036a21df26b015
github_commit

commit 5360e2a9681c (umbraco/Umbraco-CMS)

Fix landed in umbraco/Umbraco-CMS commit 5360e2a9681c — awaiting tagged release

https://github.com/umbraco/Umbraco-CMS/commit/5360e2a9681ce2d0024be374e80339260bcc2511
github_commit

commit 26312a3f717a (umbraco/Umbraco-CMS)

Fix landed in umbraco/Umbraco-CMS commit 26312a3f717a — awaiting tagged release

https://github.com/umbraco/Umbraco-CMS/commit/26312a3f717a0f33bb3d7d28b14bef3592bdb0fe
github Patch Available

Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion · Advisory · umbraco/Umbraco-CMS · GitHub

https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-wr57-hqmp-fgvh

Vendor Advisories for CVE-2026-69197(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Umbraco.Cms12.0.0 ... 13.9.3 (85 versions)13.15.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 15:39 UTCEG score recompute
  2. 2026-09-24 04:39 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 19:38 UTCEG score recompute
  5. 2026-09-21 21:36 UTCEG score recompute
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-20 23:34 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-20 01:32 UTCEG score recompute
  10. 2026-09-19 03:29 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 18:26 UTCEG score recompute
  13. 2026-09-17 17:56 UTCEG score recompute
  14. 2026-09-17 15:49 UTCEG score recompute
  15. 2026-09-17 15:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-69197?
CVE-2026-69197 is a high vulnerability published on September 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…
When was CVE-2026-69197 disclosed?
CVE-2026-69197 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69197 actively exploited?
CVE-2026-69197 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.5% of all scored CVEs.
What is the CVSS score of CVE-2026-69197?
CVE-2026-69197 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-69197?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69197, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69197

Explore →

Is Your Infrastructure Affected by CVE-2026-69197?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs