CVE-2024-12678: Nomad Allocations Vulnerable To Privilege Escalation Within A Namespace Using Unredacted Workload Identity Tokens
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: HashiCorp Nomad 1.9.4; HashiCorp Nomad Enterprise 1.7.16, 1.8.8, 1.9.4.
Low priority for now. Upgrade to HashiCorp Nomad 1.9.4; HashiCorp Nomad Enterprise 1.7.16, 1.8.8, 1.9.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Nomad Community and Nomad Enterprise ("Nomad") allocations are vulnerable to privilege escalation within a namespace through unredacted workload identity tokens. This vulnerability, identified as CVE-2024-12678, is fixed in Nomad Community Edition 1.9.4 and Nomad Enterprise 1.9.4, 1.8.8, and 1.7.16.
- Published
- Dec 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-266
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HashiCorp
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | nomad | cpe:2.3:a:hashicorp:nomad |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Nomad
- 1.4.0 and later · before 1.9.4affected · semver
HashiCorp Nomad Enterprise
- 1.4.0 and later · before 1.9.4affected · semverfixed in 1.8.8, 1.7.16
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp nomad1.4.0 and later · before 1.7.16
- hashicorp nomad1.4.0 and later · before 1.9.4
- hashicorp nomad1.8.0 and later · before 1.8.8
- hashicorp nomad1.9.0 and later · before 1.9.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/hashicorp/nomad | before 1.9.4 | 1.9.4 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250108T191942-150000.1.26.1 | 0.0.20250108T191942-150000.1.26.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20241220T214820-1.1 | 0.0.20241220T214820-1.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250108T191942-150000.1.26.1 | 0.0.20250108T191942-150000.1.26.1 |
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-12618HashiCorp Nomad 0.9.0 through 0.9.1 has Incorrect Access Control via the exec driver.40Plan
- CVE-2023-1782Nomad Unauthenticated Client Agent HTTP Request Privilege Escalation39Monitor
- CVE-2022-30324HashiCorp Nomad and Nomad Enterprise version 0.2.0 up to 1.3.0 were impacted by go-getter vulnerabilities enabling privilege escalation…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-7625Aug 14, 2024 · Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking23Monitor
- ← EarlierCVE-2024-10975Nov 7, 2024 · Nomad Vulnerable To Cross-Namespace Volume Creation Abusing CSI Write Permission30Monitor
- Later →CVE-2025-0937Feb 12, 2025 · Nomad Vulnerable To Event Stream Namespace ACL Policy Bypass Through Wildcard Namespace28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Nomad | 1.9.4 | Vendor (CNA) |
| HashiCorp Nomad Enterprise | 1.7.16 | Vendor (CNA) |
| HashiCorp Nomad Enterprise | 1.8.8 | Vendor (CNA) |
| HashiCorp Nomad Enterprise | 1.9.4 | Vendor (CNA) |
| Go:github.com/hashicorp/nomad | 1.9.4 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250108T191942-150000.1.26.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20250108T191942-150000.1.26.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-4922174 days apartNomad Vulnerable To Incorrect ACL Policy Lookup Attached To A Job32Monitor
- CVE-2025-3744145 days apartNomad Vulnerable To Violation Of Mandatory Sentinel Policies in Nomad Job Submissions via Policy Override30Monitor
- CVE-2023-3300519 days apartNomad Search API Leaks Information About CSI Plugins21Monitor
- CVE-2023-3072519 days apartNomad ACL Policies without Label are Applied to Unexpected Resources15Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-266 · Incorrect Privilege AssignmentCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.