Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-15612: Wazuh provisioning scripts and Dockerfiles contain an insecure transport vulnerability where curl is invoked w

35
This week
MEDIUM 4.8REMOTEWATCHLISTUPGRADE

CVE-2025-15612 is a medium-severity flaw (CVSS 4.8) affecting wazuh. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score4.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 87%)
CISA exploited listNo
WeaknessCWE-295, CWE-829
Published2026-03-27
Last modified2026-10-07
Publisher (CNA): VulnCheck · Vendor: wazuh

Share: LinkedIn · X · Reddit

Last updated 2026-10-07 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

wazuh wazuh UPGRADE
Affected: >= 4.1.3 and < 4.14.0
Fixed in: 4.14.0
Safe to downgrade to: a release before 4.1.3
1. Check installed version
apt-cache policy wazuh || rpm -q wazuh || wazuh --version
2. UPGRADE to 4.14.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade wazuh
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade wazuh
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.1.3 (Debian / Ubuntu)
apt-cache madison wazuh sudo apt install wazuh=<VERSION_BEFORE_4.1.3> sudo apt-mark hold wazuh
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list wazuh sudo dnf downgrade wazuh-<VERSION_BEFORE_4.1.3> sudo dnf versionlock add wazuh
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-15612?

wazuh: upgrade to 4.14.0. Exact commands for each OS are on this page.

Is CVE-2025-15612 being exploited?

CVE-2025-15612 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-15612 affect?

CVE-2025-15612 affects wazuh. Severity is medium (CVSS 4.8). 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

How urgent is CVE-2025-15612?

Priority 35/100. Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

curl vulnerabilities · Wazuh vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.