Is @babel/traverse 7.17 vulnerable?

npm · 5 releases from 7.17.0 to 7.17.12 · latest @babel/traverse is 8.0.10 · checked 1 Nov 2026

Yes: 1 known advisory

Yes. @babel/traverse 7.17.12, the last 7.17 release, is affected by 1 known security advisory (1 critical), including CVE-2023-45133. Upgrade to 7.23.2 or later to fix all of them.

Upgrade with:npm install @babel/traverse@7.23.2

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting @babel/traverse 7.17.12

  • CriticalCVE-2023-45133GHSA-67hx-6x53-jw9216 Oct 2023

    Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code

    Affected
    <7.23.2 · >=8.0.0-alpha.0 <8.0.0-alpha.4
    Fixed in
    7.23.2, 8.0.0-alpha.4

Which of your client projects are still on @babel/traverse 7.17?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact @babel/traverse version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other @babel/traverse versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.