PatchSiren cyber security CVE debrief
CVE-2026-86426 librenms CVE debrief
CVE-2026-86426 is a critical authentication bypass vulnerability in LibreNMS before version 26.8.0. The vulnerability allows unauthenticated attackers to access protected REST API endpoints by exploiting MySQL type coercion. This can lead to unauthorized access to device credentials and administrative features, potentially enabling remote code execution through alert templates.
- Vendor
- librenms
- Product
- Unknown
- CVSS
- CRITICAL 9.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-07
- Original CVE updated
- 2026-09-07
- Advisory published
- 2026-09-07
- Advisory updated
- 2026-09-07
Who should care
System administrators and security teams responsible for LibreNMS installations, especially those exposed to the internet or untrusted networks, should assess their exposure and prioritize remediation.
Why it matters
CVE-2026-86426 is a critical authentication bypass vulnerability in LibreNMS before version 26.8.0. It allows unauthenticated attackers to access protected REST API endpoints by exploiting MySQL type coercion, potentially leading to remote code execution. System administrators and security teams should assess their exposure and prioritize remediation.
- Potential unauthorized access to device credentials and administrative features.
- Possible remote code execution through alert templates.
- Exposure of sensitive information through API endpoints.
- Compromised integrity of LibreNMS installations.
Technical summary
The CVE-2026-86426 vulnerability in LibreNMS before version 26.8.0 allows unauthenticated attackers to bypass authentication in the REST API. By sending numeric values instead of string tokens, attackers can exploit MySQL type coercion to match token hashes. This grants access to protected API endpoints, including those providing device credentials and administrative features. Consequently, attackers may be able to execute remote code through alert templates.
Defensive priority
High priority for systems using LibreNMS, especially those exposed to the internet or untrusted networks.
Recommended defensive actions
- Immediately upgrade to LibreNMS version 26.8.0 or later if currently using an affected version.
- Restrict access to the LibreNMS API to trusted networks or implement additional authentication mechanisms.
- Monitor for suspicious API activity and implement logging and alerting for potential exploitation attempts.
- Review and limit the use of alert templates to prevent potential remote code execution.
- Verify the integrity of device credentials and administrative features.
Evidence notes
The vulnerability is confirmed in LibreNMS versions before 26.8.0. The CVE record and NVD entry provide details on the vulnerability, but specific version remediation details are not provided in the corpus.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-86426 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-86426
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-86426 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-86426
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/librenms/librenms/security/advisories/GHSA-cvq8-gqfq-3mvg
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/librenms-before-26.8.0-authentication-bypass-via-api-token-type-confusion
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.