log4js (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 6.4.0 or later to clear it. No malicious-package signal is recorded.
0 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, 24th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-82v2-mx6x-wq7q, the advisory selected below
Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix).
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for log4js (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for log4js (npm), the worst rated MODERATE. They are GHSA-82v2-mx6x-wq7q.
6.4.0 or later clears every advisory recorded for log4js (npm). Check the release you pick before installing it.
Search log4js in CyberXYZ Check at https://cyberxyz.io/check?q=log4js. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:03 UTC. The most recent advisory here was published 2022-01-21. Updated continuously from NVD, GHSA, OSV and CNA feeds.