CVE-2026-32282: On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chm

Routine

MEDIUM 6.4WATCHLISTUPGRADE

CVE-2026-32282 is a medium-severity flaw (CVSS 6.4) affecting go. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 impac

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-59
Published	2026-04-08
Last modified	2026-07-25

Publisher (CNA): Go Project · Vendor: golang

Last updated 2026-07-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-08 02:16 UTCPublished CVE record published
2026-07-25 10:10 UTCUpdated Record last modified

golang go UPGRADE

Affected: < 1.25.9 · >= 1.26.0 and < 1.26.2

Fixed in: 1.25.9, 1.26.2

Safe to downgrade to: a release before 1.26.0

1. Check installed version

apt-cache policy go || rpm -q go || go --version

2. UPGRADE to 1.25.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade go

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade go

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.26.0 (Debian / Ubuntu)

apt-cache madison go sudo apt install go=<VERSION_BEFORE_1.26.0> sudo apt-mark hold go

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list go sudo dnf downgrade go-<VERSION_BEFORE_1.26.0> sudo dnf versionlock add go

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32282?

go: upgrade to 1.25.9, 1.26.2. Exact commands for each OS are on this page.

Is CVE-2026-32282 being exploited?

CVE-2026-32282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32282 affect?

CVE-2026-32282 affects go. Severity is medium (CVSS 6.4). 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 ignor

How urgent is CVE-2026-32282?

Priority 33/100. On your watchlist

Software pages

Go (Golang) vulnerabilities

Related CVEs

CVE-2026-33814 HIGH 7.5 UPGRADE UPGRADE When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames i
CVE-2026-39836 HIGH 7.5 UPGRADE The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0).
CVE-2026-39825 MEDIUM 5.3 UPGRADE ReverseProxy can forward queries containing parameters not visible to Rewrite functions
CVE-2026-39826 MEDIUM 6.1 UPGRADE If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' att
CVE-2026-39823 MEDIUM 6.1 UPGRADE CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <conten

References

← Back to latest CVEs