# CVE-2025-48057: Icinga 2 certificate renewal might incorrectly renew an invalid certificate

> Attackers can bypass certificate validation to obtain valid certificates and impersonate trusted nodes in Icinga 2 when built with older OpenSSL versions.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2025
- **Updated:** 27 May 2025
- **Also known as:** DEBIAN-CVE-2025-48057, GHSA-7vcf-f5v9-3wr6, SUSE-SU-2025:02783-1, UBUNTU-CVE-2025-48057, openSUSE-SU-2025:15180-1

## What is CVE-2025-48057?

CVE-2025-48057 is a critical vulnerability in icinga2, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Icinga 2 is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. Prior to versions 2.12.12, 2.13.12, and 2.14.6, the VerifyCertificate() function can be tricked into incorrectly treating certificates as valid. This allows an attacker to send a malicious certificate request that is then treated as a renewal of an already existing certificate, resulting in the attacker obtaining a valid certificate that can be used to impersonate trusted nodes. This only occurs when Icinga 2 is built with OpenSSL older than version 1.1.0. This issue has been patched in versions 2.12.12, 2.13.12, and 2.14.6.

Weakness: CWE-296 (Improper Following of a Certificate's Chain of Trust)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `icinga2` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 2.8.2-3.11.2 |
| `icinga2` | openSUSE:Tumbleweed | All versions | 2.14.6-1.1 |

Products: Icinga Icinga.

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

Upgrade to a fixed version.

## Is CVE-2025-48057 being exploited?

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

## Other vulnerabilities in icinga2

- [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)
- [CVE-2018-6533](https://insights.sbomify.com/CVE-2018-6533/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48057 is a critical vulnerability in icinga2, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48057 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-48057/ (Markdown: https://insights.sbomify.com/CVE-2025-48057/index.md)
```

## Sources

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

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