Is CVE-2026-112338 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-112338 being exploited in the wild.

How severe is CVE-2026-112338?

Medium severity, with a CVSS score of 5.9, published 6 November 2026.

Which products and versions are affected?

Wazuh Agent 4.3.0 to 4.14.8; Wazuh Manager 4.3.0 to 4.14.8.

How is CVE-2026-112338 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-112338?

Check whether you run Wazuh Agent or Wazuh Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112338: Wazuh GitHub module server-side request forgery in pagination

CVE-2026-112338 · Severity: medium · CVSS 5.9 · Published 2026-11-06

Wazuh is a security monitoring platform that collects GitHub organization audit logs to track administrative and repository activity. A vulnerability in the GitHub module allows attackers to redirect API requests to attacker-controlled servers while the GitHub authentication token remains attached, exposing private repositories, audit logs, and enabling unauthorized actions on the organization.

Technologies: Wazuh Agent, Wazuh Manager. Vendors: Wazuh.

Quick answers

Is CVE-2026-112338 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112338 being exploited in the wild.
How severe is CVE-2026-112338?: Medium severity, with a CVSS score of 5.9, published 6 November 2026.
Which products and versions are affected?: Wazuh Agent 4.3.0 to 4.14.8; Wazuh Manager 4.3.0 to 4.14.8.
Is there a fix for CVE-2026-112338?: Yes: fixed in Wazuh Manager 4.14.9, Wazuh Agent 4.14.9. Until then: Restrict network access from the Wazuh manager to only the configured GitHub or GitHub Enterprise API host (api.github.com by default), preventing requests to attacker-controlled servers. Disable the GitHub module if not actively monitoring GitHub audit logs. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112338 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-112338?: Check whether you run Wazuh Agent or Wazuh Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Wazuh Manager 4.14.9, Wazuh Agent 4.14.9

Restrict network access from the Wazuh manager to only the configured GitHub or GitHub Enterprise API host (api.github.com by default), preventing requests to attacker-controlled servers. Disable the GitHub module if not actively monitoring GitHub audit logs.

Technical details

The GitHub module in wm_github.c trusts the Link: rel="next" pagination header without validating the host, allowing an attacker to inject a malicious URL that causes the manager to make requests to attacker-controlled hosts while retaining the GitHub API token in the Authorization header. An attacker can exploit this if they control or can influence the HTTP response from GitHub, or if a man-in-the-middle attack is possible. This is a server-side request forgery (SSRF) with credential forwarding.

Affected products

Wazuh Manager 4.3.0 to 4.14.8
Wazuh Agent 4.3.0 to 4.14.8

Timeline

2026-11-06: disclosed
2026-10-15: patched: Wazuh v4.14.9 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.