Vulnerability Database · Debian · Package report

node-babel7: vulnerability history, versions and safety

node-babel7 is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 74 releases, from Oct 2023 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 22 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on node-babel7 i

Updated on 23 Oct 2026

Careful: 2 of the 5 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 5 vulnerabilities on record across 2 years, 2 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 2 years · 2 in the last year i
  • Latest disclosure 22 Jun 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i

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 holds for node-babel7, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
7.20.15+ds1+~cs214.269.168-17 U2 No Details →
7.20.15+ds1+~cs214.269.168-16 U2 No Details →
7.20.15+ds1+~cs214.269.168-15 U2 No Details →
7.20.15+ds1+~cs214.269.168-14 U2 No Details →
7.20.15+ds1+~cs214.269.168-13 U2 No Details →
7.20.15+ds1+~cs214.269.168-12 U2 No Details →
7.20.15+ds1+~cs214.269.168-11 U2 No Details →
7.20.15+ds1+~cs214.269.168-10 U2 No Details →
7.20.15+ds1+~cs214.269.168-9 U2 No Details →
7.20.15+ds1+~cs214.269.168-8 U2 No Details →
7.20.15+ds1+~cs214.269.168-7 U2 No Details →
7.20.15+ds1+~cs214.269.168-6 U2 No Details →
7.20.15+ds1+~cs214.269.168-5 U2 No Details →
7.20.15+ds1+~cs214.269.168-4 U2 No Details →
7.20.15+ds1+~cs214.269.168-3 U2 No Details →
7.20.15+ds1+~cs214.269.168-2 U2 No Details →
7.20.15+ds1+~cs214.269.168-1 U2 No Details →
7.20.14+ds1+~cs214.269.168-1 U2 No Details →
7.20.12+ds1+~cs214.250.188-1 U2 No Details →
7.20.11+ds1+~cs214.250.188-1 U2 No Details →
7.20.6+ds1+~cs214.250.188-1 U2 No Details →
7.20.4+ds1+~cs214.250.187-1 U2 No Details →
7.20.1+ds1+~cs214.250.186-2 U2 No Details →
7.20.1+ds1+~cs214.250.186-1 U2 No Details →
7.20.0+ds1+~cs214.250.186-1 U2 No Details →
7.19.6+ds1+~cs214.250.186-1 U2 No Details →
7.19.5+ds1+~cs214.250.186-1 U2 No Details →
7.19.3+ds1+~cs214.250.186-3 U2 No Details →
7.19.3+ds1+~cs214.250.186-2 U2 No Details →
7.19.3+ds1+~cs214.250.186-1 U2 No Details →
7.19.2+~cs214.250.185-2 U2 No Details →
7.19.2+~cs214.250.185-1 U2 No Details →
7.19.2+ds1+~cs214.250.186-2 U2 No Details →
7.19.2+ds1+~cs214.250.186-1 U2 No Details →
7.19.0+~cs214.250.185-1 U2 No Details →
7.18.13+~cs214.250.184-3 U2 No Details →
7.18.13+~cs214.250.184-2 U2 No Details →
7.18.13+~cs214.250.184-1 U2 No Details →
7.18.12+~cs214.250.184-1 U2 No Details →
7.18.9+~cs214.249.185-1 U2 No Details →
7.18.8+~cs214.249.185-1 U2 No Details →
7.18.7+~cs214.249.185-1 U2 No Details →
7.18.6+~cs214.249.185-1 U2 No Details →
7.18.5+~cs214.249.185-1 U2 No Details →
7.18.4+~cs214.249.185-2 U2 No Details →
7.18.4+~cs214.249.185-1 U2 No Details →
7.17.11+~cs214.263.190-2 U2 No Details →
7.17.11+~cs214.263.190-1 U2 No Details →
7.17.9+~cs214.260.191-2 U2 No Details →
7.17.9+~cs214.260.191-1 U2 No Details →
7.17.8+~cs214.260.191-2 U2 No Details →
7.17.8+~cs214.260.191-1 U2 No Details →
7.17.7+~cs214.260.190-1 U2 No Details →
7.17.6+~cs214.260.190-1 U2 No Details →
7.17.5+~cs214.260.190-1 U2 No Details →
7.17.4+~cs214.260.190-2 U2 No Details →
7.17.4+~cs214.260.190-1 U2 No Details →
7.17.2+~cs214.260.190-1 U2 No Details →
7.16.12+~cs214.260.189-2 U2 No Details →
7.16.12+~cs214.260.189-1 U2 No Details →
7.16.10+~cs214.260.188-1 U2 No Details →
7.16.9+~cs214.260.184-1 U2 No Details →
7.16.7+~cs214.260.184-1 U2 No Details →
7.16.6+~cs215.259.185-2 U2 No Details →
7.16.6+~cs215.259.185-1 U2 No Details →
7.16.6+ds1+~cs214.259.181-5 U2 No Details →
7.16.6+ds1+~cs214.259.181-4 U2 No Details →
7.16.6+ds1+~cs214.259.181-3 U2 No Details →
7.16.6+ds1+~cs214.259.181-2 U2 No Details →
7.16.6+ds1+~cs214.259.181-1 U2 No Details →
7.12.12+~cs150.141.84-8 U2 No Details →
7.12.12+~cs150.141.84-7 U2 No Details →
7.12.12+~cs150.141.84-6 U5 No Details →
7.12.12+~cs150.141.84-6+deb11u1 U2 No Details →

Newest 74 of 74 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for node-babel7

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Code Execution Vulnerability in Babel's @babel/traverse Package 8.8 high 7.12.12+~cs150.141.84-6+deb11u1 12 Oct 2023
Critical Vulnerability in node-babel7: Arbitrary Code Execution Risk 7.8 high No fix published 26 May 2026
Arbitrary File Read Vulnerability in node-babel7 Package 3.2 low No fix published 22 Jun 2026
Security Update for node-babel7 N/A unrated 7.12.12+~cs150.141.84-6+deb11u1 16 Oct 2023
Critical Vulnerability in node-babel7: Arbitrary Code Execution Risk N/A unrated 7.12.12+~cs150.141.84-6+deb11u1 12 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: 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 node-babel7

Is node-babel7 safe to use?

Vulert records 5 vulnerabilities for node-babel7 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-babel7 have?

5 vulnerabilities are recorded for node-babel7 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 5 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 node-babel7 vulnerabilities disclosed?

2 vulnerabilities were recorded for node-babel7 in the last 12 months, and the oldest entry in this database dates to 12 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 node-babel7 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 node-babel7 for upcoming vulnerabilities?

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