# CVE-2026-2750: Command Injection via CLAPI generatetraps

> Attackers can execute arbitrary commands on the Centreon Central Server via improper input validation in the Open Tickets module.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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:** No
- **Published:** 27 Feb 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-34c9-25wc-q378

## What is CVE-2026-2750?

CVE-2026-2750 is a critical command injection vulnerability in Centreon Open Tickets on Central Server, published on 27 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Input Validation vulnerability in Centreon Centreon Open Tickets on Central Server on Linux (Centreon Open Tickets modules).This issue affects Centreon Open Tickets on Central Server: from all before 25.10; 24.10;24.04.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Centreon Web.

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

No fix has been published for CVE-2026-2750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2750 is a critical command injection vulnerability in Centreon Open Tickets on Central Server, published on 27 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2750 in the wild and no public exploit code.

Affected product: Centreon Open Tickets on Central Server. 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-2750/ (Markdown: https://insights.sbomify.com/CVE-2026-2750/index.md)
```

## Sources

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

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