mercurius (npm) has 4 known vulnerabilities, the worst rated HIGH. Upgrade to 16.8.0 or later to clear all of them. No malicious-package signal is recorded.
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, 76th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-273r-rm8g-7f3x, the advisory selected below
Any users from Mercurius@8.10.0 to 8.11.1 are subjected to a denial of service attack by sending a malformed JSON to /graphql unless they are using a custom…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for mercurius (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 4 known vulnerabilities for mercurius (npm), the worst rated HIGH. They are GHSA-273r-rm8g-7f3x, GHSA-v66j-6wwf-jc57, GHSA-cm8h-q92v-xcfc, GHSA-m4h2-mjfm-mp55.
16.8.0 or later clears every advisory recorded for mercurius (npm). Check the release you pick before installing it.
Search mercurius in CyberXYZ Check at https://cyberxyz.io/check?q=mercurius. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:38 UTC. The most recent advisory here was published 2026-03-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.