Skip to main content
VulnerabilityPublished

CVE-2025-61907: Icinga icinga2 · Information Exposure

Affects Icinga icinga2Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in 2.15.1 : patch Icinga icinga2 soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.15.1, 2.14.7, 2.13.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 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

Upgrade icinga/icinga2 to 2.15.1, 2.14.7 or 2.13.13.

Affected software

ProductAffectedFixed in
GitHubicinga/icinga2pkg:github/icinga/icinga2Other threatsAffected
  • <2.13.13
  • >=2.13.0 <2.13.13
  • >=2.14.0 <2.14.7
  • >=2.15.0 <2.15.1
Fixed in
  • 2.13.13
  • 2.14.7
  • 2.15.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade all affected Icinga 2 instances to the fixed versions 2.15.1, 2.14.7, or 2.13.13 as applicable. Until patching is complete, restrict API access to trusted users and networks, enforce strict authentication and authorization policies, and audit API user permissions to ensure least privilege. Implement monitoring and alerting for unusual API queries or access patterns that could indicate exploitation attempts. Review and harden the configuration of Icinga 2’s API endpoints, disabling or limiting filter expression capabilities if possible. Conduct regular security assessments and penetration tests focusing on API access controls. Additionally, consider network segmentation to isolate monitoring infrastructure and reduce the attack surface. Maintain an inventory of all Icinga 2 deployments and ensure timely application of security updates.

Description

Icinga 2 is an open source monitoring system. In Icinga 2 versions 2.4 through 2.15.0, filter expressions provided to the various /v1/objects endpoints could access variables or objects that would otherwise be inaccessible for the user. This allows authenticated API users to learn information that should be hidden from them, including global variables not permitted by the variables permission and objects not permitted by the corresponding objects/query permissions. The vulnerability is fixed in versions 2.15.1, 2.14.7, and 2.13.13.

References

Community reviews

Loading reviews…