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.
CVE-2026-69197
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-81902 (ENISA EUVD) · GHSA-wr57-hqmp-fgvh (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.7%
- EPSS %ILE
- 51st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 17, 2026
Last Modified
September 30, 2026
Advisory Details (7)
Auto-updated Sep 17, 202618.0.2
Patch available: umbraco/Umbraco-CMS release-18.0.2
https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.0.217.5.3
Patch available: umbraco/Umbraco-CMS release-17.5.3
https://github.com/umbraco/Umbraco-CMS/releases/tag/release-17.5.313.15.1
Patch available: umbraco/Umbraco-CMS release-13.15.1
https://github.com/umbraco/Umbraco-CMS/releases/tag/release-13.15.1commit a9649da4e5a0 (umbraco/Umbraco-CMS)
Fix landed in umbraco/Umbraco-CMS commit a9649da4e5a0 — awaiting tagged release
https://github.com/umbraco/Umbraco-CMS/commit/a9649da4e5a0786db7688bd6b5036a21df26b015commit 5360e2a9681c (umbraco/Umbraco-CMS)
Fix landed in umbraco/Umbraco-CMS commit 5360e2a9681c — awaiting tagged release
https://github.com/umbraco/Umbraco-CMS/commit/5360e2a9681ce2d0024be374e80339260bcc2511commit 26312a3f717a (umbraco/Umbraco-CMS)
Fix landed in umbraco/Umbraco-CMS commit 26312a3f717a — awaiting tagged release
https://github.com/umbraco/Umbraco-CMS/commit/26312a3f717a0f33bb3d7d28b14bef3592bdb0feDelivery 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-fgvhVendor 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.
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| nuget | Umbraco.Cms @ 13.15.1 (fixes >= 12.0.0, < 13.15.1) | — | ghsa |
| nuget | Umbraco.Cms @ 17.5.3 (fixes >= 14.0.0-rc1, < 17.5.3) | — | ghsa |
| nuget | Umbraco.Cms @ 18.0.2 (fixes >= 18.0.0, < 18.0.2) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| Umbraco.Cms | 18.0.0, 18.0.1 |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 49× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-01 07:40 UTCGHSA enrichmentGHSA-wr57-hqmp-fgvh · GitHub severity HIGH
- 2026-11-01 07:40 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-27 18:42 UTCEG score recompute
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 14:09 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-20 08:58 UTCEG score recompute
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-18 03:19 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 54 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-13 09:55 UTCEG score recompute
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-12 15:44 UTCEG score recompute
- 2026-10-11 19:29 UTCEG score recompute
- 2026-10-11 16:45 UTCEG score recompute
- 2026-10-11 14:05 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-11 03:42 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-10 03:05 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-08 18:02 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-08 05:08 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-06 17:24 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-05 19:23 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-05 08:14 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-03 23:13 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-03 01:13 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-02 03:10 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-30 18:08 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-29 16:50 UTCEG score recompute
- 2026-09-29 05:47 UTCEG score recompute
- 2026-09-28 18:47 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-27 20:47 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-26 22:47 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-26 00:47 UTCEG score recompute
- 2026-09-24 15:39 UTCEG score recompute
- 2026-09-24 04:39 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-22 19:38 UTCEG score recompute
- 2026-09-21 21:36 UTCEG score recompute
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-20 23:34 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-20 01:32 UTCEG score recompute
- 2026-09-19 03:29 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-17 18:26 UTCEG score recompute
- 2026-09-17 17:56 UTCEG score recompute
- 2026-09-17 15:49 UTCEG score recomputeFirst assessed: 8.7 HIGH
- 2026-09-17 15:49 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownNuGet:Umbraco.Cms
Frequently asked(5)
What is CVE-2026-69197?
When was the CVE record for CVE-2026-69197 published?
Is CVE-2026-69197 actively exploited?
What is the CVSS score of CVE-2026-69197?
How do I remediate CVE-2026-69197?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69197
Is Your Infrastructure Affected by CVE-2026-69197?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.