Skip to main content
VulnerabilityPublished

CVE-2026-83631: Okta Verify for macOS · Link Following

Affects Okta Verify for macOSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 9.75.1 when convenient.

Data as of 19 Nov 2026, 21:34 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Okta)CVSS 3.16.8
Patch
Available – fixed in 9.75.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Okta Verify for macOS to 9.75.1.

Affected software

ProductAffectedFixed in
OktaOkta Verify for macOSAffected
  • <9.75.1
Fixed in
  • 9.75.1

AI-suggested

Upgrade Okta Verify for macOS to version 9.75.1 or later, where this vulnerability is fixed. Additionally, ensure that directory permissions for /usr/local/bin do not allow write access to unauthorized local users to prevent exploitation.

Description

CVE-2026-83631 is a vulnerability in Okta Verify for macOS affecting Intel-based systems. The Okta Device Access component configures a LaunchDaemon service whose program path resolves through a symbolic link in /usr/local/bin. If local non-root users have write access to this path due to non-standard directory permissions, they can modify the symbolic link target. This allows execution of a replacement binary when the LaunchDaemon service restarts. The issue is fixed in version 9.75.1.

References

Community reviews

Loading reviews…