Medium Info disclosure

CVE-2025-61907 — Icinga 2 API users could access restricted values in filter expressions

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.

Published Oct 16, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+5
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.4%

ahead of 33% of scored CVEs · Oct 14, 2026

Affects

Icinga

Icinga and 1 more

CVSS base

6.5

Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Icinga Icinga, Icinga Icinga2).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Icinga	Icinga	≥ 2.4.0 and < 2.13.13≥ 2.14.0 and < 2.14.7version 2.15.0	Vulnerable	NIST National Vulnerability Database
Icinga	Icinga2	version >= 2.15.0, < 2.15.1version >= 2.14.0, < 2.14.7version >= 2.4.0, < 2.13.13	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.1	CVSS 4.0	High	—	—	security-advisories@github.com via NIST National Vulnerability Database
7.1	CVSS 4.0	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
6.5	CVSS 3.1	Medium	2.8	3.6	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.40%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for anomalous data read/export volumes and access to sensitive records.

web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · icinga/icinga2
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 6.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Oct 16, 2025 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/Icinga/icinga2/security/advisories/GHSA-gg32-w9rm-vp2v
Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
github.com/Icinga/icinga2/commit/56255ac7a689b9e198742d2fca6f7459a54c85a3
Patch, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

Icinga
every CVE for this vendor

Info disclosure
same class

CWE-200
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-61552 Icinga 2 DSL Injection via Unescaped Import Template Name 27d
High CVE-2026-61551 Icinga 2: Stack overflow via deeply nested JSON objects 27d
Medium CVE-2026-24413 Icinga has insecure permission of %ProgramData%\icinga2\var on Windows Jan 29, 2026
Medium CVE-2025-61909 Icinga 2 signals sent as root to processes based on PID file written by the Icinga 2 daemon user Oct 16, 2025
Medium CVE-2025-61908 Icinga 2 Denial of Service (DoS) By Dereferencing Invalid Reference Oct 16, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-61907 is "Icinga 2 API users could access restricted values in filter expressions", rated Medium. It affects Icinga (Icinga); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.40% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.