Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows
Summary
| CVE | CVE-2026-39824 |
|---|---|
| State | PUBLISHED |
| Assigner | Go |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-22 20:16:33 UTC |
| Updated | 2026-05-27 14:16:46 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 3.3 LOW from ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS: 0.000130000 probability, percentile 0.024140000 (date 2026-05-31)
Problem Types: CWE-190 | CWE-190: Integer Overflow or Wraparound | CWE-190 CWE-190 Integer Overflow or Wraparound
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | ADP | DECLARED | 3.3 | LOW | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 3.3 | LOW | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
LowAvailability
NoneCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Golang.orgxsys | Golang.org/x/sys/windows | affected 0.44.0 semver | windows |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| pkg.go.dev/vuln/GO-2026-5024 | [email protected] | pkg.go.dev | |
| go.dev/cl/770080 | [email protected] | go.dev | |
| groups.google.com/g/golang-announce/c/6MMI8Lj-Atg | [email protected] | groups.google.com | |
| go.dev/issue/78916 | [email protected] | go.dev | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.