VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ultralytics: vulnerability history, versions and safety

ultralytics is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Dec 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 ultralytics vulnerabilities

Vulert verdict on ultralytics 8.4.184 i

Updated on 23 Oct 2026

Good news: 8.4.184, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 95/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 8.4.184 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.4.184 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.4.184 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Dec 2024 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 62,645 i
  • Last release this month i
  • Licence AGPL-3.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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

Every version Vulert tracks for ultralytics, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.4.184 22 Oct 2026 none AGPL-3.0 — Details →
8.4.183 20 Oct 2026 none AGPL-3.0 — Details →
8.4.182 18 Oct 2026 none AGPL-3.0 — Details →
8.4.181 17 Oct 2026 none AGPL-3.0 — Details →
8.4.180 17 Oct 2026 none AGPL-3.0 — Details →
8.4.179 17 Oct 2026 none AGPL-3.0 — Details →
8.4.178 16 Oct 2026 none AGPL-3.0 — Details →
8.4.177 13 Oct 2026 none AGPL-3.0 — Details →
8.4.176 12 Oct 2026 none AGPL-3.0 — Details →
8.4.175 09 Oct 2026 none AGPL-3.0 — Details →
8.4.174 06 Oct 2026 none AGPL-3.0 — Details →
8.4.173 04 Oct 2026 none AGPL-3.0 — Details →
8.4.172 03 Oct 2026 none AGPL-3.0 — Details →
8.4.171 01 Oct 2026 none AGPL-3.0 — Details →
8.4.170 30 Sep 2026 none AGPL-3.0 — Details →
8.4.169 30 Sep 2026 none AGPL-3.0 — Details →
8.4.168 30 Sep 2026 none AGPL-3.0 — Details →
8.4.167 30 Sep 2026 none AGPL-3.0 — Details →
8.4.166 29 Sep 2026 none AGPL-3.0 — Details →
8.4.165 28 Sep 2026 none AGPL-3.0 — Details →
8.4.164 27 Sep 2026 none AGPL-3.0 — Details →
8.4.163 25 Sep 2026 none AGPL-3.0 — Details →
8.4.162 24 Sep 2026 none AGPL-3.0 — Details →
8.4.161 23 Sep 2026 none AGPL-3.0 — Details →
8.4.160 22 Sep 2026 none AGPL-3.0 — Details →
8.4.159 22 Sep 2026 none AGPL-3.0 — Details →
8.4.158 21 Sep 2026 none AGPL-3.0 — Details →
8.4.157 20 Sep 2026 none AGPL-3.0 — Details →
8.4.156 19 Sep 2026 none AGPL-3.0 — Details →
8.4.155 17 Sep 2026 none AGPL-3.0 — Details →
8.4.154 16 Sep 2026 none AGPL-3.0 — Details →
8.4.153 15 Sep 2026 none AGPL-3.0 — Details →
8.4.152 14 Sep 2026 none AGPL-3.0 — Details →
8.4.151 14 Sep 2026 none AGPL-3.0 — Details →
8.4.150 12 Sep 2026 none AGPL-3.0 — Details →
8.4.149 12 Sep 2026 none AGPL-3.0 — Details →
8.4.148 11 Sep 2026 none AGPL-3.0 — Details →
8.4.147 11 Sep 2026 none AGPL-3.0 — Details →
8.4.146 09 Sep 2026 none AGPL-3.0 — Details →
8.4.145 09 Sep 2026 none AGPL-3.0 — Details →
8.4.144 08 Sep 2026 none AGPL-3.0 — Details →
8.4.143 07 Sep 2026 none AGPL-3.0 — Details →
8.4.142 05 Sep 2026 none AGPL-3.0 — Details →
8.4.141 05 Sep 2026 none AGPL-3.0 — Details →
8.4.140 04 Sep 2026 none AGPL-3.0 — Details →
8.4.139 04 Sep 2026 none AGPL-3.0 — Details →
8.4.138 01 Sep 2026 none AGPL-3.0 — Details →
8.4.137 31 Aug 2026 none AGPL-3.0 — Details →
8.4.136 31 Aug 2026 none AGPL-3.0 — Details →
8.4.135 29 Aug 2026 none AGPL-3.0 — Details →
8.4.134 29 Aug 2026 none AGPL-3.0 — Details →
8.4.133 29 Aug 2026 none AGPL-3.0 — Details →
8.4.132 28 Aug 2026 none AGPL-3.0 — Details →
8.4.131 27 Aug 2026 none AGPL-3.0 — Details →
8.4.130 26 Aug 2026 none AGPL-3.0 — Details →
8.4.129 25 Aug 2026 none AGPL-3.0 — Details →
8.4.128 25 Aug 2026 none AGPL-3.0 — Details →
8.4.127 23 Aug 2026 none AGPL-3.0 — Details →
8.4.126 21 Aug 2026 none AGPL-3.0 — Details →
8.4.125 21 Aug 2026 none AGPL-3.0 — Details →
8.4.124 20 Aug 2026 none AGPL-3.0 — Details →
8.4.123 19 Aug 2026 none AGPL-3.0 — Details →
8.4.122 19 Aug 2026 none AGPL-3.0 — Details →
8.4.121 17 Aug 2026 none AGPL-3.0 — Details →
8.4.120 13 Aug 2026 none AGPL-3.0 — Details →
8.4.119 13 Aug 2026 none AGPL-3.0 — Details →
8.4.118 11 Aug 2026 none AGPL-3.0 — Details →
8.4.117 09 Aug 2026 none AGPL-3.0 — Details →
8.4.116 07 Aug 2026 none AGPL-3.0 — Details →
8.4.115 01 Aug 2026 none AGPL-3.0 — Details →
8.4.114 31 Jul 2026 none AGPL-3.0 — Details →
8.4.113 30 Jul 2026 none AGPL-3.0 — Details →
8.4.112 29 Jul 2026 none AGPL-3.0 — Details →
8.4.111 29 Jul 2026 none AGPL-3.0 — Details →
8.4.110 29 Jul 2026 none AGPL-3.0 — Details →
8.4.109 28 Jul 2026 none AGPL-3.0 — Details →
8.4.108 27 Jul 2026 none AGPL-3.0 — Details →
8.4.107 26 Jul 2026 none AGPL-3.0 — Details →
8.4.106 25 Jul 2026 none AGPL-3.0 — Details →
8.4.105 24 Jul 2026 none AGPL-3.0 — Details →
8.4.104 21 Jul 2026 none AGPL-3.0 — Details →
8.4.103 21 Jul 2026 none AGPL-3.0 — Details →
8.4.102 19 Jul 2026 none AGPL-3.0 — Details →
8.4.101 18 Jul 2026 none AGPL-3.0 — Details →
8.4.100 18 Jul 2026 none AGPL-3.0 — Details →
8.4.99 17 Jul 2026 none AGPL-3.0 — Details →
8.4.98 17 Jul 2026 none AGPL-3.0 — Details →
8.4.97 17 Jul 2026 none AGPL-3.0 — Details →
8.4.96 15 Jul 2026 none AGPL-3.0 — Details →
8.4.95 13 Jul 2026 none AGPL-3.0 — Details →
8.4.94 13 Jul 2026 none AGPL-3.0 — Details →
8.4.93 12 Jul 2026 none AGPL-3.0 — Details →
8.4.92 10 Jul 2026 none AGPL-3.0 — Details →
8.4.91 09 Jul 2026 none AGPL-3.0 — Details →
8.4.90 06 Jul 2026 none AGPL-3.0 — Details →
8.4.89 05 Jul 2026 none AGPL-3.0 — Details →
8.4.88 05 Jul 2026 none AGPL-3.0 — Details →
8.4.87 03 Jul 2026 none AGPL-3.0 — Details →
8.4.86 02 Jul 2026 none AGPL-3.0 — Details →
8.4.85 02 Jul 2026 none AGPL-3.0 — Details →
8.4.84 01 Jul 2026 none — — Details →
8.4.83 29 Jun 2026 none — — Details →
8.4.82 29 Jun 2026 none — — Details →
8.4.81 28 Jun 2026 none — — Details →
8.4.80 26 Jun 2026 none — — Details →
8.4.79 26 Jun 2026 none — — Details →
8.4.78 25 Jun 2026 none — — Details →
8.4.77 25 Jun 2026 none — — Details →
8.4.76 24 Jun 2026 none — — Details →
8.4.75 21 Jun 2026 none — — Details →
8.4.74 21 Jun 2026 none — — Details →
8.4.73 21 Jun 2026 none — — Details →
8.4.72 19 Jun 2026 none — — Details →
8.4.71 18 Jun 2026 none — — Details →
8.4.70 17 Jun 2026 none — — Details →
8.4.69 16 Jun 2026 none — — Details →
8.4.68 15 Jun 2026 none — — Details →
8.4.67 14 Jun 2026 none — — Details →
8.4.66 11 Jun 2026 none — — Details →
8.4.65 11 Jun 2026 none — — Details →

The newest 120 of 859 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for ultralytics

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Crypto Miner Found in Ultralytics Package Versions 8.3.41 to 8.3.46 8.6 high 8.3.47 10 Dec 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 ultralytics

Is ultralytics safe to use?

Vulert records 1 vulnerabilities for ultralytics in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ultralytics's Vulert package health score?

Vulert scores ultralytics 95/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of ultralytics affected?

No. 8.4.184, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does ultralytics have?

1 vulnerability is recorded for ultralytics in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ultralytics vulnerabilities disclosed?

0 vulnerabilities were recorded for ultralytics in the last 12 months, and the oldest entry in this database dates to 10 Dec 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 ultralytics 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 ultralytics for upcoming vulnerabilities?

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