CVE-2026-26987
Reflected XSS in LibreNMS Email Field Allows Script Injection
Publication date: 2026-02-20
Last updated on: 2026-02-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| librenms | librenms | to 26.2.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-26987 is a reflected Cross-Site Scripting (XSS) vulnerability in LibreNMS version 25.12.0 and below. It occurs specifically in the email address input field within the settings alerting email page. An attacker can inject malicious JavaScript code into this email field, which is then reflected back and executed in the victim's browser, for example via toast notification messages. This allows arbitrary script execution in the context of the user's browser session."}, {'type': 'paragraph', 'content': 'The vulnerability was caused by the application directly injecting error messages containing user input as HTML content into toast notifications without proper sanitization. The fix involved changing the frontend code to treat error messages as plain text by creating a DOM element and setting its textContent property, preventing script execution.'}] [1, 3, 4]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability can lead to the execution of arbitrary JavaScript code in the context of a user's browser session when they interact with the vulnerable LibreNMS interface. This can result in security risks such as theft of session cookies, which may enable attackers to perform Account Takeover (ATO) attacks."}, {'type': 'paragraph', 'content': "Because the malicious script runs in the victim's browser, it can potentially manipulate the user interface, steal sensitive information, or perform actions on behalf of the user without their consent."}] [3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability is a reflected Cross-Site Scripting (XSS) issue in the email field of LibreNMS settings at the URL path /settings/alerting/email. Detection involves testing if the email input field reflects injected JavaScript code.'}, {'type': 'paragraph', 'content': 'A common detection method is to attempt injecting a harmless XSS payload such as <img src=1 onerror=alert(document.cookie)> into the email field and observe if the script executes in the browser.'}, {'type': 'paragraph', 'content': 'Since this is a web application vulnerability, detection commands would typically involve using web security testing tools or manual testing with curl or browser developer tools.'}, {'type': 'list_item', 'content': 'Use curl to submit a POST request with a malicious payload in the email field to the vulnerable endpoint and check the response for reflected script tags.'}, {'type': 'list_item', 'content': "Example curl command: curl -X POST -d 'email=<img src=1 onerror=alert(document.cookie)>' https://your-librenms-instance/settings/alerting/email"}, {'type': 'list_item', 'content': 'Use a web proxy tool like Burp Suite or OWASP ZAP to intercept and modify requests to inject XSS payloads and observe if the payload is executed.'}, {'type': 'paragraph', 'content': 'Note that automated scanning tools that detect reflected XSS vulnerabilities can also be used against the LibreNMS web interface.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade LibreNMS to version 26.2.0 or later, where this reflected XSS vulnerability has been fixed.
The fix sanitizes user input in the email field by ensuring error messages are safely displayed as plain text rather than executable HTML or JavaScript.
Until the upgrade can be applied, restrict access to the LibreNMS web interface to trusted users only, to reduce the risk of exploitation.
Avoid entering untrusted or suspicious data into the email field or other settings fields that may be vulnerable to reflected XSS.
Monitor for unusual activity or alerts that may indicate exploitation attempts.