log4net (nuget) has 3 known vulnerabilities, the worst rated CRITICAL. Upgrade to 3.3.0 or later to clear all of them. No malicious-package signal is recorded.
1 direct dependencies
none carry a known advisory
27 packages depend on it
an advisory here reaches each of them
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so nuget packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 97th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-2cwj-8chv-9pp9, the advisory selected below
Apache log4net before 2.0.10 does not disable XML external entities when parsing log4net configuration files.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for log4net (nuget), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 3 known vulnerabilities for log4net (nuget), the worst rated CRITICAL. They are GHSA-2cwj-8chv-9pp9, GHSA-4f7c-pmjv-c25w, GHSA-f9fr-w54q-772h.
3.3.0 or later clears every advisory recorded for log4net (nuget). Check the release you pick before installing it.
Search log4net in CyberXYZ Check at https://cyberxyz.io/check?q=log4net. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:17 UTC. The most recent advisory here was published 2026-04-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.