VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-opcua: vulnerability history, versions and safety

node-opcua is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Aug 2022 to Aug 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 H5
i
1 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 20 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-opcua vulnerabilities

Vulert verdict on node-opcua 2.187.12 i

Updated on 23 Oct 2026

Careful: 2.187.12 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.187.12 — affected i
  • Vulnerabilities on record 5 over 3 years · 2 in the last year i
  • Latest disclosure 20 Aug 2026 i
  • Highest CVSS 7.7 i
  • With no published fix 1 i
  • Depended on by 95 packages i
  • Stars 1,666 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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 node-opcua, 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
2.187.12 21 Oct 2026 H1 MIT No Details →
2.187.11 21 Oct 2026 H1 MIT No Details →
2.187.10 19 Oct 2026 H1 MIT No Details →
2.187.9 15 Oct 2026 H1 MIT No Details →
2.187.8 14 Oct 2026 H1 MIT No Details →
2.187.7 13 Oct 2026 H1 MIT No Details →
2.187.6 13 Oct 2026 H1 MIT No Details →
2.187.5 12 Oct 2026 H1 MIT No Details →
2.187.4 12 Oct 2026 H1 MIT No Details →
2.187.3 09 Oct 2026 H1 MIT No Details →
2.187.2 09 Oct 2026 H1 MIT No Details →
2.187.1 09 Oct 2026 H1 MIT No Details →
2.187.0 08 Oct 2026 H1 MIT No Details →
2.186.17 05 Oct 2026 H1 MIT No Details →
2.186.15 01 Oct 2026 H1 MIT No Details →
2.186.14 01 Oct 2026 H1 MIT No Details →
2.186.13 30 Sep 2026 H1 MIT No Details →
2.186.12 30 Sep 2026 H1 MIT No Details →
2.186.10 29 Sep 2026 H1 MIT No Details →
2.186.9 29 Sep 2026 H1 MIT No Details →
2.186.8 28 Sep 2026 H1 MIT No Details →
2.186.7 28 Sep 2026 H1 MIT No Details →
2.186.4 25 Sep 2026 H1 MIT No Details →
2.186.3 25 Sep 2026 H1 MIT No Details →
2.186.2 24 Sep 2026 H1 MIT No Details →
2.186.1 21 Sep 2026 H1 MIT No Details →
2.186.0 20 Sep 2026 H1 MIT No Details →
2.185.0 19 Sep 2026 H1 MIT No Details →
2.184.8 17 Sep 2026 H1 MIT No Details →
2.184.7 17 Sep 2026 H1 MIT No Details →
2.184.6 17 Sep 2026 H1 MIT No Details →
2.184.5 16 Sep 2026 H1 MIT No Details →
2.184.4 15 Sep 2026 H1 MIT No Details →
2.184.3 15 Sep 2026 H1 MIT No Details →
2.184.2 14 Sep 2026 H1 MIT No Details →
2.184.1 14 Sep 2026 H1 MIT No Details →
2.184.0 14 Sep 2026 H1 MIT No Details →
2.183.1 11 Sep 2026 H1 MIT No Details →
2.183.0 10 Sep 2026 H1 MIT No Details →
2.182.2 09 Sep 2026 H1 MIT No Details →
2.182.0 08 Sep 2026 H1 MIT No Details →
2.181.1 05 Sep 2026 H1 MIT No Details →
2.181.0 05 Sep 2026 H1 MIT No Details →
2.180.0 03 Sep 2026 H1 MIT No Details →
2.179.0 27 Aug 2026 H1 MIT No Details →
2.178.0 20 Aug 2026 H1 MIT No Details →
2.177.0 16 Aug 2026 H1 MIT No Details →
2.176.0 09 Aug 2026 H1 MIT No Details →
2.175.6 30 Jul 2026 H1 MIT No Details →
2.175.3 29 Jul 2026 H1 MIT No Details →
2.175.2 15 Jul 2026 H1 MIT No Details →
2.175.1 13 Jul 2026 H1 MIT No Details →
2.175.0 08 Jul 2026 H1 MIT No Details →
2.174.0 30 Jun 2026 H1 MIT No Details →
2.173.1 19 May 2026 H1 MIT No Details →
2.173.0 19 May 2026 H1 MIT No Details →
2.172.0 14 May 2026 H1 MIT No Details →
2.170.1 03 May 2026 H1 MIT No Details →
2.169.0 13 Apr 2026 H1 MIT No Details →
2.168.0 04 Apr 2026 H1 MIT No Details →
2.167.0 30 Mar 2026 H2 MIT No Details →
2.166.0 25 Mar 2026 H2 MIT No Details →
2.165.2 24 Mar 2026 H2 MIT No Details →
2.165.1 20 Mar 2026 H2 MIT No Details →
2.165.0 18 Mar 2026 H2 MIT No Details →
2.164.2 09 Mar 2026 H2 MIT No Details →
2.163.1 09 Feb 2026 H2 MIT No Details →
2.163.0 07 Feb 2026 H2 MIT No Details →
2.162.0 03 Feb 2026 H2 MIT No Details →
2.161.0 19 Jan 2026 H2 MIT No Details →
2.160.0 10 Jan 2026 H2 MIT No Details →
2.159.0 16 Dec 2025 H2 MIT No Details →
2.158.0 10 Nov 2025 H2 MIT No Details →
2.157.0 26 Sep 2025 H2 MIT No Details →
2.156.0 08 Jun 2025 H2 MIT No Details →
2.155.0 06 Jun 2025 H2 MIT No Details →
2.154.0 04 Jun 2025 H2 MIT No Details →
2.153.0 03 May 2025 H2 MIT No Details →
2.152.0 09 Apr 2025 H2 MIT No Details →
2.151.0 06 Apr 2025 H2 MIT No Details →
2.150.0 18 Mar 2025 H2 MIT No Details →
2.149.0 23 Feb 2025 H2 MIT No Details →
2.148.0 13 Feb 2025 H2 MIT No Details →
2.147.0 13 Feb 2025 H2 MIT No Details →
2.146.0 13 Feb 2025 H2 MIT No Details →
2.145.0 13 Feb 2025 H2 MIT No Details →
2.144.0 07 Feb 2025 H2 MIT No Details →
2.143.0 30 Jan 2025 H2 MIT No Details →
2.142.0 30 Jan 2025 H2 MIT No Details →
2.141.0 27 Jan 2025 H2 MIT No Details →
2.140.0 03 Jan 2025 H2 MIT No Details →
2.139.0 15 Dec 2024 H2 MIT No Details →
2.138.1 22 Nov 2024 H2 MIT No Details →
2.138.0 22 Nov 2024 H2 MIT No Details →
2.137.0 20 Nov 2024 H2 MIT No Details →
2.136.0 11 Nov 2024 H2 MIT No Details →
2.135.0 11 Nov 2024 H2 MIT No Details →
2.134.0 10 Nov 2024 H2 MIT No Details →
2.133.0 25 Sep 2024 H2 MIT No Details →
2.132.0 13 Sep 2024 H2 MIT No Details →
2.131.0 13 Sep 2024 H2 — No Details →
2.130.0 30 Jul 2024 H2 — No Details →
2.129.0 17 Jul 2024 H2 — No Details →
2.128.0 02 Jul 2024 H2 — No Details →
2.127.1 27 Jun 2024 H2 — No Details →
2.127.0 27 Jun 2024 H2 — No Details →
2.126.0 18 Jun 2024 H2 — No Details →
2.125.0 05 Jun 2024 H2 — No Details →
2.124.0 08 Apr 2024 H2 — No Details →
2.123.0 10 Mar 2024 H2 — No Details →
2.122.0 28 Feb 2024 H2 — No Details →
2.121.0 25 Feb 2024 H2 — No Details →
2.120.0 21 Jan 2024 H2 — No Details →
2.119.2 25 Dec 2023 H2 — No Details →
2.119.1 25 Dec 2023 H2 — No Details →
2.119.0 23 Dec 2023 H2 — No Details →
2.113.2 23 Dec 2023 H2 — No Details →
2.113.1 22 Dec 2023 H2 — No Details →
2.118.0 20 Nov 2023 H2 — No Details →
2.117.0 13 Nov 2023 H2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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-opcua

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54155: node-opcua Vulnerability Due to Missing Nonce Verification in UserNameIdentityToken Authentication 7.7 high No fix published 20 Aug 2026
CVE-2022-21208: Uncontrolled Resource Consumption in node-opcua 7.5 high 2.74.0 24 Aug 2022
CVE-2022-25231: Denial of Service (DoS) vulnerability in node-opcua 7.5 high 2.74.0 24 Aug 2022
CVE-2022-24375: Denial of Service (DoS) in node-opcua 7.5 high 2.74.0 25 Aug 2022
CVE-2026-54156: node-opcua Unbounded Nonce Cache Leads to Heap Exhaustion DoS 7.5 high 2.168.0 20 Aug 2026

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-opcua

Is node-opcua safe to use?

Vulert records 5 vulnerabilities for node-opcua in npm: 0 critical, 5 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is node-opcua's Vulert package health score?

Vulert scores node-opcua 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of node-opcua affected?

Yes. 2.187.12, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does node-opcua have?

5 vulnerabilities are recorded for node-opcua in the npm ecosystem: 0 critical, 5 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 node-opcua vulnerabilities disclosed?

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

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