dbcve.org
NomadApplication · Hashicorp

CVE-2025-3744

HIGH · 7.6 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 1.8.13 / 1.9.9 or later.
See remediation →
82/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 Enterprise (“Nomad”) jobs using the policy override option are bypassing the mandatory sentinel policies. This vulnerability, identified as CVE-2025-3744, is fixed in Nomad Enterprise 1.10.1, 1.9.9, and 1.8.13.

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 Enterprise jobs using the policy override option bypass mandatory sentinel policies, creating a security control bypass. The vulnerability allows job submissions to circumvent policy enforcement that should be non-optional.

MitigationUpgrade Nomad Enterprise to version 1.10.1, 1.9.9, or 1.8.13 (depending on current deployed version) to restore proper mandatory sentinel policy enforcement.

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.8.13>= 1.9.0, < 1.9.9= 1.10.0

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
Low
Integrity
High
Availability
Low

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

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. Identify Nomad version
    Run `nomad version` or query the API at `/v1/agent/self` to retrieve the installed version. Compare this version against the affected ranges: < 1.8.13, >= 1.9.0 and < 1.9.9, or = 1.10.0.
    Affected if The installed version falls within any of these ranges (less than 1.8.13, 1.9.0 through 1.9.8, or exactly 1.10.0).
  2. Confirm this is Nomad Enterprise
    Check the version output or API response for 'Enterprise' or 'ent' designation. This vulnerability only affects the Enterprise edition.
    Affected if The installation is Nomad Enterprise (not open-source Nomad).
  3. Verify Sentinel policies exist
    Query the Sentinel API at `/v1/sentinel/policies` or list policies using the CLI `nomad sentinel list` to see if any policies are defined.
    Affected if Sentinel policies are configured in the environment.
  4. Check for mandatory policies
    Review the Sentinel policies identified above and check their enforcement mode. In the API response or CLI output, look for policies with `"enforcement_level": "mandatory"` or equivalent.
    Affected if There are policies configured with mandatory enforcement level.
  5. Audit recent job submissions for override usage
    Query job submission logs, audit logs, or the API at `/v1/jobs` to look for job submissions that may have used the policy override flag. Check for query parameters or request fields indicating `policy-override` or similar override behavior.
    Affected if Any job submissions were made using the policy override option in the affected version.

You are affected if you are running a vulnerable Nomad Enterprise version (1.8.x before 1.8.13, 1.9.x before 1.9.9, or exactly 1.10.0) and have mandatory Sentinel policies configured that could be bypassed via the job submission policy override option.

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.13 / 1.9.9 or later
Fixed in 1.8.131.9.9
Interim mitigation

Upgrade Nomad Enterprise to version 1.10.1, 1.9.9, or 1.8.13 (depending on current deployed version) to restore proper mandatory sentinel policy enforcement.

Recommended fix High confidence

Nomad Enterprise 1.10.1 (or 1.9.9 or 1.8.13 depending on current version)

  1. 1. Identify the current Nomad Enterprise version by running `nomad version` or checking the Nomad UI
  2. 2. Determine the appropriate target version based on current version: if < 1.8.13 upgrade to 1.8.13; if >= 1.9.0 and < 1.9.9 upgrade to 1.9.9; if = 1.10.0 upgrade to 1.10.1
  3. 3. Review the HashiCorp Nomad Enterprise upgrade guide and release notes for the target version for any migration considerations
  4. 4. Back up your Nomad state and configuration files before upgrading
  5. 5. Upgrade the Nomad Enterprise cluster following the standard rolling upgrade procedure
  6. 6. Verify the upgrade by checking `nomad version` and confirming all nodes are running the patched version
  7. 7. Test that mandatory Sentinel policies are properly enforced for jobs using the policy override option
Caveat Review release notes for the target version 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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