dbcve.org
NomadApplication · Hashicorp

CVE-2025-0937

HIGH · 7.1 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 1.7.18 / 1.8.10 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Nomad's event stream feature, when configured with a wildcard namespace, allows bypass of ACL policies that should restrict read access. This authorization flaw enables a user with limited namespace permissions to read events from namespaces they should not have access to, effectively circumventing the intended access control boundaries.

MitigationUpgrade to the patched Nomad version and review ACL policies to ensure wildcard namespace configurations do not grant unintended access across namespaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NomadApplication
Affected:>= 1.0.0, < 1.7.18>= 1.0.0, < 1.9.6>= 1.8.0, < 1.8.10>= 1.9.0, < 1.9.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Nomad version
    Run `nomad version` or check the Nomad server logs at startup to identify the exact version number
    Affected if The version is 1.0.0 to 1.7.17, 1.8.0 to 1.8.9, or 1.9.0 to 1.9.5 (i.e., any version before 1.7.18, 1.8.10, or 1.9.6)
  2. Verify ACLs are enabled
    Check Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or /etc/nomad/config.hcl) for the `acl` stanza with `enabled = true`, or query the Nomad API at /v1/operator/acl-bootstrap to confirm ACL status
    Affected if ACLs are enabled and the Nomad version is vulnerable
  3. Identify ACL policies with wildcard namespace
    Run `nomad acl policy list` to enumerate all ACL policies, then for each policy run `nomad acl policy info <policy-name>` and examine the `namespace` field in the event stream rules section
    Affected if Any ACL policy grants event stream access using a wildcard (*) namespace value
  4. Check for event stream API usage
    Review client applications or monitoring integrations that connect to Nomad's event stream endpoint (e.g., subscriptions to /v1/event/stream) to identify which policies are being used in practice
    Affected if The wildcard namespace policy from step 3 is actively being used to connect to the event stream API

A user is affected if running a vulnerable Nomad version, ACLs are enabled, and an ACL policy with a wildcard (*) namespace is being used to access the event stream feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.18 / 1.8.10 / 1.9.6 or later
Fixed in 1.7.181.8.101.9.6
Interim mitigation

Upgrade to the patched Nomad version and review ACL policies to ensure wildcard namespace configurations do not grant unintended access across namespaces.

Recommended fix High confidence

Upgrade to Nomad 1.7.18, 1.8.10, 1.9.6, or later respective to your current major version branch

  1. 1. Identify the currently installed Nomad version using `nomad version`
  2. 2. Review current ACL policies to identify any that use wildcard namespace (*) configurations for event streams
  3. 3. Upgrade Nomad to version 1.7.18, 1.8.10, or 1.9.6 (or higher) following the standard upgrade procedure for your deployment type
  4. 4. After upgrade, verify ACL policies are correctly enforcing namespace restrictions on event stream endpoints
  5. 5. Test that event stream subscriptions only allow access to explicitly permitted namespaces
Caveat Review release notes for your version branch to check for any breaking changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nomad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0937 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data