VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-engineio: vulnerability history, versions and safety

python-engineio is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 115 releases, from Jul 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
6 vulnerabilities recorded H3 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 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 python-engineio vulnerabilities

Vulert verdict on python-engineio 4.14.0 i

Updated on 22 Oct 2026

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

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 4.14.0 — unaffected i
  • Vulnerabilities on record 6 over 6 years · 4 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 2,027 packages i
  • Stars 258 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago 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 python-engineio, 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.14.0 30 Aug 2026 none MIT — Details →
4.13.5 12 Aug 2026 none MIT — Details →
4.13.4 31 Jul 2026 none MIT — Details →
4.13.3 20 Jun 2026 none MIT — Details →
4.13.2 21 May 2026 none MIT — Details →
4.13.1 06 Feb 2026 H2 U2 MIT Yes Details →
4.13.0 24 Dec 2025 H2 U2 MIT Yes Details →
4.12.3 28 Sep 2025 H2 U2 MIT Yes Details →
4.12.2 04 Jun 2025 H2 U2 MIT Yes Details →
4.12.1 11 May 2025 H2 U2 MIT Yes Details →
4.12.0 12 Apr 2025 H2 U2 MIT Yes Details →
4.11.2 29 Dec 2024 H2 U2 MIT Yes Details →
4.11.1 17 Dec 2024 H2 U2 MIT Yes Details →
4.11.0 17 Dec 2024 H2 U2 MIT Yes Details →
4.10.1 15 Oct 2024 H2 U2 MIT Yes Details →
4.10.0 13 Oct 2024 H2 U2 MIT Yes Details →
4.9.1 18 May 2024 H2 U2 MIT Yes Details →
4.9.0 05 Feb 2024 H2 U2 MIT Yes Details →
4.8.2 06 Jan 2024 H2 U2 MIT Yes Details →
4.8.1 28 Dec 2023 H2 U2 MIT Yes Details →
4.8.0 14 Oct 2023 H2 U2 MIT Yes Details →
4.7.1 12 Sep 2023 H2 U2 MIT Yes Details →
4.7.0 03 Sep 2023 H2 U2 MIT Yes Details →
4.6.1 23 Aug 2023 H2 U2 MIT Yes Details →
4.6.0 21 Aug 2023 H2 U2 MIT Yes Details →
4.5.1 05 Jul 2023 H2 U2 MIT Yes Details →
4.5.0 05 Jul 2023 H2 U2 MIT Yes Details →
4.4.1 19 Apr 2023 H2 U2 MIT Yes Details →
4.4.0 16 Mar 2023 H2 U2 MIT Yes Details →
4.3.4 03 Aug 2022 H2 U2 MIT Yes Details →
4.3.3 04 Jul 2022 H2 U2 MIT Yes Details →
4.3.2 24 Apr 2022 H2 U2 MIT Yes Details →
4.3.1 11 Jan 2022 H2 U2 MIT Yes Details →
4.3.0 26 Oct 2021 H2 U2 MIT Yes Details →
4.2.1 01 Aug 2021 H2 U2 MIT Yes Details →
4.2.0 15 May 2021 H2 U2 MIT Yes Details →
4.1.0 15 Apr 2021 H2 U2 MIT Yes Details →
4.0.1 10 Mar 2021 H2 U2 MIT Yes Details →
4.0.0 07 Dec 2020 H2 U2 MIT Yes Details →
3.14.2 30 Nov 2020 H2 U2 MIT Yes Details →
3.14.1 28 Nov 2020 H2 U2 MIT Yes Details →
3.14.0 28 Nov 2020 H2 U2 MIT Yes Details →
3.13.2 18 Aug 2020 H2 U2 MIT Yes Details →
3.13.1 02 Jul 2020 H2 U2 MIT Yes Details →
3.13.0 23 May 2020 H2 U2 MIT Yes Details →
3.12.1 17 Mar 2020 H2 U2 MIT Yes Details →
3.12.0 14 Mar 2020 H2 U2 MIT Yes Details →
3.11.2 03 Jan 2020 H2 U2 MIT Yes Details →
3.11.1 10 Dec 2019 H2 U2 MIT Yes Details →
3.11.0 08 Dec 2019 H2 U2 MIT Yes Details →
3.10.0 22 Oct 2019 H2 U2 MIT Yes Details →
3.9.3 05 Aug 2019 H2 U2 MIT Yes Details →
3.9.2 03 Aug 2019 H2 U2 MIT Yes Details →
3.9.1 02 Aug 2019 H2 U2 MIT Yes Details →
3.9.0 29 Jul 2019 H2 U2 MIT Yes Details →
3.8.2.post1 03 Jul 2019 H3 U3 MIT Yes Details →
3.8.2 29 Jun 2019 H3 U3 MIT Yes Details →
3.8.1 08 Jun 2019 H3 U3 MIT Yes Details →
3.8.0 03 Jun 2019 H3 U3 MIT Yes Details →
3.7.0 29 May 2019 H3 U3 MIT Yes Details →
3.6.0 25 May 2019 H3 U3 MIT Yes Details →
3.5.2 19 May 2019 H3 U3 MIT Yes Details →
3.5.1 07 Apr 2019 H3 U3 MIT Yes Details →
3.5.0 16 Mar 2019 H3 U3 MIT Yes Details →
3.4.4 14 Mar 2019 H3 U3 MIT Yes Details →
3.4.3 20 Feb 2019 H3 U3 MIT Yes Details →
3.4.2 19 Feb 2019 H3 U3 MIT Yes Details →
3.4.1 16 Feb 2019 H3 U3 MIT Yes Details →
3.4.0 16 Feb 2019 H3 U3 MIT Yes Details →
3.3.2 12 Feb 2019 H3 U3 MIT Yes Details →
3.3.1 09 Feb 2019 H3 U3 MIT Yes Details →
3.3.0 23 Jan 2019 H3 U3 MIT Yes Details →
3.2.3 12 Jan 2019 H3 U3 MIT Yes Details →
3.2.2 10 Jan 2019 H3 U3 MIT Yes Details →
3.2.1 09 Jan 2019 H3 U3 MIT Yes Details →
3.2.0 03 Jan 2019 H3 U3 MIT Yes Details →
3.1.2 22 Dec 2018 H3 U3 MIT Yes Details →
3.1.1 20 Dec 2018 H3 U3 MIT Yes Details →
3.1.0 14 Dec 2018 H3 U3 MIT Yes Details →
3.0.0 25 Nov 2018 H3 U3 MIT Yes Details →
2.3.2 09 Oct 2018 H3 U3 MIT Yes Details →
2.3.1 29 Sep 2018 H3 U3 MIT Yes Details →
2.3.0 26 Sep 2018 H3 U3 MIT Yes Details →
2.2.0 28 Jun 2018 H3 U3 MIT Yes Details →
2.1.1 12 May 2018 H3 U3 MIT Yes Details →
2.1.0 27 Apr 2018 H3 U3 MIT Yes Details →
2.0.4 13 Mar 2018 H3 U3 MIT Yes Details →
2.0.3 06 Mar 2018 H3 U3 MIT Yes Details →
2.0.2 05 Jan 2018 H3 U3 MIT Yes Details →
2.0.1 21 Nov 2017 H3 U3 MIT Yes Details →
2.0.0 19 Nov 2017 H3 U3 MIT Yes Details →
1.7.0 17 Nov 2017 H3 U3 MIT Yes Details →
1.6.1 27 Jun 2017 H3 U3 MIT Yes Details →
1.6.0 23 Jun 2017 H3 U3 MIT Yes Details →
1.5.4 30 May 2017 H3 U3 MIT Yes Details →
1.5.3 29 May 2017 H3 U3 MIT Yes Details →
1.5.2 16 May 2017 H3 U3 MIT Yes Details →
1.5.1 09 May 2017 H3 U3 MIT Yes Details →
1.5.0 09 May 2017 H3 U3 MIT Yes Details →
1.4.0 21 Apr 2017 H3 U3 MIT Yes Details →
1.3.2 09 Apr 2017 H3 U3 — Yes Details →
1.3.1 22 Mar 2017 H3 U3 — Yes Details →
1.3.0 08 Mar 2017 H3 U3 — Yes Details →
1.2.4 02 Mar 2017 H3 U3 — Yes Details →
1.2.3 22 Feb 2017 H3 U3 — Yes Details →
1.2.2 15 Feb 2017 H3 U3 — Yes Details →
1.2.1 11 Feb 2017 H3 U3 — Yes Details →
1.2.0 09 Feb 2017 H3 U3 — Yes Details →
1.1.2 30 Jan 2017 H3 U3 — Yes Details →
1.1.1 23 Jan 2017 H3 U3 — Yes Details →
1.1.0 27 Nov 2016 H3 U3 — Yes Details →
1.0.4 26 Nov 2016 H3 U3 — Yes Details →
1.0.3 05 Sep 2016 H3 U3 — Yes Details →
1.0.2 04 Sep 2016 H3 U3 — Yes Details →
1.0.1 01 Sep 2016 H3 U3 — Yes Details →
1.0.0 26 Aug 2016 H3 U3 — Yes Details →
0.9.2 28 Jun 2016 H3 U3 — Yes Details →
0.9.1 15 May 2016 H3 U3 — Yes Details →
0.9.0 06 Mar 2016 H3 U3 — Yes Details →
0.8.8 21 Feb 2016 H3 U3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for python-engineio

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-13611: python-engineio vulnerable to Cross-Site Request Forgery (CSRF) 8.8 high 3.9.0 30 Jul 2019
CVE-2026-48802: python-engineio Denial of Service via Unbound Thread Allocation 7.5 high 4.13.2 26 Jun 2026
CVE-2026-48809: python-engineio Denial of Service Due to Unchecked Payload Size 7.5 high 4.13.2 26 Jun 2026
CVE-2026-48802: python-engineio Denial of Service via Unbound Thread Allocation 7.5 high 4.13.2 13 Jul 2026
CVE-2026-48809: python-engineio Denial of Service Due to Payload Size Enforcement Issue 7.5 high 4.13.2 13 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 python-engineio

Is python-engineio safe to use?

Vulert records 6 vulnerabilities for python-engineio in PyPI: 0 critical, 3 high, 0 medium and 0 low, plus 3 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 python-engineio's Vulert package health score?

Vulert scores python-engineio 73/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 python-engineio affected?

No. 4.14.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 python-engineio should I use?

4.14.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 python-engineio have?

6 vulnerabilities are recorded for python-engineio in the PyPI ecosystem: 0 critical, 3 high, 0 medium and 0 low, plus 3 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 python-engineio vulnerabilities disclosed?

4 vulnerabilities were recorded for python-engineio in the last 12 months, and the oldest entry in this database dates to 16 Jul 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 python-engineio 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 python-engineio for upcoming vulnerabilities?

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