VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

matrix-synapse: vulnerability history, versions and safety

matrix-synapse is a package in the PyPI ecosystem. Vulert records 88 vulnerabilities for it across 120 releases, from Mar 2019 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
88 vulnerabilities recorded H20 M21 L3 U44
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
15 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all matrix-synapse vulnerabilities

Vulert verdict on matrix-synapse 1.163.0 i

Updated on 23 Oct 2026

Action needed: 1.163.0 has 5 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 55/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.163.0 — affected i
  • Vulnerabilities on record 88 over 7 years · 15 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 7 packages i
  • Stars 4,716 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 matrix-synapse, 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.164.0rc1 20 Oct 2026 U5 non-standard Yes Details →
1.163.0 14 Oct 2026 U5 non-standard Yes Details →
1.163.0rc1 06 Oct 2026 U5 non-standard Yes Details →
1.162.0 29 Sep 2026 U5 non-standard Yes Details →
1.162.0rc1 22 Sep 2026 U5 non-standard Yes Details →
1.161.0 15 Sep 2026 U5 non-standard Yes Details →
1.161.0rc1 09 Sep 2026 U5 non-standard Yes Details →
1.160.0 02 Sep 2026 U5 non-standard Yes Details →
1.160.0rc2 31 Aug 2026 U5 non-standard Yes Details →
1.160.0rc1 25 Aug 2026 U5 non-standard Yes Details →
1.159.0 18 Aug 2026 U5 non-standard Yes Details →
1.159.0rc1 11 Aug 2026 U5 non-standard Yes Details →
1.158.0 04 Aug 2026 U5 non-standard Yes Details →
1.158.0rc1 30 Jul 2026 U5 non-standard Yes Details →
1.157.2 28 Jul 2026 U5 non-standard Yes Details →
1.157.1 22 Jul 2026 U5 non-standard Yes Details →
1.157.0 21 Jul 2026 U5 non-standard Yes Details →
1.157.0rc1 15 Jul 2026 U5 non-standard Yes Details →
1.156.0 07 Jul 2026 U5 non-standard Yes Details →
1.156.0rc1 30 Jun 2026 U5 non-standard Yes Details →
1.155.0 16 Jun 2026 U5 non-standard Yes Details →
1.155.0rc1 09 Jun 2026 U5 non-standard Yes Details →
1.154.0 04 Jun 2026 U5 non-standard Yes Details →
1.154.0rc1 27 May 2026 U5 non-standard Yes Details →
1.153.0 19 May 2026 U5 non-standard Yes Details →
1.153.0rc3 15 May 2026 U5 non-standard Yes Details →
1.153.0rc2 13 May 2026 U5 non-standard Yes Details →
1.153.0rc1 08 May 2026 U5 non-standard Yes Details →
1.152.1 07 May 2026 U5 non-standard Yes Details →
1.152.0 28 Apr 2026 H1 M1 U2 non-standard Yes Details →
1.152.0rc1 22 Apr 2026 H1 M1 U2 non-standard Yes Details →
1.151.0 07 Apr 2026 H1 M1 U2 non-standard Yes Details →
1.151.0rc1 31 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.150.0 24 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.150.0rc1 17 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.149.1 11 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.149.0 10 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.149.0rc1 03 Mar 2026 H1 M1 U2 non-standard Yes Details →
1.148.0 24 Feb 2026 H1 M1 U2 non-standard Yes Details →
1.148.0rc1 17 Feb 2026 H1 M1 U2 non-standard Yes Details →
1.147.1 12 Feb 2026 H1 M1 U2 non-standard Yes Details →
1.147.0 10 Feb 2026 H1 M1 U2 non-standard Yes Details →
1.147.0rc1 03 Feb 2026 H1 M1 U2 non-standard Yes Details →
1.146.0 27 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.146.0rc1 20 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.145.0 13 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.145.0rc4 08 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.145.0rc3 07 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.145.0rc2 07 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.145.0rc1 07 Jan 2026 H1 M1 U2 non-standard Yes Details →
1.144.0 09 Dec 2025 H1 M1 U2 non-standard Yes Details →
1.144.0rc1 02 Dec 2025 H1 M1 U2 non-standard Yes Details →
1.143.0 25 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.143.0rc2 19 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.142.1 18 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.142.0 11 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.142.0rc4 07 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.142.0rc3 04 Nov 2025 H1 M1 U2 non-standard Yes Details →
1.141.0 29 Oct 2025 H1 M1 U2 non-standard Yes Details →
1.141.0rc2 28 Oct 2025 H1 M1 U2 non-standard Yes Details →
1.141.0rc1 21 Oct 2025 H1 M1 U2 non-standard Yes Details →
1.140.0 14 Oct 2025 H1 M1 U2 non-standard Yes Details →
1.140.0rc1 10 Oct 2025 H1 M1 U2 non-standard Yes Details →
1.139.2 08 Oct 2025 H1 M1 U2 AGPL-3.0-or-later Yes Details →
1.138.4 08 Oct 2025 H1 M1 U2 AGPL-3.0-or-later Yes Details →
1.138.3 07 Oct 2025 H1 M1 U2 AGPL-3.0-or-later Yes Details →
1.139.1 07 Oct 2025 H1 M1 U2 AGPL-3.0-or-later Yes Details →
1.139.0 01 Oct 2025 H1 M1 U3 AGPL-3.0-or-later Yes Details →
1.139.0rc3 25 Sep 2025 H1 M1 U3 AGPL-3.0-or-later Yes Details →
1.138.2 24 Sep 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.139.0rc2 23 Sep 2025 H1 M1 U3 AGPL-3.0-or-later Yes Details →
1.138.0 09 Sep 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.138.0rc1 02 Sep 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.137.0 26 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.137.0rc1 19 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.136.0 12 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.136.0rc2 11 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.135.2 11 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.136.0rc1 07 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.135.0 01 Aug 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.135.0rc2 30 Jul 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.135.0rc1 22 Jul 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.134.0 15 Jul 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.134.0rc1 09 Jul 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.133.0 01 Jul 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.133.0rc1 24 Jun 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.132.0 17 Jun 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.132.0rc1 10 Jun 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.131.0 03 Jun 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.131.0rc1 28 May 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.130.0 20 May 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.130.0rc1 13 May 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.129.0 06 May 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.129.0rc2 30 Apr 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.128.0 08 Apr 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.128.0rc1 01 Apr 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.127.1 26 Mar 2025 H1 M2 U3 AGPL-3.0-or-later Yes Details →
1.127.0 25 Mar 2025 H2 M2 U4 AGPL-3.0-or-later Yes Details →
1.127.0rc1 18 Mar 2025 H2 M2 U4 AGPL-3.0-or-later Yes Details →
1.126.0 11 Mar 2025 H2 M2 U4 AGPL-3.0-or-later Yes Details →
1.126.0rc3 07 Mar 2025 H2 M2 U4 — Yes Details →
1.126.0rc2 05 Mar 2025 H2 M2 U4 — Yes Details →
1.125.0 25 Feb 2025 H2 M2 U4 — Yes Details →
1.125.0rc1 18 Feb 2025 H2 M2 U4 — Yes Details →
1.124.0 11 Feb 2025 H2 M2 U4 — Yes Details →
1.124.0rc3 07 Feb 2025 H2 M2 U4 — Yes Details →
1.124.0rc2 05 Feb 2025 H2 M2 U4 — Yes Details →
1.124.0rc1 04 Feb 2025 H2 M2 U4 — Yes Details →
1.123.0 28 Jan 2025 H2 M2 U4 — Yes Details →
1.123.0rc1 21 Jan 2025 H2 M2 U4 — Yes Details →
1.122.0 14 Jan 2025 H2 M2 U4 — Yes Details →
1.122.0rc1 07 Jan 2025 H2 M2 U4 — Yes Details →
1.121.1 11 Dec 2024 H2 M2 U4 — Yes Details →
1.121.0 11 Dec 2024 H2 M2 U4 — Yes Details →
1.121.0rc1 04 Dec 2024 H2 M2 U4 — Yes Details →
1.120.2 03 Dec 2024 H2 M2 U4 — Yes Details →
1.120.0 26 Nov 2024 H5 M3 U8 — Yes Details →
1.120.0rc1 20 Nov 2024 H5 M3 U8 — Yes Details →
1.119.0 13 Nov 2024 H5 M3 U8 — Yes Details →
1.119.0rc2 11 Nov 2024 H5 M3 U8 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2020 6
  • 2021 23
  • 2022 11
  • 2023 18
  • 2024 10
  • 2025 2
  • 2026 15

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

03 Vulnerabilities

Recorded vulnerabilities for matrix-synapse

The 5 most severe of 88 vulnerabilities recorded for this package

Search all 88 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-16515: Matrix Synapse Improper Signature Validation 8.8 high 0.33.3.1 13 May 2022
CVE-2018-16515: Matrix Synapse Improper Signature Validation Vulnerability 8.8 high 0.33.2.1 06 Jul 2026
CVE-2024-52815: matrix-synapse Malformed Invite Vulnerability Disrupts Sync Functionality 8.7 high 1.120.1 07 Jul 2026
CVE-2024-52815: Matrix Synapse Malformed Invite Vulnerability Disrupts Sync Functionality 8.7 high 1.120.1 03 Dec 2024
CVE-2019-18835: Improper Verification of Cryptographic Signature in matrix-synapse 8.6 high 1.5.0 24 May 2022

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 matrix-synapse

Is matrix-synapse safe to use?

Vulert records 88 vulnerabilities for matrix-synapse in PyPI: 0 critical, 20 high, 21 medium and 3 low, plus 44 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 matrix-synapse's Vulert package health score?

Vulert scores matrix-synapse 55/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).

Is the latest version of matrix-synapse affected?

Yes. 1.163.0, the version you would install today, has 5 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of matrix-synapse should I use?

1.163.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 matrix-synapse have?

88 vulnerabilities are recorded for matrix-synapse in the PyPI ecosystem: 0 critical, 20 high, 21 medium and 3 low, plus 44 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 matrix-synapse vulnerabilities disclosed?

15 vulnerabilities were recorded for matrix-synapse in the last 12 months, and the oldest entry in this database dates to 21 Mar 2019. 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 matrix-synapse 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 matrix-synapse for upcoming vulnerabilities?

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