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

> Authenticated API users can access restricted variables and objects via filter expressions, leaking sensitive monitoring data.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-61907, GHSA-gg32-w9rm-vp2v, UBUNTU-CVE-2025-61907

## What is CVE-2025-61907?

CVE-2025-61907 is a high-severity vulnerability in icinga2, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-749 (Exposed Dangerous Method or Function), CWE-204 (Observable Response Discrepancy), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-61907?

It affects 1 product.


Products: Icinga Icinga.

## How do I fix CVE-2025-61907?

Upgrade to a fixed version.

## Is CVE-2025-61907 being exploited?

There is no known exploitation of CVE-2025-61907 in the wild and no public exploit code.

## Other vulnerabilities in icinga2

- [CVE-2025-48057](https://insights.sbomify.com/CVE-2025-48057/): Icinga 2 certificate renewal might incorrectly renew an invalid certificate (critical 9.3)
- [CVE-2020-29663](https://insights.sbomify.com/CVE-2020-29663/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-24820](https://insights.sbomify.com/CVE-2024-24820/): Icinga Director configuration is susceptible to Cross-Site Request Forgery (high 8.3)
- [CVE-2018-6535](https://insights.sbomify.com/CVE-2018-6535/): Information disclosure in n/a (high 8.1)
- [CVE-2020-14004](https://insights.sbomify.com/CVE-2020-14004/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61907 and fix it if it is affected.

What it is: CVE-2025-61907 is a high-severity vulnerability in icinga2, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61907 in the wild and no public exploit code.

Affected product: icinga2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61907/ (Markdown: https://insights.sbomify.com/CVE-2025-61907/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61907
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61907
- OSV: https://osv.dev/vulnerability/CVE-2025-61907

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61907/
Summaries are generated and may contain mistakes; the official description above is the record.