CVE-2026-39824 json
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows
published 2026-05-22 5 mo ago modified 2026-07-23 3 mo ago also GO-2026-5024 , EUVD-2026-31498
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go golang.org/x/sys 0.44.0
- golang.org/x/sys golang.org/x/sys/windows 0.44.0
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- keybase-client openSUSE Leap 16.0 6.6.3-bp160.2.1
- rclone openSUSE Leap 16.0 1.74.4-bp160.1.1
- keybase-client openSUSE Tumbleweed 6.6.3-3.1
- rclone openSUSE Tumbleweed 1.74.2-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:21492-1openSUSE-SU-2026:21436-1openSUSE-SU-2026:11306-1openSUSE-SU-2026:10856-1
- go.dev/cl/770080 patch
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | golang.org/x/sys | <0.44.0 |
0.44.0 |
Affected products
- golang.org/x/sys golang.org/x/sys/windows
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
Sources
- CVE List CVE-2026-39824
- NVD CVE-2026-39824
- OSV GO-2026-5024
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.