CVE-2026-61552 json
Icinga 2 DSL Injection via Unescaped Import Template Name
published 4mo ago modified last mo. also EUVD-2026-83211 , GHSA-jgqj-x5j9-vgcm
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository Icinga/icinga2. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Icinga 2 is an open source monitoring system. From 2.4 until 2.14.9, 2.15.4, and 2.16.2, the /v1/objects API writes attacker-controlled template names into generated configuration without escaping them. An authenticated ApiUser with an objects/create/* permission can inject Icinga 2 DSL configuration, escape the intended object, create additional objects, and exceed the user's assigned privileges. This issue is fixed in versions 2.14.9, 2.15.4, and 2.16.2.
Patch / fix
- icinga icinga 2.14.9, 2.15.4, 2.16.2
- icinga2 Debian 13 2.14.6-1+deb13u1
- icinga2 Debian 14 2.16.2-1
debian advisories DEBIAN-CVE-2026-61552
- github.com/Icinga/icinga2@125b773 commit
- github.com/Icinga/icinga2@af4b36e commit
- github.com/Icinga/icinga2@eec0d90 commit
- github.com/Icinga/icinga2@faf0450 commit
- github.com/Icinga/icinga2#10910 pull request
- github.com/Icinga/icinga2/releases/tag/v2.14.9 release
- github.com/Icinga/icinga2/releases/tag/v2.15.4 release
- github.com/Icinga/icinga2/releases/tag/v2.16.2 release
Is CVE-2026-61552 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Icinga icinga2
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
- github.com /Icinga/icinga2/pull/10910
- github.com /Icinga/icinga2/commit/125b7734e84d03f09b79d36c270152b11629a8c5
- github.com /Icinga/icinga2/commit/af4b36e6464b9b214bed270a53d6474cf91eb441
- github.com /Icinga/icinga2/commit/eec0d90e8303376fe772b3e4a04e3b064a44cf30
- github.com /Icinga/icinga2/commit/faf0450962ad678397991cfdf041810feafa71e7
-
github.com
/Icinga/icinga2/security/advisories/GHSA-jgqj-x5j9-vgcm
advisory
- github.com /Icinga/icinga2/releases/tag/v2.14.9
- github.com /Icinga/icinga2/releases/tag/v2.15.4
- github.com /Icinga/icinga2/releases/tag/v2.16.2
- icinga.com /blog/icinga2-security-release-v2-16-2
Sources
- CVE List CVE-2026-61552
- NVD CVE-2026-61552
- Maintainer advisory GHSA-jgqj-x5j9-vgcm
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Icinga/icinga2 published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.