GO-2026-5024

NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.

Low highest severity reported · also known as CVE-2026-39824

12
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.1%
EPSS for CVE-2026-39824, percentile 1

Catalog tools matching GO-2026-5024

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
tracee
Container Security › Runtime Security
v0.24.1golang.org/x/sys@v0.31.0
golang
0.44.0vulnerable code not in binaryapi/go.modDispute
tracee
Container Security › Runtime Security
v0.24.1golang.org/x/sys@v0.33.0
golang
0.44.0vulnerable code not in binarycommon/go.modDispute
tracee
Container Security › Runtime Security
v0.24.1golang.org/x/sys@v0.34.0
golang
0.44.0vulnerable code not in binarygo.modDispute
kics
Infrastructure as Code Security
v2.2.0golang.org/x/sys@v0.12.0
golang
0.44.0not analyzed.github/scripts/report/go.modDispute
bomber
Software Composition Analysis (SCA)
v0.5.1golang.org/x/sys@v0.25.0
golang
0.44.0vulnerable code not in binarygo.modDispute
gitleaks
Pre-commit & Secrets Detection
v8.30.1golang.org/x/sys@v0.30.0
golang
0.44.0vulnerable code not in binarygo.modDispute
govulncheck
Static Application Security Testing (SAST) › Language-specific › Go
v1.1.4golang.org/x/sys@v0.29.0
golang
0.44.0not analyzedgo.modDispute
dockle
Container Security › Image Scanning
v0.4.15golang.org/x/sys@v0.28.0
golang
0.44.0vulnerable code not in binarygo.modDispute
notation
Artifact Signing & Verification
v1.3.2golang.org/x/sys@v0.32.0
golang
0.44.0vulnerable code not in binarygo.modDispute
clair
Container Security › Image Scanning
v4.9.0golang.org/x/sys@v0.39.0
golang
0.44.0vulnerable code not in binarygo.modDispute
slsa-verifier
Supply Chain Compliance
v2.7.1golang.org/x/sys@v0.31.0
golang
0.44.0vulnerable code not in binarygo.modDispute
kube-linter
Kubernetes Security
v0.8.3golang.org/x/sys@v0.40.0
golang
0.44.0vulnerable code not in binarygo.modDispute
kube-linter
Kubernetes Security
v0.8.3golang.org/x/sys@v0.41.0
golang
0.44.0vulnerable code not in binarytool-imports/go.modDispute
talisman
Pre-commit & Secrets Detection
v1.37.0golang.org/x/sys@v0.30.0
golang
0.44.0vulnerable code not in binarygo.modDispute
dive
Container Security › Image Scanning
v0.13.1golang.org/x/sys@v0.31.0
golang
0.44.0vulnerable code not in binarygo.modDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

Go vulnerability GO-2026-5024 · NVD CVE-2026-39824 · OSV GO-2026-5024

Grype data sources: https://go.dev/issue/78916