dbcve.org
NomadApplication · Hashicorp

CVE-2025-4922

HIGH · 8.1 CVSS v3.1 Published 2025-06-11
Fix available
A fix is available. Upgrade to 1.8.14 / 1.9.10 or later.
See remediation →
87/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”) prefix-based ACL policy lookup can lead to incorrect rule application and shadowing. This vulnerability, identified as CVE-2025-4922, is fixed in Nomad Community Edition 1.10.2 and Nomad Enterprise 1.10.2, 1.9.10, and 1.8.14.

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 · high confidence

Nomad's Access Control List (ACL) system has a flaw in prefix-based policy lookup where policies can be incorrectly applied or shadowed, potentially allowing unauthorized access or privilege escalation due to misapplied ACL rules.

MitigationUpgrade Nomad to version 1.10.2 (Community) or 1.10.2/1.9.10/1.8.14 (Enterprise) to patch the ACL policy lookup vulnerability.

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.4.0, < 1.8.14>= 1.4.0, < 1.10.2>= 1.9.0, < 1.9.10>= 1.10.0, < 1.10.2

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify ACL system is enabled
    Check Nomad configuration files (typically in /etc/nomad.d/) for the ACL block with enabled = true, or query the Nomad API at /v1/operator/cluster/health to inspect the ACLsEnabled field
    Affected if ACL is disabled - the vulnerability does not apply since it exploits the ACL policy lookup mechanism
  2. Determine installed Nomad version
    Run the command 'nomad version' to obtain the client and server version, or query the /v1/agent/self API endpoint
    Affected if Version is 1.4.0 through 1.8.13, or 1.9.0 through 1.9.9, or 1.10.0 through 1.10.1 (vulnerable version ranges)
  3. Identify prefix-based ACL policies in use
    Review ACL policy files or query the /v1/acl/policies API endpoint to list all ACL policies and examine them for policies that use prefix matching (such as namespace prefixes or path prefixes in policy rules)
    Affected if Prefix-based ACL policies exist and ACL is enabled on a vulnerable version - these policies can be incorrectly applied or shadowed due to the lookup flaw

If ACL is enabled and the Nomad version is within the affected ranges (1.4.0 to <1.8.14, 1.9.0 to <1.9.10, or 1.10.0 to <1.10.2) and prefix-based ACL policies are configured, the environment is affected by this vulnerability.

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.8.14 / 1.9.10 / 1.10.2 or later
Fixed in 1.8.141.9.101.10.2
Interim mitigation

Upgrade Nomad to version 1.10.2 (Community) or 1.10.2/1.9.10/1.8.14 (Enterprise) to patch the ACL policy lookup vulnerability.

Recommended fix High confidence

Nomad 1.10.2 (Community Edition) or Nomad Enterprise 1.10.2/1.9.10/1.8.14 depending on your current version

  1. 1. Back up your Nomad cluster state and configuration files
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Upgrade Nomad server nodes first, one at a time, ensuring leader election remains stable
  4. 4. After servers are upgraded, upgrade client nodes
  5. 5. Verify the cluster health using `nomad server members` and `nomad node status`
  6. 6. Test ACL policy functionality to confirm the prefix-based policy lookup issue is resolved
  7. 7. Review Nomad logs for any post-upgrade errors
Caveat Review HashiCorp migration guides; upgrading across major version jumps may require attention to configuration and API changes

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

Fix this in Nomad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4922 — 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-4922 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