This CVE represents a logic flaw in exception handling that bypasses .NET's managed security model — not a memory corruption issue — which means traditional exploit mitigations (ASLR, stack canaries) provide zero protection. The vulnerability stems from .NET's async patterns creating a systematic trap: when developers write DoSomethingAsync() instead of await DoSomethingAsync(), exceptions are silently captured into the Task and never surface to the caller. The caller sees 'started successfully' as equivalent to 'completed successfully' — a conflation the type system does not warn against. In authorization paths, this means security checks that should gate on completion instead gate on initiation, leaving the privilege context in an ambiguous or partially-applied state when the exception fires mid-elevation. Downstream components (distributed caches, database connections, inter-service tokens) receive what appears to be a legitimate call — no exception, no alarm, no audit entry. The failure is invisible until someone notices access anomalies in adjacent systems. The 'authorized attacker' framing in the CVSS deserves scrutiny: it suggests the attacker already has local access, but the escalation path (service account to SYSTEM looks very different from standard user to admin) fundamentally changes the threat model. The low EPSS likely reflects limited public exploitation knowledge rather than genuine constraint, and historical precedence shows these logic flaws tend to cluster — find one in an error-handling contract, and siblings often surface. Audit your async authorization paths for any DoSomethingAsync() calls that lack await, and extend scrutiny to any legacy APM (BeginXxx/EndXxx) callbacks in authorization layers that survived framework migrations untouched.
CVE-2026-62909
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUncaught exception in .NET allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 17.14.0, < 17.14.38>= 18.8.0, < 18.8.3>= 8.0.0, < 8.0.30>= 9.0.0, < 9.0.19>= 10.0.0, < 10.0.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data8.0.309.0.1910.0.11
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis CVE represents a logic flaw in exception handling that bypasses .NET's managed security model — not a memory corruption issue — which means traditional exploit mitigations (ASLR, stack canaries) provide zero protection. The vulnerability stems from .NET's async patterns creating a systematic trap: when developers write `DoSomethingAsync()` instead of `await DoSomethingAsync()`, exceptions are silently captured into the Task and never surface to the caller. The caller sees 'started successfully' as equivalent to 'completed successfully' — a conflation the type system does not warn against. In authorization paths, this means security checks that should gate on completion instead gate on initiation, leaving the privilege context in an ambiguous or partially-applied state when the exception fires mid-elevation. Downstream components (distributed caches, database connections, inter-service tokens) receive what appears to be a legitimate call — no exception, no alarm, no audit entry. The failure is invisible until someone notices access anomalies in adjacent systems. The 'authorized attacker' framing in the CVSS deserves scrutiny: it suggests the attacker already has local access, but the escalation path (service account to SYSTEM looks very different from standard user to admin) fundamentally changes the threat model. The low EPSS likely reflects limited public exploitation knowledge rather than genuine constraint, and historical precedence shows these logic flaws tend to cluster — find one in an error-handling contract, and siblings often surface. Audit your async authorization paths for any `DoSomethingAsync()` calls that lack `await`, and extend scrutiny to any legacy APM (`BeginXxx`/`EndXxx`) callbacks in authorization layers that survived framework migrations untouched.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62909 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data