CVE-2026-8052

Medium
6.0
0.05.010.0
Year
2026
Published
May 12, 2026
Known Affected Devices
0
CVSS Score
6.0

What is CVE-2026-8052?

HashiCorp Nomad’s exec2 task driver prior to 0.1.2 is vulnerable to arbitrary file read and write on the client host as the Nomad process user through a symlink attack. This vulnerability (CVE-2026-8052) is fixed in version 0.1.2 of the exec2 task driver.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
AV
Attack Vector
Local

Requires local access — attacker must be logged in or have physical access to the device.

AC
Attack Complexity
Low

No special conditions required. Exploit can be performed reliably and repeatedly.

PR
Privileges Required
High

Administrative or root-level privileges required to exploit.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Changed

Exploiting the vulnerability can affect other components beyond the vulnerable one.

C
Confidentiality Impact
None

No confidentiality impact. Sensitive data is not exposed.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
None

No availability impact. Service remains fully operational.

FAQ

How severe is CVE-2026-8052?

CVE-2026-8052 has a CVSS score of 6.0/10, rated as Medium. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2026-8052?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-8052 scores 6.0/10 (Medium). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2026-8052?

The list of devices confirmed to be affected by CVE-2026-8052 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2026-8052?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.