Vulnerability Database · PyPI · pyro · Version

pyro 3.9.1.win32

3.9.1.win32 is affected by 2 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.16.0.

Critical 0 High 1 Medium 0 Low 0 Unrated 1

Licence MIT Also known from other sources 2 Newer releases 8 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

pyro 3.9.1.win32 vulnerabilities

2 vulnerabilities cover pyro 3.9.1.win32. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2011-2765: Pyro mishandles pid files in temporary directory locations and opening the pid file as root 7.5 high 3.15 21 Aug 2018
CVE-2011-2765: pyro Package Arbitrary File Overwrite Vulnerability N/A unrated 554e095a62c4412c91f981e72fd34a936ac2bf1e 20 Aug 2018

Looking for another version, or everything Vulert holds for pyro?

All versions → Full vulnerability list →

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 pyro 3.9.1.win32

Is pyro 3.9.1.win32 vulnerable?

Yes. 2 vulnerabilities in the Vulert database cover pyro 3.9.1.win32: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 3.16.0, and each entry above names the fixed version to move to.

Which version of pyro should I use instead of 3.9.1.win32?

3.16.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

How do I monitor pyro for upcoming vulnerabilities?

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