CVE-2022-3866 json
Nomad Workload Identity Token Can List Non-sensitive Metadata for Paths Under nomad/
published 2022-11-10 3 y ago modified 2026-06-17 4 mo ago also GHSA-7wg4-8m5p-hrfg , GO-2022-1105 , EUVD-2022-7271
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 workload identity token can list non-sensitive metadata for paths under nomad/ that belong to other jobs in the same namespace. Fixed in 1.4.2.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/nomad | >=1.4.0, <1.4.2 |
1.4.2 |
Affected products
- HashiCorp Nomad
- HashiCorp Nomad Enterprise
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
github.com
/hashicorp/nomad/commit/3b24f26603e2b116ba324101afa8a7e3a7a769a5
web, patch
-
discuss.hashicorp.com
/t/hcsec-2022-25-nomad-s-workload-identity-token-can-list-non-sensitive-metadata-for-nomad-paths/46167
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3866
advisory
-
github.com
/hashicorp/nomad
package
-
github.com
/advisories/GHSA-7wg4-8m5p-hrfg
advisory
Sources
- CVE List CVE-2022-3866
- GitHub Advisory GHSA-7wg4-8m5p-hrfg
- NVD CVE-2022-3866
- OSV GO-2022-1105
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.