syscall-unix up to 1.25.8/1.26.1 on Go Root.Chmod AT_SYMLINK_NOFOLLOW symlink

Summaryinfo

A vulnerability identified as critical has been detected in syscall-unix up to 1.25.8/1.26.1 on Go. This affects the function Root.Chmod. The manipulation of the argument AT_SYMLINK_NOFOLLOW leads to symlink. This vulnerability is listed as CVE-2026-32282. The attack must be carried out locally. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in syscall-unix up to 1.25.8/1.26.1 on Go and classified as critical. This issue affects the function Root.Chmod. The manipulation of the argument AT_SYMLINK_NOFOLLOW with an unknown input leads to a symlink vulnerability. Using CWE to declare the problem leads to CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root. The Linux fchmodat syscall silently ignores the AT_SYMLINK_NOFOLLOW flag, which Root.Chmod uses to avoid symlink traversal. Root.Chmod checks its target before acting and returns an error if the target is a symlink lying outside the root, so the impact is limited to cases where the target is replaced with a symlink between the check and operation.

The identification of this vulnerability is CVE-2026-32282 since 03/11/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 305649 (Linux Distros Unpatched Vulnerability : CVE-2026-32282), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.25.9 or 1.26.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (305649) and CERT Bund (WID-SEC-2026-1006). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Red Hat Ansible Automation Platform
• Google Container-Optimized OS
• Amazon Linux 2
• Red Hat Enterprise Linux
• SUSE Linux
• Oracle Linux
• Red Hat OpenShift
• SUSE openSUSE
• RESF Rocky Linux
• Red Hat OpenStack
• Microsoft Azure Linux
• Golang Go
• Open Source CoreDNS
• IBM Business Automation Workflow
• Open Source Fleet
• Splunk Splunk Enterprise

Productinfo

Type

• Operating System

Name

• syscall-unix

Version

• 1.25.0
• 1.25.1
• 1.25.2
• 1.25.3
• 1.25.4
• 1.25.5
• 1.25.6
• 1.25.7
• 1.25.8
• 1.26.0
• 1.26.1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion