CVE-2026-109353 librenms CVE debrief

Who should care

Defenders responsible for LibreNMS installations, especially in environments where unprivileged user access is common, should verify and remediate this vulnerability. This includes operators, platform administrators, vulnerability management teams, and security teams who need to assess the impact of this vulnerability on their systems and take necessary actions to prevent exploitation.

Why it matters

LibreNMS before 26.9.0 contains an SQL injection vulnerability that allows unprivileged users to inject SQL and read sensitive information. Defenders should prioritize verifying and remediating this vulnerability.

• Unprivileged users can inject SQL and read users.password hashes.
• Results are persisted in notifications_attribs and readable through the interface.
• Defenders should verify and remediate this vulnerability to prevent potential exploitation.
• Remediation priority is high due to the potential for sensitive information disclosure.

Technical summary

The SQL injection vulnerability in LibreNMS before 26.9.0 allows unprivileged users to inject SQL by supplying an array-valued notification_id parameter to notifications.inc.php. This can lead to cross-table reads of users.password hashes. The vulnerability has a high severity score and requires immediate attention from defenders responsible for LibreNMS installations, especially in environments where unprivileged user access is common. Defenders should prioritize verifying and remediating this vulnerability in LibreNMS installations.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in LibreNMS installations, especially in environments where unprivileged user access is common.

Recommended defensive actions

• Verify and remediate this vulnerability in LibreNMS installations, especially in environments where unprivileged user access is common.
• Restrict access to notifications.inc.php and validate user input for notification_id.
• Monitor for suspicious activity related to notifications and user accounts.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the SQL injection vulnerability in LibreNMS before 26.9.0. The vulnerability allows unprivileged users to inject SQL and read users.password hashes. The source item provides additional context on the vulnerability, including its impact on LibreNMS installations. Defenders should verify and remediate this vulnerability to prevent potential exploitation.

Sources and references

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.