# CVE-2026-109353: LibreNMS before 26.9.0 SQL Injection via notification_id in notifications.inc.php

> Unprivileged users can inject SQL to read password hashes via the notification_id parameter in LibreNMS.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-2pw7-8mmj-gcw5, GHSA-g9jw-2r94-hwjc

## What is CVE-2026-109353?

CVE-2026-109353 is a high-severity SQL injection vulnerability in librenms, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LibreNMS before 26.9.0 contains an SQL injection vulnerability that allows unprivileged users to inject SQL by supplying an array-valued notification_id parameter to notifications.inc.php. Attackers can perform cross-table reads of users.password hashes, with results persisted in notifications_attribs and readable through the interface.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-109353?


## How do I fix CVE-2026-109353?

No fix has been published for CVE-2026-109353 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109353 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109353 and fix it if it is affected.

What it is: CVE-2026-109353 is a high-severity SQL injection vulnerability in librenms, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109353 exists.

Affected product: librenms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109353/ (Markdown: https://insights.sbomify.com/CVE-2026-109353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109353
- OSV: https://osv.dev/vulnerability/CVE-2026-109353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109353/
Summaries are generated and may contain mistakes; the official description above is the record.