Vulnerability in stdlib (CVE-2026-32282)
Summary
Vulnerability in stdlib (CVE-2026-32282). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.25.9, 1.26.2 or later.
Original description
The description as published by the source.
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.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32282 has been found in stdlib.
Successful exploitation can lead to full system takeover. CVSS score: 6.4/10.
What to do: upgrade stdlib to 1.25.9, 1.26.2 or later.
If unsure, ask your IT team or search "stdlib CVE-2026-32282" on the vendor's site.
CVE-2026-32282 (stdlib) — CWE-59 / CVSS v3 6.4
Attack vector: local / no user interaction
Patched: 1.25.9, 1.26.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in stdlib.
Check the vendor advisory for the affected versions of stdlib.
Severity: Medium (CVSS 6.4/10). Successful exploitation can lead to full system takeover.
Update to 1.25.9, 1.26.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'stdlib' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'stdlib' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
stdlibを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade stdlib to 1.25.9, 1.26.2ステージング環境で 1.25.9, 1.26.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-32282 golang-1.15
- Ubuntu UBUNTU-CVE-2026-32282 golang-1.10
References
- advisory nvd.nist.gov
- advisory github.com
- web go.dev
- web go.dev
- web groups.google.com
- web pkg.go.dev
- web pkg.go.dev