VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

miniconda: vulnerability history, versions and safety

miniconda is a package in the Bitnami ecosystem. Vulert records 3 vulnerabilities for it across 3 affected ranges, from Jan 2024 to Mar 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all miniconda vulnerabilities

Vulert verdict on miniconda i

Updated on 23 Oct 2026

Careful: 2 of the 3 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 3 vulnerabilities on record across 1 year, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 06 Mar 2024 i
  • Highest CVSS n/a i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 4.11.0 (exclusive) 1
from 2021.05.0 onwards, no fix published yet 1
from 2023.03-1.0 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for miniconda

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-42969: OS Command Injection in Anaconda3 2021.05 N/A high No fix published 31 Jan 2024
CVE-2023-35845: Anaconda 3 2023.03-1-Linux TLS Certificate Validation Disruption N/A medium No fix published 31 Jan 2024
CVE-2022-26526: Anaconda3 and Miniconda3 World-Writable Directory Creation Vulnerability N/A high 4.11.0 06 Mar 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About miniconda

Is miniconda safe to use?

Vulert records 3 vulnerabilities for miniconda in Bitnami: 0 critical, 2 high, 1 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does miniconda have?

3 vulnerabilities are recorded for miniconda in the Bitnami ecosystem: 0 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new miniconda vulnerabilities disclosed?

0 vulnerabilities were recorded for miniconda in the last 12 months, and the oldest entry in this database dates to 31 Jan 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of miniconda are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor miniconda for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the miniconda version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.