Centreon Open Tickets up to 25.10.2/24.10.7/24.04.6 path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Centreon Open Tickets up to 25.10.2/24.10.7/24.04.6. This vulnerability affects unknown code. This manipulation causes Remote Privilege Escalation. This vulnerability is registered as CVE-2026-2749. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Centreon Open Tickets up to 25.10.2/24.10.7/24.04.6. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a remote privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Vulnerability in Centreon Centreon Open Tickets on Central Server on Linux (Centroen Open Ticket modules).This issue affects Centreon Open Tickets on Central Server: from all before 25.10.3, 24.10.8, 24.04.7.
The weakness was published by Texugo. It is possible to read the advisory at thewatch.centreon.com. This vulnerability is known as CVE-2026-2749 since 02/19/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
Upgrading to version 25.10.3, 24.10.8 or 24.04.7 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 24.04.0
- 24.04.1
- 24.04.2
- 24.04.3
- 24.04.4
- 24.04.5
- 24.04.6
- 24.10.0
- 24.10.1
- 24.10.2
- 24.10.3
- 24.10.4
- 24.10.5
- 24.10.6
- 24.10.7
- 25.10.0
- 25.10.1
- 25.10.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CNA Base Score: 9.9
CNA Vector (Centreon): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Open Tickets 25.10.3/24.10.8/24.04.7
Timeline
02/19/2026 CVE reserved02/27/2026 Advisory disclosed
02/27/2026 VulDB entry created
03/23/2026 VulDB entry last update
Sources
Advisory: thewatch.centreon.comResearcher: Texugo
Status: Confirmed
CVE: CVE-2026-2749 (🔒)
GCVE (CVE): GCVE-0-2026-2749
GCVE (VulDB): GCVE-100-348175
Entry
Created: 02/27/2026 18:12Updated: 03/23/2026 18:44
Changes: 02/27/2026 18:12 (63), 03/23/2026 18:44 (14)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.