node-opcua-alarm-condition (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 2.137.0 or later to clear it. No malicious-package signal is recorded.
16 direct dependencies
none carry a known advisory
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 41st percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-gvwq-6fmx-28xm, the advisory selected below
A prototype pollution in the function fieldsToJson of node-opcua-alarm-condition v2.134.0 allows attackers to cause a Denial of Service (DoS) via supplying a…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for node-opcua-alarm-condition (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for node-opcua-alarm-condition (npm), the worst rated HIGH. They are GHSA-gvwq-6fmx-28xm.
2.137.0 or later clears every advisory recorded for node-opcua-alarm-condition (npm). Check the release you pick before installing it.
Search node-opcua-alarm-condition in CyberXYZ Check at https://cyberxyz.io/check?q=node-opcua-alarm-condition. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 14:58 UTC. The most recent advisory here was published 2025-02-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.