VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

parlai: vulnerability history, versions and safety

parlai is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 25 releases, first recorded in Sep 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 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 parlai vulnerabilities

Vulert verdict on parlai 1.7.2 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

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.7.2 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 13 Sep 2021 i
  • Highest CVSS 8.4 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Last release 40 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 parlai, 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.7.2 06 Jun 2023 U1 MIT Yes Details →
1.7.1 16 Sep 2022 U1 MIT Yes Details →
1.7.0 23 Aug 2022 U1 MIT Yes Details →
1.6.0 30 Mar 2022 U1 MIT Yes Details →
1.5.1 12 Oct 2021 U1 MIT Yes Details →
1.5.0 25 Aug 2021 U1 MIT Yes Details →
1.4.1 23 Jul 2021 U1 MIT Yes Details →
1.4.0 22 Jul 2021 U1 MIT Yes Details →
1.3.0 07 Jul 2021 U1 MIT Yes Details →
1.2.0 23 Apr 2021 U1 MIT Yes Details →
1.1.1 17 Mar 2021 U1 MIT Yes Details →
1.1.0 01 Mar 2021 U1 MIT Yes Details →
1.0.0 19 Jan 2021 M2 U2 MIT Yes Details →
0.10.0 16 Dec 2020 M2 U2 MIT Yes Details →
0.9.4 16 Oct 2020 M2 U2 MIT Yes Details →
0.9.3 28 Sep 2020 M2 U2 MIT Yes Details →
0.9.2 10 Sep 2020 M2 U2 MIT Yes Details →
0.9.1 08 Sep 2020 M2 U2 MIT Yes Details →
0.9.0 18 Aug 2020 M2 U2 MIT Yes Details →
0.8.0 04 Aug 2020 M2 U2 MIT Yes Details →
0.1.20200716 16 Jul 2020 M2 U2 MIT Yes Details →
0.1.20200713 13 Jul 2020 M2 U2 MIT Yes Details →
0.1.20200610 11 Jun 2020 M2 U2 MIT Yes Details →
0.1.20200416 17 Apr 2020 M2 U2 MIT Yes Details →
0.1.20200409 09 Apr 2020 M2 U2 MIT Yes Details →

All 25 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 4

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

03 Vulnerabilities

Recorded vulnerabilities for parlai

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-39207: Deserialization of Untrusted Data in parlai 8.4 medium 1.1.0 13 Sep 2021
CVE-2021-24040: Deserialization of Untrusted Data in ParlAI N/A medium 1.1.0 13 Sep 2021
CVE-2021-24040: Unsafe YAML Deserialization in ParlAI N/A unrated 1.1.0 10 Sep 2021
CVE-2021-39207: YAML Deserialization Attack in parlai N/A unrated 507d066ef432ea27d3e201da08009872a2f37725 10 Sep 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 parlai

Is parlai safe to use?

Vulert records 4 vulnerabilities for parlai in PyPI: 0 critical, 0 high, 2 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 parlai's Vulert package health score?

Vulert scores parlai 69/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 parlai affected?

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

Which version of parlai should I use?

1.7.2 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 parlai have?

4 vulnerabilities are recorded for parlai in the PyPI ecosystem: 0 critical, 0 high, 2 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 parlai vulnerabilities disclosed?

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

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