CVE-2025-34283: Nagios XI · Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affects Nagios XISource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2024R1.4.2 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2024R1.4.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade Nagios XI to 2024R1.4.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NagiosXI | Affected
| Fixed in
|
AI-suggested
The primary mitigation is to upgrade Nagios XI installations to version 2024R1.4.2 or later, where the vulnerability has been patched. Organizations should immediately audit current API key usage and revoke any keys that may have been exposed or are no longer necessary. Implement strict role-based access controls to limit API key generation and visibility only to authorized users. Enable detailed logging and monitoring of API key usage to detect anomalous or unauthorized access patterns. Consider segregating monitoring infrastructure networks to reduce exposure. Regularly review and update user permissions to ensure least privilege principles are enforced. If upgrading is not immediately possible, restrict access to the Nagios XI web interface to trusted networks and users, and disable or limit the use of Neptune themes if feasible. Finally, conduct security awareness training for administrators and users about the risks of credential exposure.
Description
Nagios XI versions prior to 2024R1.4.2 revealed API keys to users who were not authorized for API access when using Neptune themes. An authenticated user without API privileges could view another user's or their own API key value.