golang.org/x/sys
Activity
- Latest release
- 1w ago
- Total releases
- 21
- Cadence
- ~28 days
- Last 12 months
- 12
Details
- First release
- Dec 03, 2024
| Version | Released | |
|---|---|---|
v0.48.0
minor
|
v0.48.0
minor
|
|
v0.47.0
minor
|
v0.47.0
minor
|
|
v0.46.0
minor
|
v0.46.0
minor
|
|
v0.45.0
minor
|
v0.45.0
minor
|
|
v0.44.0
minor
|
v0.44.0
minor
|
|
v0.43.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.43.0
minor
|
|
v0.42.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.42.0
minor
|
|
v0.41.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.41.0
minor
|
|
v0.40.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.40.0
minor
|
|
v0.39.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.39.0
minor
|
|
v0.38.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.38.0
minor
|
|
v0.37.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.37.0
minor
|
|
v0.36.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.36.0
minor
|
|
v0.35.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.35.0
minor
|
|
v0.34.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.34.0
minor
|
|
v0.33.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.33.0
minor
|
|
v0.32.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.32.0
minor
|
|
v0.31.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.31.0
minor
|
|
v0.30.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.30.0
minor
|
|
v0.29.0
minor
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.29.0
minor
|
|
v0.28.0
initial
1 CVE
CVE-2026-39824
GO-2026-5024
May 22, 2026
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows 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. Fixed in
0.44.0
References Updated Jun 09, 2026 · Source: OSV.dev |
v0.28.0
initial
|