VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

instaloader: vulnerability history, versions and safety

instaloader is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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

Vulert verdict on instaloader 4.15.4 i

Updated on 23 Oct 2026

Good news: 4.15.4, the version you would install today, has no known vulnerabilities.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 4.15.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 47 packages i
  • Last release this month i
  • Licence MIT 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 instaloader, 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
4.16.0b1 21 Oct 2026 none MIT — Details →
4.15.4 12 Oct 2026 none MIT — Details →
4.15.3 26 Jul 2026 none MIT — Details →
4.15.2 05 Jul 2026 none MIT — Details →
4.15.1 21 Mar 2026 none MIT — Details →
4.15.0 08 Nov 2025 none MIT — Details →
4.15.0a1 18 Jul 2025 none MIT — Details →
4.14.2 18 Jul 2025 none MIT — Details →
4.14.1 24 Jan 2025 none MIT — Details →
4.14.0 07 Nov 2024 none MIT — Details →
4.14.0rc3 07 Nov 2024 none MIT — Details →
4.14.0rc2 26 Oct 2024 none MIT — Details →
4.13.2 26 Oct 2024 none MIT — Details →
4.14.0rc1 02 Oct 2024 none MIT — Details →
4.13.1 28 Aug 2024 none MIT — Details →
4.13.0 10 Aug 2024 none MIT — Details →
4.12.2 10 Aug 2024 none MIT — Details →
4.12.1 31 Jul 2024 none MIT — Details →
4.12.0 29 Jun 2024 none MIT — Details →
4.11.1 29 Jun 2024 none MIT — Details →
4.11.0 18 Mar 2024 none MIT — Details →
4.11.0rc3 17 Mar 2024 none MIT — Details →
4.10.3 12 Jan 2024 none MIT — Details →
4.11.0rc2 18 Dec 2023 none MIT — Details →
4.10.2 09 Dec 2023 none MIT — Details →
4.11.0rc1 15 Nov 2023 none MIT — Details →
4.10.1 16 Oct 2023 none MIT — Details →
4.10.0 10 Jul 2023 none MIT — Details →
4.10.0b1 19 Apr 2023 none MIT — Details →
4.9.6 11 Feb 2023 none MIT — Details →
4.9.5 26 Sep 2022 none MIT — Details →
4.9.4 16 Sep 2022 none MIT — Details →
4.9.3 11 Aug 2022 none MIT — Details →
4.9.2 04 Jul 2022 none MIT — Details →
4.9.1 08 Jun 2022 none MIT — Details →
4.9.0 26 Mar 2022 none MIT — Details →
4.8.5 19 Mar 2022 none MIT — Details →
4.9.0b3 19 Mar 2022 none MIT — Details →
4.9.0b2 15 Jan 2022 none MIT — Details →
4.8.4 15 Jan 2022 none MIT — Details →
4.8.3 07 Jan 2022 none MIT — Details →
4.8.2 27 Nov 2021 none MIT — Details →
4.9.0b1 12 Nov 2021 none MIT — Details →
4.8.1 10 Aug 2021 none MIT — Details →
4.8.0 04 Aug 2021 none MIT — Details →
4.7.6 04 Aug 2021 none MIT — Details →
4.7.5 24 Jul 2021 none MIT — Details →
4.8.0rc4 24 Jul 2021 none MIT — Details →
4.8.0rc3 22 Jun 2021 none MIT — Details →
4.7.4 18 Jun 2021 none MIT — Details →
4.8.0rc2 18 Jun 2021 none MIT — Details →
4.7.2 06 Jun 2021 none MIT — Details →
4.7.1 27 Mar 2021 none MIT — Details →
4.7.0 27 Mar 2021 none MIT — Details →
4.7.0rc2 20 Mar 2021 none MIT — Details →
4.7.0rc1 13 Mar 2021 none MIT — Details →
4.6.2 24 Feb 2021 none MIT — Details →
4.6.1 25 Jan 2021 none MIT — Details →
4.6.0 09 Jan 2021 none MIT — Details →
4.6.0rc1 02 Jan 2021 none MIT — Details →
4.6.0a1 15 Dec 2020 none MIT — Details →
4.5.5 04 Dec 2020 none MIT — Details →
4.5.4 28 Nov 2020 none MIT — Details →
4.5.3 03 Sep 2020 none MIT — Details →
4.5.2 23 Aug 2020 none MIT — Details →
4.5.1 20 Aug 2020 none MIT — Details →
4.5.1rc1 17 Aug 2020 none MIT — Details →
4.5.0 02 Aug 2020 none MIT — Details →
4.5.0b1 30 Jul 2020 none MIT — Details →
4.5.0a1 21 Jul 2020 none MIT — Details →
4.4.5 18 Jul 2020 none MIT — Details →
4.4.5rc1 15 Jul 2020 none MIT — Details →
4.4.4 11 Jun 2020 none MIT — Details →
4.4.4rc3 08 Jun 2020 none MIT — Details →
4.4.4rc1 06 Jun 2020 none MIT — Details →
4.4.3 22 May 2020 none MIT — Details →
4.4.2 19 May 2020 none MIT — Details →
4.4.1 14 May 2020 none MIT — Details →
4.4.0 11 May 2020 none MIT — Details →
4.4.0b1 21 Apr 2020 none MIT — Details →
4.3.2 10 Apr 2020 none MIT — Details →
4.3.1 04 Apr 2020 none MIT — Details →
4.3.0 16 Mar 2020 none MIT — Details →
4.3.0rc1 15 Mar 2020 none MIT — Details →
4.3.0b1 14 Mar 2020 none MIT — Details →
4.3.0a2 01 Mar 2020 none MIT — Details →
4.3.0a1 17 Feb 2020 none MIT — Details →
4.2.10 28 Oct 2019 none MIT — Details →
4.2.9 18 Aug 2019 none MIT — Details →
4.2.8 27 May 2019 none MIT — Details →
4.2.7 17 May 2019 none MIT — Details →
4.2.6 08 May 2019 none MIT — Details →
4.2.5 07 May 2019 none MIT — Details →
4.2.5rc1 07 May 2019 none MIT — Details →
4.2.4 01 Apr 2019 none MIT — Details →
4.2.3 16 Feb 2019 none MIT — Details →
4.2.2 10 Feb 2019 none MIT — Details →
4.2.1 17 Jan 2019 none MIT — Details →
4.2.0 23 Dec 2018 none MIT — Details →
4.2.0rc2 21 Dec 2018 none MIT — Details →
4.2.0rc1 21 Dec 2018 none — — Details →
4.1.1 07 Oct 2018 none — — Details →
4.1.0 02 Sep 2018 none — — Details →
4.1.0rc1 31 Aug 2018 none — — Details →
4.1.0b1 31 Aug 2018 none — — Details →
4.1.0a1 24 Aug 2018 none — — Details →
4.0.8 07 Aug 2018 none — — Details →
4.0.7 05 Aug 2018 none — — Details →
4.0.6 02 Aug 2018 none — — Details →
4.0.5 09 Jul 2018 none — — Details →
4.0.4 07 Jun 2018 none — — Details →
4.0.3 23 May 2018 none — — Details →
4.0.2 14 May 2018 none — — Details →
4.0.1 08 May 2018 none — — Details →
4.0.0 02 May 2018 none — — Details →
4.0.0rc1 29 Apr 2018 none — — Details →
3.3.10 20 Apr 2018 none — — Details →
3.3.9 18 Apr 2018 none — — Details →
3.3.8 17 Apr 2018 none — — Details →
3.3.7 13 Apr 2018 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for instaloader

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 instaloader

Is instaloader safe to use?

Vulert has no vulnerabilities on record for instaloader in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is instaloader's Vulert package health score?

Vulert scores instaloader 89/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 instaloader affected?

No. 4.15.4, 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.

Which version of instaloader should I use?

4.15.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does instaloader have?

0 vulnerabilities are recorded for instaloader in the PyPI ecosystem: 0 critical, 0 high, 0 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 instaloader vulnerabilities disclosed?

0 vulnerabilities were recorded for instaloader in the last 12 months. 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 instaloader 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 instaloader for upcoming vulnerabilities?

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