VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ryu: vulnerability history, versions and safety

ryu is a package in the PyPI ecosystem. Vulert records 18 vulnerabilities for it across 81 releases, from Aug 2023 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
18 vulnerabilities recorded H7 M2 U9
i
18 with no fix published

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

See the unfixed vulnerabilities →
i
9 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 ryu vulnerabilities

Vulert verdict on ryu 4.34.0 i

Updated on 23 Oct 2026

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

Package health score 36/100
  • Security Unfixed issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Not enough data

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 4.34.0 — affected i
  • Vulnerabilities on record 18 over 2 years · 9 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 18 i
  • Depended on by 16 packages i
  • Last release 76 months ago i
  • Licence Apache-2.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 ryu, 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.34.0 27 May 2020 H7 M2 U9 Apache-2.0 No Details →
4.33.0 27 May 2020 H7 M2 U9 Apache-2.0 No Details →
4.32.0 07 May 2019 H7 M2 U9 — No Details →
4.31.0 01 Apr 2019 H7 M2 U9 — No Details →
4.30.0 03 Nov 2018 H7 M2 U9 — No Details →
4.29.0 03 Oct 2018 H7 M2 U9 — No Details →
4.27.0 02 Aug 2018 H7 M2 U9 — No Details →
4.26.0 01 Jul 2018 H7 M2 U9 — No Details →
4.25.0 01 Jun 2018 H7 M2 U9 — No Details →
4.24.0 01 Apr 2018 H7 M2 U9 — No Details →
4.23.0 02 Mar 2018 H7 M2 U9 — No Details →
4.22.0 01 Feb 2018 H7 M2 U9 — No Details →
4.21.0 02 Jan 2018 H7 M2 U9 — No Details →
4.20.0 02 Dec 2017 H7 M2 U9 — No Details →
4.19.0 01 Nov 2017 H7 M2 U9 — No Details →
4.18.0 03 Oct 2017 H7 M2 U9 — No Details →
4.17.0 04 Sep 2017 H7 M2 U9 — No Details →
4.16.0 02 Aug 2017 H7 M2 U9 — No Details →
4.15.0 02 Jul 2017 H7 M2 U9 — No Details →
4.14.0 02 Jun 2017 H7 M2 U9 — No Details →
4.13.0 04 Apr 2017 H7 M2 U9 — No Details →
4.12.0 02 Mar 2017 H7 M2 U9 — No Details →
4.11.0 04 Feb 2017 H7 M2 U9 — No Details →
4.10.0 13 Jan 2017 H7 M2 U9 — No Details →
4.9.0 05 Dec 2016 H7 M2 U9 — No Details →
4.8.1 11 Nov 2016 H7 M2 U9 — No Details →
4.8.0 07 Nov 2016 H7 M2 U9 — No Details →
4.7.0 03 Oct 2016 H7 M2 U9 — No Details →
4.6.0 01 Sep 2016 H7 M2 U9 — No Details →
4.5.0 02 Aug 2016 H7 M2 U9 — No Details →
4.4.0 02 Jul 2016 H7 M2 U9 — No Details →
4.3.0 02 Jun 2016 H7 M2 U9 — No Details →
4.2.2 27 May 2016 H7 M2 U9 — No Details →
4.2.1 19 May 2016 H7 M2 U9 — No Details →
4.1.0 13 May 2016 H7 M2 U9 — No Details →
4.2.0 13 May 2016 H7 M2 U9 — No Details →
4.0.0 03 Mar 2016 H7 M2 U9 — No Details →
3.30.0 02 Feb 2016 H7 M2 U9 — No Details →
3.29.1 12 Jan 2016 H7 M2 U9 — No Details →
3.29.0 04 Jan 2016 H7 M2 U9 — No Details →
3.26.0 01 Oct 2015 H7 M2 U9 — No Details →
3.25.1 24 Sep 2015 H7 M2 U9 — No Details →
3.25.0 03 Sep 2015 H7 M2 U9 — No Details →
3.24.0 03 Aug 2015 H7 M2 U9 — No Details →
3.23.2 07 Jul 2015 H7 M2 U9 — No Details →
3.23.0 02 Jul 2015 H7 M2 U9 — No Details →
3.22.0 04 Jun 2015 H7 M2 U9 — No Details →
3.20.2 20 Apr 2015 H7 M2 U9 — No Details →
3.20.1 16 Apr 2015 H7 M2 U9 — No Details →
3.20.0 03 Apr 2015 H7 M2 U9 — No Details →
3.19.0 02 Mar 2015 H7 M2 U9 — No Details →
3.18.0 04 Feb 2015 H7 M2 U9 — No Details →
3.17.0 05 Jan 2015 H7 M2 U9 — No Details →
3.15.0 01 Nov 2014 H7 M2 U9 — No Details →
3.13.0 01 Sep 2014 H7 M2 U9 — No Details →
3.12.0 01 Aug 2014 H7 M2 U9 — No Details →
3.11.0 03 Jul 2014 H7 M2 U9 — No Details →
3.10.0 05 Jun 2014 H7 M2 U9 — No Details →
3.9.0 02 May 2014 H7 M2 U9 — No Details →
3.8.0 10 Apr 2014 H7 M2 U9 — No Details →
3.7.0 12 Mar 2014 H7 M2 U9 — No Details →
3.6.0 03 Feb 2014 H7 M2 U9 — No Details →
3.5.0 07 Jan 2014 H7 M2 U9 — No Details →
3.4.0 03 Dec 2013 H7 M2 U9 — No Details →
3.3.0 01 Nov 2013 H7 M2 U9 — No Details →
3.2.0 07 Oct 2013 H7 M2 U9 — No Details →
3.1.0 05 Oct 2013 H7 M2 U9 — No Details →
2.2.0 01 Aug 2013 H7 M2 U9 Apache-2.0 No Details →
2.1.0 30 Jun 2013 H7 M2 U9 Apache-2.0 No Details →
2.0.0 10 Jun 2013 H7 M2 U9 Apache-2.0 No Details →
1.9.0 01 May 2013 H7 M2 U9 Apache-2.0 No Details →
1.8.0 01 Apr 2013 H7 M2 U9 Apache-2.0 No Details →
1.7.0 27 Feb 2013 H7 M2 U9 Apache-2.0 No Details →
1.6.0 29 Jan 2013 H7 M2 U9 Apache-2.0 No Details →
1.5.0 30 Nov 2012 H7 M2 U9 Apache-2.0 No Details →
1.4.0 31 Oct 2012 H7 M2 U9 Apache-2.0 No Details →
1.3.0 30 Sep 2012 H7 M2 U9 Apache-2.0 No Details →
1.2.0 31 Aug 2012 H7 M2 U9 Apache-2.0 No Details →
1.1.0 30 Jul 2012 H7 M2 U9 Apache-2.0 No Details →
1.0.0 30 Jun 2012 H7 M2 U9 Apache-2.0 No Details →
0.2.0 16 Jun 2012 H7 M2 U9 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 7
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for ryu

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35139: FaucetSDN Ryu Denial of Service Vulnerability 7.5 high No fix published 11 Aug 2023
CVE-2020-35141: FaucetSDN Ryu Denial of Service Vulnerability 7.5 high No fix published 11 Aug 2023
CVE-2024-28732: Ryu Package Infinite Loop Vulnerability 7.5 high No fix published 07 Jul 2026
CVE-2020-35141: Ryu Denial of Service Vulnerability in FaucetSDN 7.5 high No fix published 07 Jul 2026
CVE-2024-34489: Ryu Package Denial of Service via Infinite Loop in OFPHello 7.5 high No fix published 07 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: 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 ryu

Is ryu safe to use?

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

What is ryu's Vulert package health score?

Vulert scores ryu 36/100, which reads as risky. 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 ryu affected?

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

Which version of ryu should I use?

4.34.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 ryu have?

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

9 vulnerabilities were recorded for ryu in the last 12 months, and the oldest entry in this database dates to 11 Aug 2023. 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 ryu 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 ryu for upcoming vulnerabilities?

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