# CVE-2026-61552: Icinga 2 DSL Injection via Unescaped Import Template Name

> Authenticated users can inject DSL code via unescaped template names in the API, leading to privilege escalation and potential code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-61552, GHSA-jgqj-x5j9-vgcm, UBUNTU-CVE-2026-61552

## What is CVE-2026-61552?

CVE-2026-61552 is a high-severity code injection vulnerability in icinga2, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-61552?


## How do I fix CVE-2026-61552?

Upgrade to a fixed version.

## Is CVE-2026-61552 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61552 and fix it if it is affected.

What it is: CVE-2026-61552 is a high-severity code injection vulnerability in icinga2, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61552 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-2026-61552/ (Markdown: https://insights.sbomify.com/CVE-2026-61552/index.md)
```

## Sources

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

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