VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pywin32: vulnerability history, versions and safety

pywin32 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Jul 2021 to Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pywin32 vulnerabilities

Vulert verdict on pywin32 312.0.0 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 312.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Aug 2021 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 1,168 packages 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 pywin32, 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
222.0.0 — H1 U1 — Yes Details →
223.0.0 — H1 U1 — Yes Details →
224.0.0 — H1 U1 — Yes Details →
225.0.0 — H1 U1 — Yes Details →
226.0.0 — H1 U1 — Yes Details →
227.0.0 — H1 U1 — Yes Details →
228.0.0 — H1 U1 — Yes Details →
300.0.0 — H1 U1 — Yes Details →
301.0.0 — none — — Details →
302.0.0 — none — — Details →
303.0.0 — none — — Details →
304.0.0 — none — — Details →
305.0.0 — none — — Details →
306.0.0 — none — — Details →
307.0.0 — none — — Details →
308.0.0 — none — — Details →
309.0.0 — none — — Details →
310.0.0 — none — — Details →
311.0.0 — none — — Details →
312.0.0 — none — — Details →

All 20 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for pywin32

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-32559: Integer overflow in pywin32 6.5 high 301 09 Aug 2021
CVE-2021-32559: Integer Overflow in pywin32 Prior to Version b301 N/A unrated 301 06 Jul 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 pywin32

Is pywin32 safe to use?

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

Vulert scores pywin32 90/100, which reads as healthy. 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 pywin32 affected?

No. 312.0.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 pywin32 should I use?

312.0.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 pywin32 have?

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

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

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