Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54156 high CVSS 7.5

Vulnerability in node-opcua (CVE-2026-54156)

Summary

Vulnerability in node-opcua (CVE-2026-54156). Risk of unauthorized operations or information disclosure. Exploitable via g_alreadyUsedNonce. Mitigation: upgrade to 2.166.0 or later.

Original description

The description as published by the source.

Summary
A process-global nonce cache with no eviction policy allows an unauthenticated remote attacker to exhaust server heap memory by repeatedly opening sessions, causing the node-opcua server process to crash.

Affected versions: <= 2.165.0
Tested version: 2.165.0
CVSS Score: 7.5 (High)
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE: CWE-770 Allocation of Resources Without Limits or Throttling

Root Cause

In packages/node-opcua-secure-channel/source/server/server_secure_channel_layer.ts at line 156, g_alreadyUsedNonce is a process-global object used to track previously seen nonces for replay detection. Entries are added on every OpenSecureChannelRequest and every CreateSession request but are never removed or expired.

An unauthenticated attacker can exploit the CreateSession path (which requires no certificate) to accumulate nonce entries indefinitely. Even with maxSessions=10 limiting concurrent sessions, nonces persist after session expiry, allowing slow but reliable heap exhaustion across repeated connection cycles.

Measured Impact

Dynamically confirmed heap growth:

  • 5,000 unique nonces → +1.23 MB resident heap, no eviction after explicit GC
  • Projected: 10^6 nonces → ~246 MB resident heap
  • Achievable OOM on default Node.js heap limits

Suggested Fix

Add a TTL-based eviction policy to g_alreadyUsedNonce. Nonces should be expired after the maximum session timeout (or a reasonable fixed…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54156 has been found in node-opcua.
Attackers can target a specific entry point like g_alreadyUsedNonce over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade node-opcua to 2.166.0 or later.
If unsure, ask your IT team or search "node-opcua CVE-2026-54156" on the vendor's site.

CVE-2026-54156 (node-opcua) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: g_alreadyUsedNonce / OpenSecureChannelRequest / CreateSession
Patched: 2.166.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-770) exists in node-opcua. Attackers reach the vulnerable code path via g_alreadyUsedNonce without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of node-opcua. Attack surface: g_alreadyUsedNonce / OpenSecureChannelRequest / CreateSession.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.166.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-opcua' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'node-opcua' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で node-opcua を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade node-opcua to 2.166.0

    ステージング環境で 2.166.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm node-opcua
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.166.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details