Skip to main content
VulnerabilityPublished Updated

CVE-2025-44824: Nagios Log Server · Incorrect Authorization

Affects Nagios Log ServerSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.7% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Nagios Log ServerAffected
  • =0
Fixed in–

AI-suggested

Immediate mitigation steps include restricting API access to trusted and minimal users, enforcing strong authentication and authorization policies, and monitoring API usage for suspicious stop commands targeting Elasticsearch. Network segmentation and firewall rules should limit access to the Nagios Log Server API endpoints. Organizations should prepare to apply vendor patches or updates as soon as they become available for version 2024R1.3.2 or later. In the interim, consider disabling or restricting the vulnerable API endpoint if feasible. Implementing robust logging and alerting on service stop events can help detect exploitation attempts early. Regularly audit user privileges to ensure that read-only API access is granted only to necessary personnel. Finally, organizations should review incident response plans to address potential monitoring outages caused by this vulnerability.

Description

Nagios Log Server before 2024R1.3.2 allows authenticated users (with read-only API access) to stop the Elasticsearch service via a /nagioslogserver/index.php/api/system/stop?subsystem=elasticsearch call. The service stops even though "message": "Could not stop elasticsearch" is in the API response. This is GL:NLS#474.

References

Community reviews

Loading reviews…