VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@ethereumjs/tx: vulnerability history, versions and safety

@ethereumjs/tx is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 @ethereumjs/tx vulnerabilities

Vulert verdict on @ethereumjs/tx 10.1.3 i

Updated on 23 Oct 2026

Good news: 10.1.3, the version you would install today, has no known vulnerabilities.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 10.1.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 638 packages i
  • Stars 2,758 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence MPL-2.0 i

Version list, release dates, licence and dependants published by the npm registry, 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 @ethereumjs/tx, 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
10.1.3 21 Aug 2026 none MPL-2.0 — Details →
10.1.2 29 May 2026 none MPL-2.0 — Details →
10.1.1 28 Jan 2026 none MPL-2.0 — Details →
10.1.1-nightly.2 19 Jan 2026 none MPL-2.0 — Details →
10.1.1-nightly.1 04 Dec 2025 none MPL-2.0 — Details →
10.1.0 06 Nov 2025 none MPL-2.0 — Details →
10.0.0 29 Apr 2025 none MPL-2.0 — Details →
10.0.0-rc.1 24 Mar 2025 none MPL-2.0 — Details →
6.0.0-alpha.1 17 Oct 2024 none MPL-2.0 — Details →
5.4.0 15 Aug 2024 none MPL-2.0 — Details →
5.3.0 18 Mar 2024 none MPL-2.0 — Details →
5.2.1 08 Feb 2024 none MPL-2.0 — Details →
5.2.0 08 Feb 2024 none MPL-2.0 — Details →
5.1.0 02 Nov 2023 none MPL-2.0 — Details →
5.0.0 09 Aug 2023 none MPL-2.0 — Details →
5.0.0-rc.1 17 Jul 2023 none MPL-2.0 — Details →
4.2.0 20 Jun 2023 none MPL-2.0 — Details →
4.1.2 24 Apr 2023 none MPL-2.0 — Details →
4.1.1 27 Feb 2023 none MPL-2.0 — Details →
4.1.0 24 Feb 2023 none MPL-2.0 — Details →
4.0.2 15 Dec 2022 none MPL-2.0 — Details →
4.0.1 19 Oct 2022 none MPL-2.0 — Details →
4.0.0 06 Sep 2022 none MPL-2.0 — Details →
4.0.0-rc.1 26 Aug 2022 none MPL-2.0 — Details →
4.0.0-beta.3 11 Aug 2022 none MPL-2.0 — Details →
4.0.0-beta.2 17 Jul 2022 none MPL-2.0 — Details →
4.0.0-beta.1 30 Jun 2022 none MPL-2.0 — Details →
3.5.2 03 Jun 2022 none MPL-2.0 — Details →
3.5.1 23 Mar 2022 none MPL-2.0 — Details →
3.5.0 01 Feb 2022 none MPL-2.0 — Details →
3.4.0 09 Nov 2021 none MPL-2.0 — Details →
3.3.2 29 Sep 2021 none MPL-2.0 — Details →
3.3.1 27 Sep 2021 none MPL-2.0 — Details →
3.3.0 08 Jul 2021 none MPL-2.0 — Details →
3.2.1 11 Jun 2021 none MPL-2.0 — Details →
3.2.0 27 May 2021 none MPL-2.0 — Details →
3.1.4 23 Apr 2021 none MPL-2.0 — Details →
3.1.3 10 Apr 2021 none MPL-2.0 — Details →
3.1.2 01 Apr 2021 none MPL-2.0 — Details →
3.1.1 23 Mar 2021 none MPL-2.0 — Details →
3.1.0 23 Mar 2021 none MPL-2.0 — Details →
3.0.2 16 Feb 2021 none MPL-2.0 — Details →
3.0.1 20 Jan 2021 none MPL-2.0 — Details →
3.0.0 25 Nov 2020 none MPL-2.0 — Details →
3.0.0-rc.1 19 Nov 2020 none MPL-2.0 — Details →
3.0.0-beta.2 12 Nov 2020 none MPL-2.0 — Details →
3.0.0-beta.1 22 Oct 2020 none MPL-2.0 — Details →

All 47 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @ethereumjs/tx

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 @ethereumjs/tx

Is @ethereumjs/tx safe to use?

Vulert has no vulnerabilities on record for @ethereumjs/tx in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @ethereumjs/tx's Vulert package health score?

Vulert scores @ethereumjs/tx 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 @ethereumjs/tx affected?

No. 10.1.3, 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 @ethereumjs/tx should I use?

10.1.3 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 @ethereumjs/tx have?

0 vulnerabilities are recorded for @ethereumjs/tx in the npm ecosystem: 0 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 @ethereumjs/tx vulnerabilities disclosed?

0 vulnerabilities were recorded for @ethereumjs/tx in the last 12 months. 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 @ethereumjs/tx 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 @ethereumjs/tx for upcoming vulnerabilities?

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