VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

librenms/librenms: vulnerability history, versions and safety

librenms/librenms is a package in the Packagist ecosystem. Vulert records 111 vulnerabilities for it across 120 releases, from Oct 2019 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
111 vulnerabilities recorded C6 H41 M58 L6
i
8 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
22 in the last 12 months

Most recent disclosure 26 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all librenms/librenms vulnerabilities

Vulert verdict on librenms/librenms i

Updated on 23 Oct 2026

Careful: 8 of the 111 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 111 vulnerabilities on record across 6 years, 22 in the last year.

What to do: Plan around the 8 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 111 over 6 years · 22 in the last year i
  • Latest disclosure 26 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 8 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for librenms/librenms, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
20160828 H1 No Details →
201609.01 H1 No Details →
201609 H1 No Details →
26.6.1 H1 M1 Yes Details →
26.6.0 H1 M1 Yes Details →
26.5.1 H1 M1 Yes Details →
26.5.0 H1 M1 Yes Details →
26.4.1 H3 M3 Yes Details →
26.4.0 H3 M3 Yes Details →
26.3.1 H3 M3 Yes Details →
26.3.0 H3 M3 Yes Details →
26.2.0 H5 M4 L1 Yes Details →
26.1.1 H7 M9 L1 Yes Details →
26.1.0 H7 M9 L1 Yes Details →
25.12.0 H7 M9 L1 Yes Details →
25.11.0 H7 M10 Yes Details →
25.10.0 H7 M12 L1 No Details →
25.9.1 H7 M13 L2 No Details →
25.9.0 H7 M13 L2 No Details →
25.8.0 H7 M13 L2 No Details →
25.7.0 H7 M14 L2 No Details →
25.6.0 H8 M15 L2 No Details →
25.5.0 H8 M15 L2 No Details →
25.4.0 H8 M15 L3 No Details →
25.3.0 H8 M15 L3 No Details →
25.2.0 H8 M15 L3 No Details →
25.1.0 H8 M15 L3 No Details →
24.12.0 H8 M15 L3 No Details →
24.11.10 M1 Yes Details →
24.11.0 H8 M15 L3 No Details →
24.10.1 H8 M20 L3 No Details →
24.10.0 H8 M20 L3 No Details →
24.9.1 C1 H20 M20 L3 No Details →
24.9.0 C1 H20 M20 L3 No Details →
24.8.1 C1 H21 M21 L5 No Details →
24.8.0 C1 H21 M21 L5 No Details →
24.7.0 C1 H21 M21 L5 No Details →
24.6.0 C1 H21 M21 L5 No Details →
24.5.0 C1 H21 M21 L5 No Details →
24.4.1 C1 H21 M21 L5 No Details →
24.4.0 C1 H21 M21 L5 No Details →
24.3.0 C1 H24 M21 L5 No Details →
24.2.0 C1 H24 M21 L5 No Details →
24.1.0 C1 H24 M22 L5 No Details →
23.11.0 C1 H24 M22 L5 No Details →
23.10.0 C1 H24 M25 L5 No Details →
23.9.1 C1 H25 M25 L5 No Details →
23.9.0 C1 H26 M25 L5 No Details →
23.8.2 C1 H26 M30 L5 No Details →
23.8.1 C1 H26 M30 L5 No Details →
23.8.0 C1 H26 M30 L5 No Details →
23.7.0 C1 H27 M30 L5 No Details →
23.6.0 C1 H27 M30 L5 No Details →
23.5.0 C1 H27 M30 L5 No Details →
23.4.1 C1 H27 M30 L5 No Details →
23.4.0 C1 H28 M30 L5 No Details →
23.2.0 C1 H28 M30 L5 No Details →
23.1.1 C1 H28 M30 L5 No Details →
23.1.0 C1 H28 M30 L5 No Details →
22.12.0 C1 H28 M30 L5 No Details →
22.11.0 C1 H28 M30 L5 No Details →
22.10.0 C1 H28 M30 L5 No Details →
22.9.0 C3 H30 M36 L5 No Details →
22.8.0 C3 H30 M37 L5 No Details →
22.7.0 C3 H30 M37 L5 No Details →
22.6.0 C3 H30 M39 L5 No Details →
22.5.0 C3 H30 M39 L5 No Details →
22.4.1 C3 H30 M39 L5 No Details →
22.4.0 C3 H30 M39 L5 No Details →
22.3.0 C3 H31 M40 L5 No Details →
22.2.2 C3 H31 M40 L5 No Details →
22.2.1 C3 H31 M41 L5 No Details →
22.2.0 C3 H31 M41 L5 No Details →
22.1.0 C3 H33 M43 L5 No Details →
21.12.1 C3 H33 M45 L5 No Details →
21.12.0 C3 H33 M45 L5 No Details →
21.11.0 C4 H33 M47 L5 No Details →
21.10.2 C4 H33 M48 L5 No Details →
21.10.1 C4 H33 M48 L5 No Details →
21.10.0 C4 H33 M48 L5 No Details →
21.9.1 C4 H33 M48 L5 No Details →
21.9.0 C4 H33 M48 L5 No Details →
21.8.0 C4 H33 M48 L5 No Details →
21.7.0 C4 H33 M48 L5 No Details →
21.6.0 C4 H33 M48 L5 No Details →
21.5.1 C4 H32 M48 L5 No Details →
21.5.0 C4 H32 M48 L5 No Details →
21.4.0 C4 H32 M48 L5 No Details →
21.3.0 C4 H32 M48 L5 No Details →
21.2.0 C4 H32 M49 L5 No Details →
21.1.0 C4 H32 M49 L5 No Details →
1.70.1 C4 H33 M49 L5 No Details →
1.70.0 C4 H33 M49 L5 No Details →
1.69 C4 H33 M49 L5 No Details →
1.68 C4 H33 M49 L5 No Details →
1.67 C4 H33 M49 L5 No Details →
1.66 C4 H33 M49 L5 No Details →
1.65.1 C4 H33 M49 L5 No Details →
1.65 C4 H34 M50 L5 No Details →
1.64.1 C4 H35 M50 L5 No Details →
1.64 C4 H35 M50 L5 No Details →
1.63 C4 H35 M50 L5 No Details →
1.62.2 C4 H35 M50 L5 No Details →
1.62.1 C4 H35 M50 L5 No Details →
1.62 C4 H35 M50 L5 No Details →
1.61 C4 H35 M50 L5 No Details →
1.60 C4 H35 M50 L5 No Details →
1.59 C4 H35 M50 L5 No Details →
1.58.1 C4 H35 M50 L5 No Details →
1.58 C4 H35 M50 L5 No Details →
1.57 C4 H35 M50 L5 No Details →
1.56 C4 H35 M50 L5 No Details →
1.55 C4 H35 M50 L5 No Details →
1.54 C4 H35 M50 L5 No Details →
1.53.1 C4 H35 M50 L5 No Details →
1.53 C4 H35 M50 L5 No Details →
1.52 C4 H38 M50 L5 No Details →
1.51 C4 H38 M50 L5 No Details →
1.50.1 C4 H38 M50 L5 No Details →
1.50 C4 H38 M52 L5 No Details →

Newest 120 of 162 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 6
  • 2021 7
  • 2022 29
  • 2023 12
  • 2024 24
  • 2025 15
  • 2026 18

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 22 of the 111 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for librenms/librenms

The 5 most severe of 111 vulnerabilities recorded for this package

Search all 111 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-10665: LibreNMS Information Disclosure 9.8 critical No fix published 24 May 2022
CVE-2018-20434: LibreNMS arbitrary OS commands execution 9.8 critical No fix published 24 May 2022
CVE-2022-4070: Insufficient Session Expiration in librenms/librenms 9.8 critical 22.10.0 20 Nov 2022
CVE-2022-40705: Apache SOAP's RPCRouterServlet allows reading of arbitrary files over HTTP 9.8 critical 22.10.0 20 Nov 2022
CVE-2021-44278: Path traversal vulnerability in librenms/librenms 9.8 critical No fix published 10 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About librenms/librenms

Is librenms/librenms safe to use?

Vulert records 111 vulnerabilities for librenms/librenms in Packagist: 6 critical, 41 high, 58 medium and 6 low. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does librenms/librenms have?

111 vulnerabilities are recorded for librenms/librenms in the Packagist ecosystem: 6 critical, 41 high, 58 medium and 6 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new librenms/librenms vulnerabilities disclosed?

22 vulnerabilities were recorded for librenms/librenms in the last 12 months, and the oldest entry in this database dates to 11 Oct 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of librenms/librenms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor librenms/librenms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the librenms/librenms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.