CVE-2025-34269: Nagios Fusion < R2.1 2FA Lack of Re-Authentication or Session Rotation
Published Oct 30, 2025
·Updated
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2025-60424.
Affected Software
10 affected components
Nagios Fusion<R2.1
Nagios Fusion<=4.2.0
Nagios Fusion=2024-r1
Nagios Fusion=2024-r1.0.1
Nagios Fusion=2024-r1.0.2
Nagios Fusion=2024-r1.0.3
Nagios Fusion=2024-r1.1
Nagios Fusion=2024-r1.1.1
Nagios Fusion=2024-r1.2
Nagios Fusion=2024-r2
Event History
Oct 30, 2025
CVE Published
via MITRE·09:19 PM
Rejected
via MITRE·09:19 PM
Data Sourced
via NVD·10:15 PM
Description
Nov 7, 2025
Rejected
via MITRE·06:20 PM
Frequently Asked Questions
1
What is the severity of CVE-2025-34269?
The severity of CVE-2025-34269 is considered high due to the potential for unauthorized access through valid sessions.
2
How do I fix CVE-2025-34269?
To fix CVE-2025-34269, upgrade Nagios Fusion to version R2.1 or later, which includes necessary security improvements.
3
What does CVE-2025-34269 affect?
CVE-2025-34269 affects Nagios Fusion versions prior to R2.1 specifically regarding two-factor authentication implementation.
4
What causes CVE-2025-34269?
CVE-2025-34269 is caused by the lack of re-authentication or session rotation when two-factor authentication is enabled.
5
Who can exploit CVE-2025-34269?
Any unauthorized adversary who has obtained a valid session can exploit CVE-2025-34269 to continue accessing an account.