CVE-2023-45133

CRITICALNVD 8.89.3
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2023-10-16. NVD baseline CVSS 8.8; sources differ by 0.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-2669 (ENISA EUVD) · GHSA-67hx-6x53-jw92 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Babel is a compiler for writingJavaScript. In @babel/traverse prior to versions 7.23.2 and 8.0.0-alpha.4 and all versions of babel-traverse, using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the path.evaluate()or path.evaluateTruthy() internal Babel methods. Known affected plugins are @babel/plugin-transform-runtime; @babel/preset-env when using its useBuiltIns option; and any "polyfill provider" plugin that depends on @babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regenerator. No other plugins under the @babel/ namespace are impacted, but third-party plugins might be. Users that only compile trusted code are not impacted. The vulnerability has been fixed in @babel/[email protected] and @babel/[email protected]. Those who cannot upgrade @babel/traverse and are using one of the affected packages mentioned above should upgrade them to their latest version to avoid triggering the vulnerable code path in affected @babel/traverse versions: @babel/plugin-transform-runtime v7.23.2, @babel/preset-env v7.23.2, @babel/helper-define-polyfill-provider v0.4.3, babel-plugin-polyfill-corejs2 v0.4.6, babel-plugin-polyfill-corejs3 v0.8.5, babel-plugin-polyfill-es-shims v0.10.0, babel-plugin-polyfill-regenerator v0.5.3.

CVSS v3
8.8
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 12, 2023

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 30, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
GitHub release Patch Available

Release v7.23.2 (babel/babel)

Patch available: babel/babel v7.23.2

https://github.com/babel/babel/releases/tag/v7.23.2
GitHub pull request Patch Available

Only evaluate own String/Number/Math methods

Patch available: babel/babel v8.0.0-beta.1 (PR #16033 merged 2023-10-11)

https://github.com/babel/babel/pull/16033
GitHub commit Patch Available

commit b13376b34694 (babel/babel)

Patch available: babel/babel v8.0.0-beta.1 (contains commit b13376b34694)

https://github.com/babel/babel/commit/b13376b346946e3f62fc0848c1d2a23223314c82
Web page

[SECURITY] [DSA 5528-1] node-babel7 security update

https://www.debian.org/security/2023/dsa-5528
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3618-1] node-babel security update

https://lists.debian.org/debian-lts-announce/2023/10/msg00026.html
GitHub advisoryMentions a patch (unverified)

Arbitrary code execution when compiling specifically crafted malicious code · Advisory · babel/babel · GitHub

https://github.com/babel/babel/security/advisories/GHSA-67hx-6x53-jw92
GitHub release Patch Available

v8.0.0-alpha.4

Patch available: babel/babel v8.0.0-alpha.4 (pre-release)

https://github.com/babel/babel/releases/tag/v8.0.0-alpha.4

Vendor Advisories for CVE-2023-45133(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunode-babel-types (6.26.0+dfsg-3ubuntu0.1~esm1) @ bionic2026-11-12ubuntu
npm@babel/traverse @ 7.23.2 (fixes < 7.23.2)—ghsa
npm@babel/traverse @ 8.0.0-alpha.4 (fixes >= 8.0.0-alpha.0, < 8.0.0-alpha.4)—ghsa
npmbabel-traverse—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 6 ecosystems)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@babel/traverse—
  • every version up to 7.23.2: fixed in 7.23.2
  • 8.0.0-alpha.0 up to 8.0.0-alpha.4: fixed in 8.0.0-alpha.4
—
babel-traverse—
  • every version on: no fix on record
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
node-babel6.26.0+dfsg-3
  • every version up to 6.26.0+dfsg-3+deb10u1: fixed in 6.26.0+dfsg-3+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-babel77.12.12+~cs150.141.84-6
  • every version up to 7.12.12+~cs150.141.84-6+deb11u1: fixed in 7.12.12+~cs150.141.84-6+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-babel77.20.15+ds1+~cs214.269.168-3
  • every version up to 7.20.15+ds1+~cs214.269.168-3+deb12u1: fixed in 7.20.15+ds1+~cs214.269.168-3+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-babel7—
  • every version up to 7.20.15+ds1+~cs214.269.168-5: fixed in 7.20.15+ds1+~cs214.269.168-5
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-babel7—
  • every version up to 7.20.15+ds1+~cs214.269.168-5: fixed in 7.20.15+ds1+~cs214.269.168-5
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 16× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 266 rows on record for this CVE, as 95 entries (5 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 166 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 05:09 UTCEchelonGraph re-scored
  2. 2026-11-13 05:09 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  3. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-12 05:25 UTCEchelonGraph re-scored
  5. 2026-11-12 05:25 UTCVendor advisory
  6. 2026-11-12 05:25 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  7. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-11 05:41 UTCEchelonGraph re-scored
  9. 2026-11-11 05:41 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  10. 2026-11-10 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-11-10 05:56 UTCEchelonGraph re-scored
  12. 2026-11-10 05:56 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  13. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-09 06:12 UTCEchelonGraph re-scored
  15. 2026-11-09 06:12 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  16. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-08 06:28 UTCEchelonGraph re-scored
  18. 2026-11-08 06:28 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  19. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-11-07 06:43 UTCEchelonGraph re-scored
  21. 2026-11-07 06:43 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  22. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-11-06 06:59 UTCEchelonGraph re-scored
  24. 2026-11-06 06:59 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  25. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 70 more
  1. 2026-11-05 07:15 UTCEchelonGraph re-scored
  2. 2026-11-05 07:15 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  3. 2026-11-04 16:55 UTCOSV refresh
  4. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-04 07:31 UTCEchelonGraph re-scored
  6. 2026-11-04 07:31 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  7. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-03 07:47 UTCEchelonGraph re-scored
  9. 2026-11-03 07:47 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  10. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-11-02 08:02 UTCEchelonGraph re-scored
  12. 2026-11-02 08:02 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  13. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-01 08:18 UTCGHSA enrichmentGHSA-67hx-6x53-jw92 · GitHub severity CRITICAL · GitHub CVSS 9.3
  15. 2026-11-01 08:18 UTCEchelonGraph re-scored▲ 0.50
  16. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-27 20:25 UTCEchelonGraph re-scored
  21. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-25 17:33 UTCEchelonGraph re-scored
  24. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-10-20 22:59 UTCEchelonGraph re-scored
  30. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-10-18 07:49 UTCEchelonGraph re-scored
  34. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  39. 2026-10-12 16:39 UTCEchelonGraph re-scored
  40. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-10-11 21:44 UTCEchelonGraph re-scored
  42. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  47. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  51. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  52. 2026-09-30 16:31 UTCEchelonGraph re-scored
  53. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  54. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  56. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  58. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  59. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  60. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  61. 2026-09-22 19:09 UTCOSV refresh
  62. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  63. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  64. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  65. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  66. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  68. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  69. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  70. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:node-babel7

Frequently asked(5)

What is CVE-2023-45133?
CVE-2023-45133 is a critical-severity vulnerability; its CVE record was published on October 12, 2023. Babel is a compiler for writingJavaScript. In @babel/traverse prior to versions 7.23.2 and 8.0.0-alpha.4 and all versions of babel-traverse, using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely…
When was the CVE record for CVE-2023-45133 published?
The CVE record for CVE-2023-45133 was published on October 12, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-45133 actively exploited?
CVE-2023-45133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-45133?
CVE-2023-45133 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.3 (CRITICAL).
How do I remediate CVE-2023-45133?
A fix for CVE-2023-45133 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-45133 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-45133

Explore →

Is Your Infrastructure Affected by CVE-2023-45133?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs