Skip to main content
CVE-2024-23295VulnerabilityPublished Updated

CVE-2024-23295: Apple visionOS · An unauthenticated user may be able to use an unprotected Persona

Affects Apple visionOSSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium · fixed in 1.1 : update Apple visionOS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Apple visionOSAffected
  • =0
Fixed in–

AI-suggested

Apply the official update to visionOS 1.1, which includes the fix for this vulnerability through additional entitlement checks to protect Personas. No further action is required beyond updating to the patched version as per the Apple advisory.

Description

CVE-2024-23295 is a permissions vulnerability in Apple visionOS that allowed an unauthenticated user to use an unprotected Persona. This issue was addressed in visionOS 1.1 by implementing additional entitlement checks to ensure Personas are always protected. The vulnerability has a CVSS score of 6.2, indicating a medium severity. There are no known exploits in the wild. The vendor advisory confirms that the issue is fixed in visionOS 1.1.

References

Community reviews

Loading reviews…