Wazuh 3.7.0 before 4.14.9 SSRF via Azure Graph nextLink Pagination
- Exploited
- No known exploitation
- Fix
- Fixed in 4.14.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.14.9.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wazuh's Azure integration (the get_graph_events() function) can be made to send requests and the Microsoft Graph bearer token to attacker-controlled servers, which can expose the token and reach internal services. An attacker can exploit this remotely, without logging in, by influencing the pagination link value that Wazuh follows.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Wazuh from 3.7.0 before 4.14.9 contains a server-side request forgery vulnerability in the Azure wodle get_graph_events() function that follows @odata.nextLink without host or HTTPS validation. Attackers who influence the nextLink value can redirect manager requests to attacker-controlled endpoints, capturing the reused Microsoft Graph bearer token and reaching internal services.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.14.9.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wazuh wazuh
From 3.7.0 · fixed in 4.14.9
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112337
Is CVE-2026-112337 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-112337?
wazuh: from 3.7.0 before 4.14.9.Source: cve.now feed data
How do I fix CVE-2026-112337?
Upgrade to a fixed version: 4.14.9.Source: cve.now feed data