Skip to main content
CVE-2025-4922VulnerabilityPublished

CVE-2025-4922: HashiCorp Nomad · Incorrect Privilege Assignment

Affects HashiCorp NomadSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High · fixed in 1.10.2 : patch HashiCorp Nomad soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.10.2, 1.9.10, 1.8.14
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade HashiCorp Nomad to 1.10.2, 1.9.10 or 1.8.14.

Affected software

ProductAffectedFixed in
HashiCorp NomadAffected
  • =1.4.0
  • <1.8.14
  • <1.9.10
  • <1.10.2
Fixed in
  • 1.8.14
  • 1.9.10
  • 1.10.2

AI-suggested

To mitigate CVE-2025-4922, European organizations should immediately upgrade affected Nomad installations to the patched versions: Nomad Community Edition 1.10.2 or later, and Nomad Enterprise 1.10.2, 1.9.10, or 1.8.14 or later. Beyond patching, organizations should audit their ACL policies to identify and correct any overlapping or ambiguous prefix rules that could cause shadowing or unintended privilege grants. Implement strict role-based access controls with the principle of least privilege to limit the impact of any potential privilege escalation. Regularly review and test ACL configurations using automated tools or scripts to detect policy conflicts. Network segmentation and monitoring should be enhanced to detect anomalous access patterns to Nomad servers. Employ logging and alerting on ACL-related events to quickly identify suspicious privilege changes. Finally, conduct security awareness and training for administrators managing Nomad ACLs to prevent misconfigurations that could exacerbate this vulnerability.

Description

Nomad Community and Nomad Enterprise (“Nomad”) prefix-based ACL policy lookup can lead to incorrect rule application and shadowing. This vulnerability, identified as CVE-2025-4922, is fixed in Nomad Community Edition 1.10.2 and Nomad Enterprise 1.10.2, 1.9.10, and 1.8.14.

References

Community reviews

Loading reviews…