VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

postorius: vulnerability history, versions and safety

postorius is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 35 releases, from Sep 2021 to Jul 2026. 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 H1 M1 U2
i
2 with no fix published

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

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

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all postorius vulnerabilities

Vulert verdict on postorius 1.3.13 i

Updated on 23 Oct 2026

Careful: 1.3.13 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.3.13 — affected i
  • Vulnerabilities on record 4 over 4 years · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 2 i
  • Depended on by 1 packages i
  • Stars 93 i
  • Last release 25 months ago i
  • Licence GPL-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 postorius, 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
1.3.13 21 Sep 2024 H1 U1 GPL-3.0 No Details →
1.3.13a1 01 Sep 2024 H1 U1 GPL-3.0 No Details →
1.3.12 03 Jul 2024 H1 U1 GPL-3.0 No Details →
1.3.11 22 Jun 2024 H1 U1 GPL-3.0 No Details →
1.3.10 21 Oct 2023 H1 U1 GPL-3.0 No Details →
1.3.9 21 Oct 2023 H1 U1 GPL-3.0 No Details →
1.3.8 04 Jan 2023 H1 U1 GPL-3.0 No Details →
1.3.7 22 Oct 2022 H1 U1 GPL-3.0 No Details →
1.3.6 29 Sep 2021 H1 U1 GPL-3.0 No Details →
1.3.6b1 20 Sep 2021 H1 U1 GPL-3.0 No Details →
1.3.5 05 Sep 2021 H1 U1 GPL-3.0 No Details →
1.3.4 03 Feb 2021 H1 M1 U2 GPL-3.0 No Details →
1.3.4rc1 16 Jan 2021 H1 M1 U2 GPL-3.0 No Details →
1.3.3 02 Jun 2020 H1 M1 U2 GPL-3.0 No Details →
1.3.3rc2 23 May 2020 H1 M1 U2 GPL-3.0 No Details →
1.3.3rc1 10 May 2020 H1 M1 U2 GPL-3.0 No Details →
1.3.2 13 Jan 2020 H1 M1 U2 GPL-3.0 No Details →
1.3.1 12 Dec 2019 H1 M1 U2 GPL-3.0 No Details →
1.3.0 05 Sep 2019 H1 M1 U2 GPL-3.0 No Details →
1.2.4 10 Feb 2019 H1 M1 U2 GPL-3.0 No Details →
1.2.3 19 Jan 2019 H1 M1 U2 GPL-3.0 No Details →
1.2.2 31 Aug 2018 H1 M1 U2 GPL-3.0 No Details →
1.2.1 12 Jul 2018 H1 M1 U2 GPL-3.0 No Details →
1.2.0 11 Jul 2018 H1 M1 U2 GPL-3.0 No Details →
1.2.0a1 11 Mar 2018 H1 M1 U2 GPL-3.0 No Details →
1.1.2 28 Dec 2017 H1 M1 U2 GPL-3.0 No Details →
1.1.1 19 Nov 2017 H1 M1 U2 GPL-3.0 No Details →
1.1.0 26 May 2017 H1 M1 U2 GPL-3.0 No Details →
1.0.2 14 Nov 2015 H1 M1 U2 GPL-3.0 No Details →
1.0.1 28 Apr 2015 H1 M1 U2 GPL-3.0 No Details →
1.0.0 18 Apr 2015 H1 M1 U2 GPL-3.0 No Details →
1.0.0b3 15 Apr 2015 H1 M1 U2 GPL-3.0 No Details →
1.0.0b1 22 Apr 2014 H1 M1 U2 GPL-3.0 No Details →
1.0.0a2 15 Apr 2014 H1 M1 U2 GPL-3.0 No Details →
1.0.3+post2 — H1 M1 U2 GPL-3.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for postorius

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-44742: Postorius XSS Vulnerability in Held Messages Pop-up 7.2 high No fix published 07 May 2026
CVE-2026-44742: Postorius XSS Vulnerability in Message Subject Rendering 7.2 high No fix published 13 Jul 2026
CVE-2021-40347: GNU Mailman Postorius Access Control Issues 5.4 medium 1.3.5 24 May 2022
CVE-2021-40347: Open Redirect Vulnerability in GNU Mailman Postorius N/A unrated 1.3.5 10 Sep 2021

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 postorius

Is postorius safe to use?

Vulert records 4 vulnerabilities for postorius in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is postorius's Vulert package health score?

Vulert scores postorius 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of postorius affected?

Yes. 1.3.13, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of postorius should I use?

1.3.13 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 postorius have?

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

2 vulnerabilities were recorded for postorius in the last 12 months, and the oldest entry in this database dates to 10 Sep 2021. 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 postorius 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 postorius for upcoming vulnerabilities?

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