Atomicorp WAF Research Note: CVE-2026-84189

LibreNMS before 26.7.0 Stored XSS via Oxidized API

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2026-84189
• Name: LibreNMS before 26.7.0 Stored XSS via Oxidized API
• Severity: Critical
• CVSS: 9.2 (v4.0) (Critical)
• CVSS version: 4.0
• CVSS source: VulnCheck CNA
• CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
  • Attack vector: Network
  • Attack complexity: Low
  • Attack requirements: None
  • Privileges required: High
  • User interaction: Passive
  • Vulnerable-system confidentiality: High
  • Vulnerable-system integrity: High
  • Vulnerable-system availability: None
  • Subsequent-system confidentiality: High
  • Subsequent-system integrity: High
  • Subsequent-system availability: None
  • Scope: X
• CWE: CWE-79 — Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)
• Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-209 (opens in a new tab) , CAPEC-588 (opens in a new tab) , CAPEC-591 (opens in a new tab) , CAPEC-592 (opens in a new tab) , CAPEC-63 (opens in a new tab) , CAPEC-85 (opens in a new tab)
• Vendor: librenms
• Vulnerable product: librenms
• CVE published: 2026-09-01
• CVE last modified: 2026-09-08
• EPSS: 0.0027; 18.4th percentile (FIRST (opens in a new tab) )
• Latest Update: 2026-09-06
• Selected Rule IDs observed: 333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148
• Matching rules: 10; rules with blocking actions: 10
• Would-block Rule IDs: 333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148
• Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, Request filename, Request headers, SOAP request data, XML request data

Vulnerability Description

LibreNMS through 26.4.0 renders JSON fields (name, ip, model, author, commit message) returned by the admin-configurable Oxidized integration URL (oxidized.url) into the device showconfig page without applying htmlspecialchars(). An administrator who points the Oxidized URL at an attacker-controlled server (SSRF) can cause it to return malicious JSON, resulting in stored/persistent cross-site scripting affecting all users who view any device’s showconfig tab. Fixed in 26.7.0.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: librenms versions earlier than 26.7.0.
   • Versions reported unaffected: librenms version 26.7.0.
   • Recommended upgrade: Upgrade librenms to 26.7.0 or later.

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• CVE authority reference: https://github.com/librenms/librenms/security/advisories/GHSA-7gww-x7fh-jf9j (opens in a new tab)
• CVE authority reference: https://www.vulncheck.com/advisories/librenms-before-26.7.0-stored-xss-via-oxidized-api (opens in a new tab)

Test or Research Source

• Source: Atomicorp AI Research Framework
• Tags: cve, derived, waf-probe, xss

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .