Wazuh up to 4.1.3/4.13.x TLS Certificate Validation certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Wazuh up to 4.1.3/4.13.x. It has been rated as critical. The affected element is an unknown function of the component TLS Certificate Validation Handler. Performing a manipulation results in certificate validation. This vulnerability is reported as CVE-2025-15612. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Wazuh up to 4.1.3/4.13.x. This affects an unknown function of the component TLS Certificate Validation Handler. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on integrity. The summary by CVE is:
Wazuh provisioning scripts and Dockerfiles contain an insecure transport vulnerability where curl is invoked with the -k/--insecure flag, disabling SSL/TLS certificate validation. Attackers with network access can perform man-in-the-middle attacks to intercept and modify downloaded dependencies or code during the build process, leading to remote code execution and supply chain compromise.
The weakness was disclosed by JLLeitschuh as GHSA-wvg9-7q49-c7mg. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-15612 since 03/20/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
Upgrading to version 4.14.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-209107) and CERT Bund (WID-SEC-2026-0908). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Open Source Wazuh
Product
Name
Version
Website
- Product: https://github.com/wazuh/wazuh/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.8
CNA Vector (VulnCheck): 🔒
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: Certificate validationCWE: CWE-295 / CWE-287
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: Wazuh 4.14.0
Timeline
03/20/2026 CVE reserved03/27/2026 Advisory disclosed
03/27/2026 VulDB entry created
03/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-wvg9-7q49-c7mg
Researcher: JLLeitschuh
Status: Confirmed
CVE: CVE-2025-15612 (🔒)
GCVE (CVE): GCVE-0-2025-15612
GCVE (VulDB): GCVE-100-353997
EUVD: 🔒
CERT Bund: WID-SEC-2026-0908 - Wazuh: Mehrere Schwachstellen
Entry
Created: 03/27/2026 23:33Updated: 03/30/2026 18:54
Changes: 03/27/2026 23:33 (77), 03/29/2026 05:12 (1), 03/30/2026 18:54 (7)
Complete: 🔍
Cache ID: 216:F98:103
No comments yet. Languages: en.
Please log in to comment.