Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as restricted probe-permitted user
-
DeliveryRequest smokeping graph with arbitrary device id
-
ExploitServer checks src probe instead of target
-
ExecutionLatency data and device names disclosed
-
ImpactEnumerate monitored devices and topology
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated LibreNMS account that has been granted restricted-user permission on at least one smokeping probe device (PR:L) - it is NOT exploitable by fully unauthenticated attackers. The deployment must have smokeping graphing in use. Given that prerequisite, the attacker simply requests smokeping_in or smokeping_out graphs with arbitrary device IDs; no user interaction, non-default configuration, or special platform is needed. The limiting factor is the required valid restricted account with probe access; impact is confined to read-only disclosure of latency data and device names (no integrity or availability impact), which caps realistic risk to reconnaissance and enumeration. |
| Impact | This is a genuine but low-to-moderate-priority issue, and the available signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) scores 5.3 (Medium) and accurately reflects an authenticated information-disclosure flaw: network-reachable, low attack complexity, but requiring low-level authenticated access (PR:L) and yielding only limited confidentiality impact (VC:L) with no integrity or availability effect. This aligns with CWE-639 (IDOR / authorization bypass through user-controlled key) and the description, which confirms the impact is bounded to viewing smokeping latency data and enumerating device names - not code execution or data modification. No EPSS score, CISA KEV listing, SSVC decision, or confirmed proof-of-concept is present in the input, so there is no evidence of active exploitation or automatability; absence of these is expected for a low-severity IDOR and should not be read as either safety or elevated risk. Net: a real, valid authorization bug worth patching in the normal cycle, but not an emergency - the privilege prerequisite and information-only impact keep real-world risk modest, and the main consequence is reconnaissance (device-name/topology enumeration) that could aid a broader attack rather than direct compromise. |
| Exploit ScenarioDerived | A restricted LibreNMS user who has legitimately been granted access to a single smokeping probe device logs in and requests a smokeping_in or smokeping_out graph, substituting arbitrary device IDs in the request. Because the authorization check validates the source probe device rather than the rendered target device, the application returns latency graphs and device names for devices the user was never authorized to see, enabling enumeration of the monitored environment. No public exploit code is identified in the provided data, though a technical write-up describing the flaw is referenced. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
An authorization bypass in LibreNMS through 26.9.1.1 lets a restricted user who has been granted access on at least one smokeping probe device view smokeping latency graphs for devices they are not authorized to see, including enumeration of device names. The flaw is in the smokeping graph authorization include, which validates the src probe device rather than the rendered target device, so requesting smokeping_in or smokeping_out with arbitrary device IDs succeeds. Exploitation requires an authenticated restricted account with probe access and a deployment using smokeping graphing; the impact is limited to read-only information disclosure with no integrity or availability effect, no public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
No vendor-released patch version is identified in the available data, so the authoritative step is to track the LibreNMS project at https://github.com/librenms/librenms and the VulnCheck advisory at https://www.vulncheck.com/advisories/librenms-through-26.9.1.1-authorization-bypass-via-smokeping-graph-auth-inc-php for an updated release that corrects the authorization check in includes/html/graphs/smokeping/auth.inc.php; the referenced code at https://github.com/librenms/librenms/blob/26.9.1.1/includes/html/graphs/smokeping/auth.inc.php#L3-L7 and https://github.com/librenms/librenms/blob/26.9.1.1/LibreNMS/Util/Graph.php#L190-L198 can be used to apply or verify a manual fix. Until a patched build is available, restrict the blast radius by removing or tightening restricted-user smokeping probe permissions so no account holds partial device access that can be pivoted from (trade-off: reduces monitoring visibility for restricted operators), disabling smokeping graph rendering for untrusted roles via the LibreNMS web UI/ACL configuration (trade-off: legitimate users lose latency dashboards), and limiting web UI/API exposure of the LibreNMS instance to trusted management networks or a VPN (trade-off: complicates remote monitoring access). Because exploitation is read-only reconnaissance and enumeration, prioritizing these controls based on how sensitive device naming and topology data is in your environment is reasonable.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LibreNMS is a PHP-based network monitoring platform; smokeping integration renders latency graphs per monitored device. The affected code, includes/html/graphs/smokeping/auth.inc.php, performs its access-control check against the src (probe/source) query parameter instead of the device actually being rendered, a CWE-639 authorization bypass through user-controlled key. Because the device identifier in the request is attacker-controlled and the check is applied to the wrong object, any user holding permission on one probe device can pivot to arbitrary device IDs. The referenced Graph utility code in LibreNMS/Util/Graph.php handles graph rendering and device resolution, and the mismatch between the checked object and the rendered object is the root cause. The CPE entry cpe:2.3:a:librenms:librenms:*:*:*:*:*:*:*:* confirms all released versions through 26.9.1.1 are in scope. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:L/UI:N with only VC:L reflects a network-reachable, low-privilege, no-interaction information disclosure, and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) agrees that confidentiality is the only impacted metric.
Know when Librenms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable (AV:N) with low complexity (AC:L) but requires a low-privilege authenticated probe-permitted account (PR:L); impact is read-only disclosure, so C:L with I:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
LibreNMS through 26.9.1.1 contains an authorization bypass vulnerability in includes/html/graphs/smokeping/auth.inc.php that checks the src probe device instead of the rendered target device. Restricted users permitted on a probe device can request smokeping_in or smokeping_out graphs with arbitrary device ids to view latency data and enumerate device names.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
An issue was discovered in LibreNMS through 1.47. Rated high severity (CVSS 7.2), this vulnerability is remotely exploit
Librenms 21.11.0 is affected by a path manipulation vulnerability in includes/html/pages/device/showconfig.inc.php. Rate
An issue was discovered in LibreNMS through 1.47. Rated critical severity (CVSS 9.8), this vulnerability is remotely exp
Authentication bypass in the LibreNMS REST API (all versions before 26.8.0) lets unauthenticated remote attackers reach
SQL injection in LibreNMS 25.12.0 and below. PoC and patch available.
An issue was discovered in LibreNMS through 1.47. Rated critical severity (CVSS 9.1), this vulnerability is remotely exp
SQL injection in LibreNMS versions 25.12.0 and below allows authenticated users to extract sensitive database informatio
LibreNMS is an open-source, PHP/MySQL/SNMP-based network monitoring system. Rated high severity (CVSS 8.8), this vulnera
An issue was discovered in LibreNMS before 1.65.1. Rated high severity (CVSS 8.8), this vulnerability is remotely exploi
An issue was discovered in LibreNMS 1.50.1. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable,
An issue was discovered in LibreNMS through 1.47. Rated high severity (CVSS 8.8), this vulnerability is remotely exploit
Command injection in LibreNMS's Virtualization Discovery module enables authenticated administrator-level users to execu
EUVD-2026-96989
GHSA-jxv8-wv9v-5824
NVD
CVE.org
EPSS
Exploit-DB