dbcve.org
NomadApplication · Hashicorp

CVE-2025-1296

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 1.7.19 / 1.8.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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”) are vulnerable to unintentional exposure of the workload identity token and client secret token in audit logs. This vulnerability, identified as CVE-2025-1296, is fixed in Nomad Community Edition 1.9.7 and Nomad Enterprise 1.9.7, 1.8.11, and 1.7.19.

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 contains an information disclosure vulnerability where workload identity tokens and client secret tokens are unintentionally written to audit logs, potentially exposing sensitive authentication credentials to unauthorized parties with access to those logs.

MitigationUpgrade to Nomad Community Edition 1.9.7 or Nomad Enterprise 1.9.7/1.8.11/1.7.19 as appropriate, and audit existing audit logs for any exposed tokens that may need to be rotated.

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.19>= 1.0.0, < 1.9.7>= 1.8.0, < 1.8.11>= 1.9.0, < 1.9.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check Nomad version
    Run `nomad version` or inspect the version file in the Nomad installation directory
    Affected if The installed version is 1.0.0 or higher but below 1.7.19, or 1.8.0-1.8.10, or 1.9.0-1.9.6
  2. Confirm audit logging is enabled
    Check the Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or /etc/nomad/config.hcl) for an `audit` block with `enabled = true`, or run `nomad operator audit list`
    Affected if Audit logging is enabled in the Nomad configuration
  3. Locate audit log files
    Check the audit log directory specified in the configuration (default is `/opt/nomad/audit/` or `/var/log/nomad/audit/`), or query the audit logs API with `nomad operator audit list` to see configured sinks
    Affected if Audit log files exist and are accessible
  4. Inspect audit logs for exposed tokens
    Search audit log files for the string patterns `wr_id` or `client_secret` or examine the JSON payload in audit logs for these fields appearing in request/response bodies
    Affected if Audit logs contain entries with `wr_id` or `client_secret` fields showing actual token values rather than redacted or masked values

The environment is affected if Nomad version is between 1.0.0 and 1.7.18, between 1.8.0 and 1.8.10, or between 1.9.0 and 1.9.6 AND audit logging is enabled, with exposed tokens visible in the audit logs.

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.19 / 1.8.11 / 1.9.7 or later
Fixed in 1.7.191.8.111.9.7
Interim mitigation

Upgrade to Nomad Community Edition 1.9.7 or Nomad Enterprise 1.9.7/1.8.11/1.7.19 as appropriate, and audit existing audit logs for any exposed tokens that may need to be rotated.

Recommended fix High confidence

Upgrade to Nomad 1.7.19, 1.8.11, or 1.9.7 (whichever is the minimum version greater than your current version)

  1. 1. Identify the current running version of Nomad using `nomad version`
  2. 2. Determine the appropriate upgrade path based on current version: if on 1.6.x or earlier, upgrade to 1.7.19; if on 1.8.x, upgrade to 1.8.11; if on 1.9.x, upgrade to 1.9.7
  3. 3. Review the Nomad upgrade guide and release notes for the target version for any migration requirements
  4. 4. Back up Nomad data directory and configuration files
  5. 5. Stop the Nomad service on all cluster nodes
  6. 6. Upgrade Nomad binaries to the fixed version (1.7.19, 1.8.11, or 1.9.7) on all nodes
  7. 7. Start the Nomad service on all cluster nodes
  8. 8. Verify the audit log configuration is active and functioning
Caveat Review release notes for any migration steps; minor version upgrades typically do not include breaking 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
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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