Cyber Resilience

CVE-2026-32282

Golang Go ≤ 1.25.9

Published
08 April 2026
Modified
25 July 2026
Patch / advisory
CVSS Score v3.1 6.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-32282 is a medium-severity Link Following (CWE-59) vulnerability in Golang Go. Its CVSS base score is 6.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1222.002 Linux and Mac Permissions Defense Impairment
Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.
Why these techniques?

TOCTOU symlink race in privileged Root.Chmod allows unauthorized permission changes outside intended root (T1222.002) and can be directly leveraged for local privilege escalation (T1068).

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-39819Same product: Golang Go
CVE-2026-27144Same product: Golang Go
CVE-2026-27143Same product: Golang Go
CVE-2026-27139Same product: Golang Go
CVE-2025-47906Same product: Golang Go
CVE-2026-27142Same product: Golang Go
CVE-2026-39825Same product: Golang Go
CVE-2023-24537Same product: Golang Go
CVE-2023-24532Same product: Golang Go
CVE-2026-33810Same product: Golang Go

Affected Assets

golang
go
≤ 1.25.9 · 1.26.0 — 1.26.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • SI-10 Information Input Validation
  • SI-7 Software, Firmware, and Information Integrity
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces that Root.Chmod must not allow symlink traversal outside the intended root directory.

prevent

Requires validation of file paths and symlink targets to block TOCTOU replacement attacks before chmod is performed.

preventdetect

Protects integrity of file operations by detecting or blocking unauthorized modifications via symlink races.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect link-following flaws before release.

prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

prevents

Secure architecture principles include input validation and safe file-access design patterns.

prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References