Skip to main content
Menu
CVEs

Okta Verify for macOS root privilege escalation via symlink in Okta Device Access

CVE-2026-83631Published November 19, 2026, updated

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 9.75.1
Who is exposed
Not reported

Summary

Okta Verify for macOS on Intel-based Macs has a flaw in its Okta Device Access component, where a LaunchDaemon service runs through a symbolic link in /usr/local/bin. A local attacker who doesn't need to log in or have any user action can, where non-standard permissions let non-root users write to that path, swap the link's target so the service runs the attacker's binary when it restarts.

Written by a model

Original description

On Intel-based macOS systems, the Okta Device Access (ODA) component of Okta Verify for macOS configures a LaunchDaemon service whose program path resolves via a symbolic link in /usr/local/bin. In environments where non-standard directory permissions grant local non-root users write access to this path, the symbolic link target can be modified, causing the LaunchDaemon to execute the replacement binary upon service restart.

What to do

Upgrade to a fixed version: 9.75.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-83631 (Symbolic Link Resolution in Okta Verify for macOS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-83631 (entry last updated 2026-11-19):
Affected:
- Okta Okta Verify for macOS: fixed in 9.75.1
Fixed versions: 9.75.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-83631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-83631 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://trust.okta.com/security-advisories/symbolic-link-resolution-in-okta-verify-for-macos-cve-2026-83631
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-83631
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-83631"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linktrust.okta.com · security-advisories/symbolic-link-resolution-in-okta-verify-for-macos-cve-2026-83631
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-83631
RecordNVD · CVE-2026-83631

Questions about CVE-2026-83631

Is CVE-2026-83631 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-83631?

Okta Verify for macOS: before 9.75.1.

Source: cve.now feed data

How do I fix CVE-2026-83631?

Upgrade to a fixed version: 9.75.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.