Patch & vulnerability status
Anaconda, Inc.
Anaconda3 2026.7.1
Latest tracked version 2026.7.1. Release status, tracked CVEs, and automated cross-platform patching for Anaconda3.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 2026.7.1 | 4 | 2026-08-10 |
Known vulnerabilities (CVEs) in Anaconda3
Lavawall tracks 4 published CVEs affecting Anaconda3, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2024-46060 | 2025-12-17 19:16:00 | HIGH (8) | 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. | LOCAL |
| CVE-2023-35845 | 2023-09-11 08:15:07 | MEDIUM (5) | Anaconda 3 2023.03-1-Linux allows local users to disrupt TLS certificate validation by modifying the cacert.pem file used by the installed pip program. This occurs because many files are installed as world-writable on Linux, ignoring umask, even when these files are installed as root. Miniconda is also affected. | LOCAL |
| CVE-2022-26526 | 2022-03-17 16:15:08 | HIGH (8) | Anaconda Anaconda3 (Anaconda Distribution) through 2021.11.0.0 and Miniconda3 through 4.11.0.0 can create a world-writable directory under %PROGRAMDATA% and place that directory into the system PATH environment variable. Thus, for example, local users can gain privileges by placing a Trojan horse file into that directory. (This problem can only happen in a non-default installation. The person who installs the product must specify that it is being installed for all users. Also, the person who installs the product must specify that the system PATH should be changed. | LOCAL |
| CVE-2021-42969 | 2022-05-13 12:15:08 | HIGH (9) | Certain Anaconda3 2021.05 are affected by OS command injection. When a user installs Anaconda, an attacker can create a new file and write something in usercustomize.py. When the user opens the terminal or activates Anaconda, the command will be executed. | NETWORK |
Why keeping Anaconda3 patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every Anaconda3 release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches Anaconda3
Lavawall® watches Anaconda3 releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on Anaconda3, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks Anaconda3 at version 2026.7.1 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 4 CVEs for Anaconda3 and remediates them automatically as part of patching.
Deploy the Lavawall® agent and Anaconda3 updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for Anaconda3 through public information and proprietary statistical analysis, and can patch it automatically across your fleet.