Improper Link Resolution in Okta Verify for Windows Uninstaller Data Removal
Summary
| CVE | CVE-2026-78622 |
|---|---|
| State | PUBLISHED |
| Assigner | Okta |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-08 21:18:41 UTC |
| Updated | 2026-09-10 15:17:41 UTC |
| Description | The Okta Verify for Windows uninstaller does not verify whether the user data directory is a filesystem junction before deleting its contents with elevated privileges. The delete operation follows the junction target, resulting in recursive deletion of unintended directory contents. |
Risk And Classification
Primary CVSS: v3.1 6 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H
EPSS: 0.000990000 probability, percentile 0.008710000 (date 2026-09-09)
Problem Types: CWE-59 | CWE-59 Improper Link Resolution Before File Access
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 6 | MEDIUM | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H |
| 3.1 | CNA | DECLARED | 6 | MEDIUM | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
HighPrivileges Required
LowUser Interaction
RequiredScope
UnchangedConfidentiality
NoneIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Okta | Okta Verify For Windows | affected 5.1.3 7.0.0 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| trust.okta.com/security-advisories/improper-link-resolution-in-okta-verify-f... | [email protected] | trust.okta.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
Solutions
CNA: Upgrade the Okta Verify for Windows client to version 7.0.0 or greater.
There are currently no legacy QID mappings associated with this CVE.