VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-anymail: vulnerability history, versions and safety

django-anymail is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 23 releases, from Feb 2018 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 U2
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 django-anymail vulnerabilities

Vulert verdict on django-anymail 15.2.0 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 15.2.0 — unaffected i
  • Vulnerabilities on record 4 over 4 years · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 18 packages i
  • Stars 1,912 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 django-anymail, 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
15.2.0 05 Sep 2026 none BSD-3-Clause — Details →
15.1.0 30 Jul 2026 none BSD-3-Clause — Details →
15.0.0 18 Apr 2026 none non-standard — Details →
14.0.0 18 Dec 2025 none non-standard — Details →
13.1.0 03 Sep 2025 none non-standard — Details →
13.0.1 25 Jul 2025 none non-standard — Details →
13.0.0 03 Apr 2025 none non-standard — Details →
12.0.0 09 Sep 2024 none non-standard — Details →
11.1.0 07 Aug 2024 none non-standard — Details →
11.0.1 11 Jul 2024 none non-standard — Details →
11.0.0 23 Jun 2024 none non-standard — Details →
10.3.0 12 Mar 2024 none non-standard — Details →
10.2.0 25 Oct 2023 none non-standard — Details →
10.1.0 31 Jul 2023 none non-standard — Details →
10.0.0 07 May 2023 none non-standard — Details →
9.2.0 02 May 2023 none non-standard — Details →
9.1.0 11 Mar 2023 none non-standard — Details →
9.0.0 19 Dec 2022 none non-standard — Details →
8.6.0 15 May 2022 none non-standard — Details →
8.5.0 19 Jan 2022 none non-standard — Details →
8.4.0 15 Jun 2021 none non-standard — Details →
8.3.0 19 May 2021 none non-standard — Details →
8.2.0 27 Jan 2021 none non-standard — Details →
8.1.0 09 Oct 2020 none non-standard — Details →
8.0.0 11 Sep 2020 none non-standard — Details →
7.2.1 05 Aug 2020 none non-standard — Details →
7.2.0 25 Jul 2020 none non-standard — Details →
7.1.0 13 Apr 2020 none non-standard — Details →
7.0.0 07 Sep 2019 none non-standard — Details →
6.1.0 07 Jul 2019 none non-standard — Details →
6.0.1 19 May 2019 none non-standard — Details →
6.0.0 24 Feb 2019 none non-standard — Details →
5.0.0 07 Nov 2018 none non-standard — Details →
4.3.0 12 Oct 2018 none non-standard — Details →
4.2.0 07 Sep 2018 none non-standard — Details →
4.1.0 27 Aug 2018 none non-standard — Details →
4.0.0 19 Aug 2018 none non-standard — Details →
3.0.0 30 May 2018 none non-standard — Details →
2.2.0 16 Apr 2018 none non-standard — Details →
2.1.0 11 Apr 2018 none non-standard — Details →
2.0.0 08 Mar 2018 none non-standard — Details →
1.4.0 08 Feb 2018 none non-standard — Details →
1.3.0 02 Feb 2018 C1 non-standard Yes Details →
1.2.1 02 Feb 2018 C1 U1 non-standard Yes Details →
1.2.0 02 Nov 2017 C2 non-standard Yes Details →
1.1.0 28 Oct 2017 C2 non-standard Yes Details →
1.0.0 18 Sep 2017 C2 non-standard Yes Details →
1.0.0rc0 09 Sep 2017 C2 non-standard Yes Details →
0.11.1 24 Jul 2017 C2 U2 non-standard Yes Details →
0.11.0 13 Jul 2017 C2 U1 non-standard Yes Details →
0.10.0 22 May 2017 C2 U1 non-standard Yes Details →
0.9.0 04 Apr 2017 C2 U1 non-standard Yes Details →
0.8.0 02 Feb 2017 C2 U1 non-standard Yes Details →
0.7.0 30 Dec 2016 C2 U1 non-standard Yes Details →
0.6.1 01 Nov 2016 C2 U2 non-standard Yes Details →
0.6.0 25 Oct 2016 C2 U1 non-standard Yes Details →
0.5.0 22 Aug 2016 C2 U1 non-standard Yes Details →
0.4.2 24 Jun 2016 C2 U2 non-standard Yes Details →
0.4.1 23 Jun 2016 C2 U2 non-standard Yes Details →
0.3.1 18 May 2016 C2 U2 non-standard Yes Details →
0.3.0 13 May 2016 C2 U1 non-standard Yes Details →
0.2.0 30 Apr 2016 C2 U1 non-standard Yes Details →
0.1.0 14 Mar 2016 C1 U1 non-standard Yes Details →
0.1.0.dev2 12 Mar 2016 C1 U1 non-standard Yes Details →
0.1.0.dev1 10 Mar 2016 C1 U1 non-standard Yes Details →

All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 3
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for django-anymail

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-6596: Django-Anymail Timing Attack Vulnerability 9.1 critical 1.2.1 12 Jul 2018
CVE-2018-1000089: django-anymail Includes Sensitive Information in Log Files 7.4 critical 1.4 14 May 2022
CVE-2018-1000089: Anymail django-anymail WEBHOOK_AUTHORIZATION Vulnerability N/A unrated 1a6086f2b58478d71f89bf27eb034ed81aefe5ef 13 Mar 2018
CVE-2018-6596: Timing Attack Vulnerability in django-anymail N/A unrated db586ede1fbb41dce21310ea28ae15a1cf1286c5 03 Feb 2018

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 django-anymail

Is django-anymail safe to use?

Vulert records 4 vulnerabilities for django-anymail in PyPI: 2 critical, 0 high, 0 medium and 0 low, plus 2 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 django-anymail's Vulert package health score?

Vulert scores django-anymail 77/100, which reads as in good shape. 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 django-anymail affected?

No. 15.2.0, 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 django-anymail should I use?

15.2.0 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 django-anymail have?

4 vulnerabilities are recorded for django-anymail in the PyPI ecosystem: 2 critical, 0 high, 0 medium and 0 low, plus 2 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 django-anymail vulnerabilities disclosed?

0 vulnerabilities were recorded for django-anymail in the last 12 months, and the oldest entry in this database dates to 03 Feb 2018. 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 django-anymail 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 django-anymail for upcoming vulnerabilities?

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