CVE-2026-112338: wazuh · Server-Side Request Forgery (SSRF)
Affects wazuhSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 4.14.9 soon.
Data as of 6 Nov 2026, 15:32 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 4.14.9
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade wazuh to 4.14.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wazuhwazuh | Affected
| Fixed in
|
GitHubwazuhpkg:github/wazuhOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Wazuh to version 4.14.9 or later, where this SSRF vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.
Description
Wazuh versions from 4.3.0 up to but not including 4.14.9 contain a server-side request forgery (SSRF) vulnerability in the GitHub module. This flaw allows attackers who can control the 'next' pagination URL to trick the Wazuh manager into sending requests with the GitHub API token to attacker-controlled hosts. This can lead to exposure of organization repositories and settings. The vulnerability is rated high severity with a CVSS score of 8.2. A fix is available in version 4.14.9.