VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@babel/traverse: vulnerability history, versions and safety

@babel/traverse is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 44 releases, first recorded in Oct 2023. 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 C2
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 @babel/traverse vulnerabilities

Vulert verdict on @babel/traverse 8.0.7 i

Updated on 22 Oct 2026

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

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.0.7 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 16 Oct 2023 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 2,577 packages i
  • Stars 44,062 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 @babel/traverse, 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
8.0.7 07 Oct 2026 none MIT — Details →
7.29.10 07 Oct 2026 none MIT — Details →
8.0.6 18 Sep 2026 none MIT — Details →
8.0.5 10 Sep 2026 none MIT — Details →
7.29.8 31 Jul 2026 none MIT — Details →
8.0.4 09 Jul 2026 none MIT — Details →
8.0.0 16 Jun 2026 none MIT — Details →
7.29.7 25 May 2026 none MIT — Details →
8.0.0-rc.6 25 May 2026 none MIT — Details →
8.0.0-rc.5 12 May 2026 none MIT — Details →
8.0.0-rc.4 29 Apr 2026 none MIT — Details →
8.0.0-rc.3 16 Mar 2026 none MIT — Details →
8.0.0-rc.2 15 Feb 2026 none MIT — Details →
8.0.0-rc.1 31 Jan 2026 none MIT — Details →
7.29.0 31 Jan 2026 none MIT — Details →
7.28.6 12 Jan 2026 none MIT — Details →
8.0.0-beta.4 12 Jan 2026 none MIT — Details →
7.28.5 23 Oct 2025 none MIT — Details →
8.0.0-beta.3 23 Oct 2025 none MIT — Details →
8.0.0-beta.2 05 Sep 2025 none MIT — Details →
7.28.4 05 Sep 2025 none MIT — Details →
7.28.3 14 Aug 2025 none MIT — Details →
8.0.0-beta.1 02 Jul 2025 none MIT — Details →
7.28.0 02 Jul 2025 none MIT — Details →
7.27.7 26 Jun 2025 none MIT — Details →
8.0.0-beta.0 30 May 2025 none MIT — Details →
7.27.4 30 May 2025 none MIT — Details →
7.27.3 27 May 2025 none MIT — Details →
7.27.1 30 Apr 2025 none MIT — Details →
7.27.0 24 Mar 2025 none MIT — Details →
8.0.0-alpha.17 11 Mar 2025 none MIT — Details →
7.26.10 11 Mar 2025 none MIT — Details →
8.0.0-alpha.16 14 Feb 2025 none MIT — Details →
7.26.9 14 Feb 2025 none MIT — Details →
7.26.8 08 Feb 2025 none MIT — Details →
7.26.7 24 Jan 2025 none MIT — Details →
8.0.0-alpha.15 10 Jan 2025 none MIT — Details →
7.26.5 10 Jan 2025 none MIT — Details →
8.0.0-alpha.14 06 Dec 2024 none MIT — Details →
7.26.4 05 Dec 2024 none MIT — Details →
7.26.3 04 Dec 2024 none MIT — Details →
8.0.0-alpha.13 25 Oct 2024 none MIT — Details →
7.25.9 22 Oct 2024 none MIT — Details →
7.25.7 02 Oct 2024 none MIT — Details →
7.25.6 29 Aug 2024 none MIT — Details →
7.25.4 22 Aug 2024 none MIT — Details →
7.25.3 31 Jul 2024 none MIT — Details →
7.25.2 30 Jul 2024 none MIT — Details →
7.25.1 28 Jul 2024 none MIT — Details →
8.0.0-alpha.12 26 Jul 2024 none MIT — Details →
7.25.0 26 Jul 2024 none MIT — Details →
7.24.8 11 Jul 2024 none MIT — Details →
8.0.0-alpha.11 07 Jun 2024 none MIT — Details →
7.24.7 05 Jun 2024 none MIT — Details →
8.0.0-alpha.10 04 Jun 2024 none MIT — Details →
8.0.0-alpha.9 03 Jun 2024 none MIT — Details →
7.24.6 24 May 2024 none MIT — Details →
7.24.5 29 Apr 2024 none MIT — Details →
8.0.0-alpha.8 04 Apr 2024 none MIT — Details →
7.24.1 19 Mar 2024 none MIT — Details →
8.0.0-alpha.7 28 Feb 2024 none MIT — Details →
7.24.0 28 Feb 2024 none MIT — Details →
8.0.0-alpha.6 26 Jan 2024 none MIT — Details →
7.23.9 25 Jan 2024 none MIT — Details →
7.23.7 29 Dec 2023 none MIT — Details →
8.0.0-alpha.5 11 Dec 2023 none MIT — Details →
7.23.6 11 Dec 2023 none MIT — Details →
7.23.5 29 Nov 2023 none MIT — Details →
7.23.4 20 Nov 2023 none MIT — Details →
7.23.3 09 Nov 2023 none MIT — Details →
8.0.0-alpha.4 12 Oct 2023 none MIT — Details →
7.23.2 11 Oct 2023 none MIT — Details →
8.0.0-alpha.3 26 Sep 2023 none MIT — Details →
7.23.0 25 Sep 2023 C2 MIT Yes Details →
7.22.20 16 Sep 2023 C2 MIT Yes Details →
7.22.19 14 Sep 2023 C2 MIT Yes Details →
7.22.18 14 Sep 2023 C2 MIT Yes Details →
7.22.17 08 Sep 2023 C2 MIT Yes Details →
7.22.15 04 Sep 2023 C2 MIT Yes Details →
7.22.11 24 Aug 2023 C2 MIT Yes Details →
8.0.0-alpha.2 09 Aug 2023 none MIT — Details →
7.22.10 07 Aug 2023 C2 MIT Yes Details →
8.0.0-alpha.1 24 Jul 2023 none MIT — Details →
8.0.0-alpha.0 20 Jul 2023 none MIT — Details →
7.22.8 06 Jul 2023 C2 MIT Yes Details →
7.22.7 06 Jul 2023 C2 MIT Yes Details →
7.22.6 04 Jul 2023 C2 MIT Yes Details →
7.22.5 08 Jun 2023 C2 MIT Yes Details →
7.22.4 29 May 2023 C2 MIT Yes Details →
7.22.1 26 May 2023 C2 MIT Yes Details →
7.22.0 26 May 2023 C2 MIT Yes Details →
7.21.5 28 Apr 2023 C2 MIT Yes Details →
7.21.4-esm.4 04 Apr 2023 C2 MIT Yes Details →
7.21.4-esm.3 04 Apr 2023 C2 MIT Yes Details →
7.21.4-esm.2 04 Apr 2023 C2 MIT Yes Details →
7.21.4-esm.1 04 Apr 2023 C2 MIT Yes Details →
7.21.4-esm 04 Apr 2023 C2 MIT Yes Details →
7.21.4 31 Mar 2023 C2 MIT Yes Details →
7.21.3 14 Mar 2023 C2 MIT Yes Details →
7.21.2 23 Feb 2023 C2 MIT Yes Details →
7.21.0 20 Feb 2023 C2 — Yes Details →
7.20.13 21 Jan 2023 C2 — Yes Details →
7.20.12 04 Jan 2023 C2 — Yes Details →
7.20.10 23 Dec 2022 C2 — Yes Details →
7.20.8 22 Dec 2022 C2 — Yes Details →
7.20.7 22 Dec 2022 C2 — Yes Details →
7.20.5 28 Nov 2022 C2 — Yes Details →
7.20.1 01 Nov 2022 C2 — Yes Details →
7.20.0 27 Oct 2022 C2 — Yes Details →
7.19.6 20 Oct 2022 C2 — Yes Details →
7.19.4 10 Oct 2022 C2 — Yes Details →
7.19.3 27 Sep 2022 C2 — Yes Details →
7.19.1 14 Sep 2022 C2 — Yes Details →
7.19.0 05 Sep 2022 C2 — Yes Details →
7.18.13 22 Aug 2022 C2 — Yes Details →
7.18.11 04 Aug 2022 C2 — Yes Details →
7.18.10 01 Aug 2022 C2 — Yes Details →
7.18.9 18 Jul 2022 C2 — Yes Details →
7.18.8 08 Jul 2022 C2 — Yes Details →
7.18.6 27 Jun 2022 C2 — Yes Details →

The newest 120 of 224 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 @babel/traverse

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-45133: Babel vulnerable to arbitrary code execution 9.3 critical 7.23.2 16 Oct 2023
CVE-2023-45133: Babel vulnerable to arbitrary code execution 9.3 critical 7.23.2 16 Oct 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524171

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About @babel/traverse

Is @babel/traverse safe to use?

Vulert records 2 vulnerabilities for @babel/traverse in npm: 2 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @babel/traverse's Vulert package health score?

Vulert scores @babel/traverse 85/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 @babel/traverse affected?

No. 8.0.7, 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 @babel/traverse should I use?

8.0.7 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 @babel/traverse have?

2 vulnerabilities are recorded for @babel/traverse in the npm ecosystem: 2 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @babel/traverse vulnerabilities disclosed?

0 vulnerabilities were recorded for @babel/traverse in the last 12 months, and the oldest entry in this database dates to 16 Oct 2023. 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 @babel/traverse 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 @babel/traverse for upcoming vulnerabilities?

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