Skip to main content
CVE-2025-44823VulnerabilityPublished

CVE-2025-44823: Nagios Log Server · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects Nagios Log ServerSource CVE Database V5

0

Not known to be exploited · 16% EPSS · CVSS 9.9 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
16.1% chance of exploitation in 30 days – higher than 96% 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:H/I:H/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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Nagios Log ServerAffected
  • =0
Fixed in–

AI-suggested

1. Immediately upgrade Nagios Log Server to version 2024R1.3.2 or later, where the vulnerability is patched. 2. Restrict access to the /nagioslogserver/index.php/api/system/get_users endpoint by implementing network segmentation, firewall rules, and IP whitelisting to limit access to trusted administrators only. 3. Rotate all administrative API keys and any credentials that may have been exposed to invalidate compromised keys. 4. Implement strict authentication and authorization controls, including multi-factor authentication (MFA) for all users with access to Nagios Log Server. 5. Monitor logs and audit trails for unusual access patterns or API calls that could indicate exploitation attempts. 6. Conduct a thorough security review of Nagios Log Server configurations and integrate it into broader security monitoring and incident response workflows. 7. Educate administrators about the risks of exposing sensitive API keys and enforce secure key management practices. 8. Consider deploying web application firewalls (WAF) to detect and block suspicious API requests targeting this vulnerability.

Description

Nagios Log Server before 2024R1.3.2 allows authenticated users to retrieve cleartext administrative API keys via a /nagioslogserver/index.php/api/system/get_users call. This is GL:NLS#475.

References

Community reviews

Loading reviews…