Quick answers
- Is CVE-2026-109355 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109355 being exploited in the wild.
- How severe is CVE-2026-109355?
- Medium severity, with a CVSS score of 6.1, published 12 October 2026.
- Which products and versions are affected?
- Librenms before 26.9.0.
- Is there a fix for CVE-2026-109355?
- Yes: fixed in 26.9.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109355 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109355?
- Check whether you run Librenms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 26.9.0
Technical details
The get_oxidized_nodes_list() function in includes/html/functions.inc.php renders six unescaped fields from Oxidized API responses (name, status, time, model, group) and device SNMP sysName directly into HTML table cells without htmlspecialchars() or equivalent output encoding. An attacker controlling the Oxidized endpoint (via admin misconfiguration, compromise, or DNS hijacking) or any device's SNMP responses can inject script tags or event handlers that execute in the browser of any user viewing the Tools → Oxidized page with appropriate device permissions. The vulnerability is a stored XSS: payloads persist in the monitored infrastructure and execute on every page view.
Affected products
- LibreNMS LibreNMS before 26.9.0
Timeline
- 2026-10-12: disclosed
- 2026-09-23: advisory: GitHub GHSA-cjqw-76mh-jmpv published
- 2026-09-23: patched: Fixed in version 26.9.0