CVE-2024-46060: Anaconda3 macOS installers · Incorrect Permissions
Source CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in 2024.06-1 : patch affected systems soon.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2024.06-1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
AI-suggested
- Ensure Anaconda3 installations on macOS are performed strictly within the user's home directory to avoid triggering the vulnerability.
- Restrict local user access to installation directories and audit permissions to prevent unauthorized modification of installer-created files.
- Monitor and enforce file permissions on Anaconda-related directories to detect and remediate world-writable files promptly.
- Implement strict local user privilege management and segmentation to limit the number of users with local access and reduce attack surface.
- Once available, promptly apply official patches or updated installers from Anaconda that address this vulnerability.
- Employ endpoint detection and response (EDR) tools to monitor for suspicious local command executions or privilege escalation attempts.
- Educate users and administrators about the risks of installing software outside recommended directories and the importance of adhering to security best practices.
- Consider deploying macOS security features such as System Integrity Protection (SIP) and mandatory access controls to limit the impact of local exploits.
Description
Anaconda3 macOS installers before 2024.06-1 contain a local privilege escalation vulnerability when installed outside the user's home directory. During installation, world-writable files are created and executed with root privileges. This allows a local low-privileged user to inject arbitrary commands, leading to code execution as the root user.