Where
AND
AND
-Infinity
0
Severity
9.1
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

A flaw was found in the elliptic package of the crypto library in golang when the IsOnCurve function could return true for invalid field elements. This flaw allows an attacker to take advantage of this undefined behavior, affecting the availability and integrity of the resource.

1 / 4
First published (updated )
Severity
9.8
Buffer Overflow, Input Validation
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

A flaw was found in golang. This vulnerability can only be triggered when invoking functions from vulnerable WASM (WebAssembly) Modules. Go can be compiled to WASM. If the product or service doesn't use WASM functions, it is not affected, although it uses golang.

1 / 4
First published (updated )
Severity
9.6
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

IBM QRadar SIEM could allow an unauthenticated user in the environment to obtain highly sensitive information in configuration files.

1 / 2
Source: IBM

Remedy

IBM strongly encourages customers to update their systems promptly. Please upgrade to at least version 1.11.3.0 according to the following instructions: https://www.ibm.com/docs/en/cloud-paks/cp-security/1.11?topic=installing https://www.ibm.com/docs/en/cloud-paks/cp-security/1.11?topic=upgrading
First published (updated )
Severity
10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

robinweser fast-loops could allow a remote attacker to execute arbitrary code on the system, caused by a prototype pollution in the function objectMergeDeep. By sending a specially crafted request, an attacker could exploit this vulnerability to execute arbitrary code or cause a denial of service.

1 / 3
Source: IBM
First published (updated )
Severity
9.8
Code Injection, Input Validation
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

An input validation vulnerability was found in Go. From a generated go file (from the cgo tool), it is possible to modify symbols within that object file and specify code. This flaw allows an attacker to create a repository that includes malicious pre-built object files that could execute arbitrary code when downloaded and run via go get or go build while building a Go project. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

1 / 4

Remedy

If it's possible to confirm that the Go project being built does not rely on any cgo code in the included dependencies, the env variable CGO_ENABLED=0 can be specified when using either `go get` or `go build`. For example: CGO_ENABLED=0 go get github.com/someproject This will not stop the files being downloaded but will stop any automatic complication of the cgo code, including inlined in the go file and separate .c files. Of course, this will only be effective if cgo is not relied upon in a given dependency and may not be appropriate in all scenarios.
First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203