# LibreNMS /port-groups name Stored Cross-Site Scripting

Advisory record · `GHSA-93fx-g747-695x`

- **Identifiers:** `GHSA-93fx-g747-695x` · `CVE-2026-26992` · `PKSA-zkdz-sv4x-6wvp`
- **State:** Confirmed
- **Severity:** CVSS 5.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 18 Feb 2026
- **Updated:** 20 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Feb 2026, 22:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `librenms/librenms` (Packagist): affected `<26.2.0`; fixed in `26.2.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> LibreNMS versions before 26.2.0 are affected by a stored cross-site scripting flaw in the name parameter of the /port-groups page, because port group names are not sanitized of HTML and JavaScript. An attacker with admin privileges can create a port group with a malicious name that runs script in the browser of any user who views the port group list, such as stealing session cookies. Upgrade librenms/librenms to version 26.2.0 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.1 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-93fx-g747-695x)

## Sources

- [GitHub Advisory Database: GHSA-93fx-g747-695x](https://github.com/advisories/GHSA-93fx-g747-695x)
- [OSV: GHSA-93fx-g747-695x](https://osv.dev/vulnerability/GHSA-93fx-g747-695x)
- <https://github.com/librenms/librenms/security/advisories/GHSA-93fx-g747-695x>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-26992>
- <https://github.com/librenms/librenms/pull/19042>
- <https://github.com/librenms/librenms/commit/882fe6f90ea504a3732f83caf89bba7850a5699f>
- <https://github.com/librenms/librenms>
- <https://github.com/librenms/librenms/releases/tag/26.2.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-93fx-g747-695x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-93fx-g747-695x/>. Everything for agents: <https://agentprime.io/llms.txt>.
