VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

steam: vulnerability history, versions and safety

steam is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 60 releases, first recorded in Oct 2019. 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 U2
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 steam vulnerabilities

Vulert verdict on steam 1.4.4 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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.4.4 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Oct 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 19 packages i
  • Stars 1,290 i
  • OpenSSF scorecard 2/10 i
  • Last release 46 months 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 steam, 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.4.4 10 Dec 2022 U2 MIT Yes Details →
1.4.3 09 Oct 2022 U2 MIT Yes Details →
1.4.2 09 Oct 2022 U2 MIT Yes Details →
1.4.1 05 Oct 2022 U2 MIT Yes Details →
1.4.0 04 Oct 2022 U2 MIT Yes Details →
1.3.0 15 May 2022 U2 MIT Yes Details →
1.2.1 03 May 2022 U2 MIT Yes Details →
1.2.0 06 Feb 2021 U2 MIT Yes Details →
1.1.1 15 Dec 2020 U2 MIT Yes Details →
1.1.0 15 Dec 2020 U2 MIT Yes Details →
1.0.2 06 Jun 2020 U2 MIT Yes Details →
1.0.1 23 May 2020 U2 MIT Yes Details →
1.0.0 02 May 2020 U2 MIT Yes Details →
1.0.0a8 25 Apr 2020 U2 MIT Yes Details →
1.0.0a7 18 Apr 2020 U2 MIT Yes Details →
1.0.0a6 03 Sep 2019 U2 MIT Yes Details →
1.0.0a5 03 Sep 2019 U2 MIT Yes Details →
1.0.0a4 20 Jul 2019 U2 MIT Yes Details →
1.0.0a3 20 Jul 2019 U2 MIT Yes Details →
1.0.0a2 14 Jul 2019 U2 MIT Yes Details →
1.0.0a1 06 Jul 2019 U2 MIT Yes Details →
0.9.1 22 Jun 2019 U2 MIT Yes Details →
0.9.0 27 Feb 2018 U2 MIT Yes Details →
0.8.23 26 Dec 2017 U2 MIT Yes Details →
0.8.22 03 Oct 2017 U2 MIT Yes Details →
0.8.21 03 Sep 2017 U2 MIT Yes Details →
0.8.20 23 Jul 2017 U2 MIT Yes Details →
0.8.19 22 Jul 2017 U2 MIT Yes Details →
0.8.18 26 Apr 2017 U2 MIT Yes Details →
0.8.17 17 Apr 2017 U2 MIT Yes Details →
0.8.16 15 Apr 2017 U2 MIT Yes Details →
0.8.15 20 Feb 2017 U2 MIT Yes Details →
0.8.14 11 Jan 2017 U2 MIT Yes Details →
0.8.13 30 Nov 2016 U2 MIT Yes Details →
0.8.12 28 Nov 2016 U2 MIT Yes Details →
0.8.11 28 Nov 2016 U2 MIT Yes Details →
0.8.10 23 Nov 2016 U2 MIT Yes Details →
0.8.9 04 Nov 2016 U2 MIT Yes Details →
0.8.8 26 Sep 2016 U2 MIT Yes Details →
0.8.7 14 Aug 2016 U2 MIT Yes Details →
0.8.6 06 Aug 2016 U2 MIT Yes Details →
0.8.5 31 Jul 2016 U2 MIT Yes Details →
0.8.4 29 Jul 2016 U2 MIT Yes Details →
0.8.3 22 Jun 2016 U2 MIT Yes Details →
0.8.2 27 May 2016 U2 MIT Yes Details →
0.8.1 25 May 2016 U2 MIT Yes Details →
0.8.0 22 May 2016 U2 MIT Yes Details →
0.7.5 21 May 2016 U2 MIT Yes Details →
0.7.4 14 May 2016 U2 MIT Yes Details →
0.7.3 26 Apr 2016 U2 MIT Yes Details →
0.7.2 14 Apr 2016 U2 MIT Yes Details →
0.7.1 14 Apr 2016 U2 MIT Yes Details →
0.6.7 30 Mar 2016 U2 MIT Yes Details →
0.6.6 22 Mar 2016 U2 MIT Yes Details →
0.6.5 28 Feb 2016 U2 MIT Yes Details →
0.5.4 24 Nov 2015 U2 MIT Yes Details →
0.5.3 22 Nov 2015 U2 MIT Yes Details →
0.5.2 15 Nov 2015 U2 MIT Yes Details →
0.5.1 22 Jul 2015 U2 MIT Yes Details →
0.5.0 22 Jul 2015 U2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 steam

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17180: Valve Steam Client File Modification Vulnerability N/A unrated 2019-09-12 04 Oct 2019
CVE-2019-17180: Valve Steam Client allows placing or appending partially controlled filesystem content N/A unrated 2019-09-12 04 Oct 2019

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 steam

Is steam safe to use?

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

Vulert scores steam 67/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 steam affected?

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

Which version of steam should I use?

1.4.4 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 steam have?

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

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

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