Skip to content

GHSA-c3q9-q986-vrwh CVE-2025-1296 GO-2025-3510

Nomad is vulnerable to unintentional exposure of the workload identity token and client secret token in audit logs

Medium Go
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.50%
Chance of exploitation in the next 30 days. Higher than 42.69% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-532 Insertion of Sensitive Information into Log File
Fix
1.9.7
Upgrade github.com/hashicorp/nomad to this version or later

Description

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.

Affected versions

Go

PackageVulnerableFixed in
github.com/hashicorp/nomad
<= 1.9.6
No fix yet
github.com/hashicorp/nomad
< 1.9.7
1.9.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/hashicorp/nomad Go → 1.9.7

go
go get github.com/hashicorp/nomad@v1.9.7 && go mod tidy

Severity breakdown

CVSS 3.1 6.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-hx53-77qj-8663
HashiCorp Nomad vulnerable to a path traversal
High Also affects github.com/hashicorp/nomad
GHSA-3934-423w-4jq3
HashiCorp Nomad vulnerable to symlink attack
Medium Also affects github.com/hashicorp/nomad
GHSA-rx97-6c62-55mf
Hashicorp Nomad Incorrect Privilege Assignment vulnerability
High Also affects github.com/hashicorp/nomad
GHSA-hr68-hvgv-xxqf
Hashicorp Nomad Incorrect Privilege Assignment vulnerability
Medium Also affects github.com/hashicorp/nomad
GHSA-2w5v-x29g-jw7j
Hashicorp Nomad Incorrect Authorization vulnerability
High Also affects github.com/hashicorp/nomad
GHSA-25qx-vfw2-fw8r
Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking
Medium Also affects github.com/hashicorp/nomad
GHSA-5mqx-rpxv-mvxj
HashiCorp Nomad is vulnerable to path escape through archive unpacking during migration
High Also affects github.com/hashicorp/nomad
GHSA-c866-8gpw-p3mv
HashiCorp Nomad vulnerable to symlink attacks
High Also affects github.com/hashicorp/nomad
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor