How severe is CVE-2019-15949?

CVE-2019-15949 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2019-15949?

Affected package information for CVE-2019-15949 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2019-15949?

Apply the nagios nagios xi security patch or hotfix for CVE-2019-15949 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2019-15949 across my infrastructure?

Inventory every nagios nagios xi deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2019-15949 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2019-15949?

O3 detects and blocks CVE-2019-15949 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2019-15949 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2019-15949, including 2 documented proof-of-concept exploits on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-15949?

CVE-2019-15949 has an EPSS (Exploit Prediction Scoring System) score of 77.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-15949 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-15949 (Nagios XI Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-15949?

CVE-2019-15949 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2019-15949?

CVE-2019-15949 affects nagios nagios xi. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2019-15949?

3 Metasploit modules reference CVE-2019-15949, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-15949 published, and has it been updated?

CVE-2019-15949 was published on September 5, 2019 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2019-15949

HIGH

Nagios XI before 5.6.6 allows remote command execution as root. The exploit requires access to the server as the nagios user, or access as the admin user via the web interface. The…

Published

Sep 5, 2019

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

77.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Nagios XI before 5.6.6 allows remote command execution as root. The exploit requires access to the server as the nagios user, or access as the admin user via the web interface. The getprofile.sh script, invoked by downloading a system profile (profile.php?cmd=download), is executed as root via a passwordless sudo entry; the script executes check_plugin, which is owned by the nagios user. A user logged into Nagios XI with permissions to modify plugins, or the nagios user on the server, can modify the check_plugin executable and insert malicious commands to execute as root.

Affected Products

1 product · 1 configurations

Application

nagios xinagios

< 5.6.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-48191remotelinux✓ Verified

Nagios XI - Authenticated Remote Command Execution (Metasploit)

by Metasploit · Mar 10, 2020

Exploit-DB Source

EDB-52138webappsmultiple

Nagios Xi 5.6.6 - Authenticated Remote Code Execution (RCE)

by Calil Khalil · Apr 8, 2025

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every nagios nagios xi deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the nagios nagios xi security patch or hotfix for CVE-2019-15949 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2019-15949 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2019-15949. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2019-15949 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2019-15949 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works