Vulnerability Database · PyPI · Package report

typed-ast: vulnerability history, versions and safety

typed-ast is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 35 releases, from Nov 2019 to Dec 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 U4
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.

Vulert verdict on typed-ast 1.5.5 i

Updated on 23 Oct 2026

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

Package health score 64/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.5.5 — affected i
  • Vulnerabilities on record 6 over 1 year · 0 in the last year i
  • Latest disclosure 02 Dec 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 289 packages i
  • Stars 234 i
  • OpenSSF scorecard 3/10 i
  • Last release 39 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 typed-ast, 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.5.5 04 Jul 2023 U4 Apache-2.0 Yes Details →
1.5.4 21 May 2022 U4 Apache-2.0 Yes Details →
1.5.3 16 Apr 2022 U4 Apache-2.0 Yes Details →
1.5.2 24 Jan 2022 U4 Apache-2.0 Yes Details →
1.5.1 03 Dec 2021 U4 Apache-2.0 Yes Details →
1.5.0 12 Nov 2021 U4 Apache-2.0 Yes Details →
1.4.3 11 Apr 2021 U4 Apache-2.0 Yes Details →
1.4.2 30 Dec 2020 U4 Apache-2.0 Yes Details →
1.4.1 25 Oct 2020 U4 Apache-2.0 Yes Details →
1.4.0 16 Oct 2019 U4 Apache-2.0 Yes Details →
1.3.5 28 Apr 2019 U4 Apache-2.0 Yes Details →
1.3.4 18 Apr 2019 U4 Apache-2.0 Yes Details →
1.3.2 17 Apr 2019 U4 Apache-2.0 Yes Details →
1.3.1 06 Feb 2019 H2 U4 Apache-2.0 Yes Details →
1.3.0 30 Jan 2019 H2 U4 Apache-2.0 Yes Details →
1.1.2 15 Jan 2019 U4 Apache-2.0 Yes Details →
1.2.0 14 Jan 2019 U4 Apache-2.0 Yes Details →
1.1.1 17 Dec 2018 U4 Apache-2.0 Yes Details →
1.1.0 03 Jul 2018 U4 Apache-2.0 Yes Details →
1.0.4 14 Jun 2017 U4 Apache-2.0 Yes Details →
1.0.3 10 Apr 2017 U4 Apache-2.0 Yes Details →
1.0.2 06 Mar 2017 U4 Apache-2.0 Yes Details →
1.0.1 24 Feb 2017 U4 Apache-2.0 Yes Details →
1.0.0 13 Feb 2017 U4 Apache-2.0 Yes Details →
0.6.3 06 Jan 2017 U4 Apache-2.0 Yes Details →
0.6.2 05 Jan 2017 U4 Apache-2.0 Yes Details →
0.6.1 30 Sep 2016 U4 Apache-2.0 Yes Details →
0.6.0 27 Sep 2016 U4 Apache-2.0 Yes Details →
0.5.6 25 Aug 2016 U4 Apache-2.0 Yes Details →
0.5.5 24 Jun 2016 U4 Apache-2.0 Yes Details →
0.5.4 23 Jun 2016 U4 Apache-2.0 Yes Details →
0.5.3 22 Jun 2016 U4 Apache-2.0 Yes Details →
0.5.2 01 Jun 2016 U4 Apache-2.0 Yes Details →
0.5.1 28 Apr 2016 U4 Apache-2.0 Yes Details →
0.5.0 28 Apr 2016 U4 Apache-2.0 Yes Details →

All 35 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 6

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

03 Vulnerabilities

Recorded vulnerabilities for typed-ast

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-19275: Out-of-bounds read in typed-ast and cpython 7.5 high 1.3.2 02 Dec 2019
CVE-2019-19274: Out-of-bounds read in typed-ast and cpython 7.5 high 1.3.2 02 Dec 2019
CVE-2019-19274: typed-ast Out-of-Bounds Read Vulnerability N/A unrated 156afcb26c198e162504a57caddfe0acd9ed7dce 26 Nov 2019
CVE-2019-19275: typed-ast Out-of-Bounds Read Vulnerability N/A unrated 156afcb26c198e162504a57caddfe0acd9ed7dce 26 Nov 2019
CVE-2019-19274: typed-ast Out-of-Bounds Read Vulnerability N/A unrated 156afcb26c198e162504a57caddfe0acd9ed7dce 26 Nov 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 typed-ast

Is typed-ast safe to use?

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

Vulert scores typed-ast 64/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 typed-ast affected?

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

Which version of typed-ast should I use?

1.5.5 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 typed-ast have?

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

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

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