Vulnerability Database · Packagist · librenms/librenms · Version
librenms/librenms 201609.01
201609.01 is affected by 8 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 3 High 2 Medium 3 Low 0 Unrated 0
-
Database updated 23/Oct/2026
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 Vulnerabilities affecting this version
librenms/librenms 201609.01 vulnerabilities
8 vulnerabilities cover librenms/librenms 201609.01. Open the full list 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-2021-44278: Path traversal vulnerability in librenms/librenms | 9.8 critical | No fix published | 10 Dec 2021 |
| CVE-2022-3525: Deserialization of Untrusted Data in librenms/librenms | 8.8 high | No fix published | 20 Nov 2022 |
| CVE-2020-36947: LibreNMS Authenticated SQL Injection Vulnerability | 7.1 high | No fix published | 27 Jan 2026 |
| CVE-2021-44279: Cross-site Scripting in LibreNMS | 6.1 medium | No fix published | 03 Dec 2021 |
| CVE-2021-44277: Cross-site Scripting in LibreNMS | 6.1 medium | No fix published | 03 Dec 2021 |
| CVE-2025-65093: LibreNMS SQL Injection Vulnerability in ajax_output.php | 5.5 medium | No fix published | 18 Nov 2025 |
Looking for another version, or everything Vulert holds for librenms/librenms?
Questions
About librenms/librenms 201609.01
Is librenms/librenms 201609.01 vulnerable?
Yes. 8 vulnerabilities in the Vulert database cover librenms/librenms 201609.01: 3 critical, 2 high, 3 medium and 0 low. Each entry above names the fixed version to move to.
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.