GoApplication · Golang
CVE-2026-39822
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOn Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a symbolic link and the path ends in /. For example, 'root.Open("symlink/")' will open "symlink" even when "symlink" is a symbolic link pointing outside of the root.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGo's os.Root implementation on Unix systems improperly follows symbolic links when the final path component is a symlink and the path ends with a trailing slash. This allows root directory escapes where root.Open('symlink/') opens the target of the symlink even when it points outside the defined root, bypassing the security boundary os.Root is intended to enforce.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GoApplication
< 1.25.12>= 1.26.0, < 1.26.5= 1.27CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Go versionRun 'go version' to get the Go runtime versionAffected if Version is < 1.25.12, >= 1.26.0 and < 1.26.5, or exactly 1.27
-
Identify os.Root usage in codebaseSearch source code for usages of os.Root such as os.Root.Open() or root.Open() where root is an os.Root valueAffected if Code uses os.Root to open paths on Unix systems
-
Find paths with trailing slashes in os.Root callsReview os.Root usage to identify if any paths passed to root.Open() or similar methods end with a trailing slash (/)Affected if Any os.Root operations use paths that end with /
-
Check for symlink involvement in target pathsInspect the filesystem paths used with os.Root to determine if the final component could be or become a symbolic linkAffected if The paths used with os.Root could involve symlinks in their final component when combined with trailing slashes
You are affected if your Go version is within the affected ranges AND your code uses os.Root on Unix with paths that end in a trailing slash where the final component is a symbolic link.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.25.121.26.5
Avoid using trailing slashes with paths ending in symlinks when using os.Root, or wait for an official Go patch that fixes this path traversal issue.
Go 1.25.12 (or later 1.25.x), Go 1.26.5 (or later 1.26.x), or Go 1.28 (or later 1.27.x)
- Check current Go version by running: go version
- Determine which upgrade path applies based on your current version: if < 1.25.12, upgrade to 1.25.12 or later; if >= 1.26.0 and < 1.26.5, upgrade to 1.26.5 or later; if using 1.27.x, upgrade to 1.28 or later
- Download the appropriate Go version from https://go.dev/dl/
- Install the new version following standard Go installation procedures for your operating system
- Verify the upgrade was successful by running: go version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39822 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data