CVE-2026-84189
Stored XSS in LibreNMS Oxidized integration allows persistent JavaScript execution.
Is CVE-2026-84189 being exploited?
Not confirmed. CVE-2026-84189 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-84189?
CVE-2026-84189 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84189?
Yes. A fix has been recorded for CVE-2026-84189. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84189 affect?
CVE-2026-84189 affects LibreNMS <= 26.4.0 (Oxidized integration), Fixed in LibreNMS 26.7.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84189?
Upgrade LibreNMS to 26.7.0 immediately; restrict/remove untrusted oxidized.url until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored/persistent XSS via Oxidized JSON fields enabling JS execution in users' browsers — session theft, account takeover, actions as victim.
Immediate action required
- affected< 26.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.