The Somatic Framework WordPress plugin through 1.8.14 does not perform an authorization check or validate a user-supplied file path before deleting it, allowing any authenticated user, such as a subscriber, to delete arbitrary files on the server, which can lead to a full site takeover.
A vulnerability in Golang 1.10 and certain related versions causes HTTP/1 servers using MaxBytesReader or MaxBytesHandler to potentially crash due to a race condition. When the MaxBytesReader's limit is exceeded, the "Connection: close" header is set automatically without synchronization, which may conflict with other headers set explicitly by the server handler. This race condition can lead to a runtime panic if the request body is read concurrently with writing the response header.
A vulnerability in golang-1.10 allows a malicious package using cgo to bypass "#cgo LDFLAGS" validation, potentially causing unexpected code execution at build time or causing the go command to panic. This occurs due to improper handling of quoting and escaping in "//go:cgo_ldflag" directives, allowing disallowed linker flags or unvalidated linker search paths to be passed to the external linker. The issue also includes a panic caused by an out-of-bounds slice index during LDFLAGS deduplication. The golang tools have been updated to properly handle backslash-escaped quotes and unquote pragma strings, and the slice bounds check has been fixed.
A vulnerability in Golang 1.10 and several related versions allows a malicious package using "//go:cgo_import_dynamic" directives or linking against crafted PE objects on Windows to pass unsafe library arguments to the external linker. The issue arises because the compiler and linker did not fully validate library names, allowing path traversal and special characters that could reference arbitrary files on disk. This flaw has been addressed by stricter validation rejecting unsafe characters and path traversal sequences.
A vulnerability in Golang 1.10 allows a malicious package containing "//go:cgo_*" compiler directives to inject arbitrary flags into the external linker invocation on ELF platforms. This occurs because the compiler and linker did not reject commas in certain cgo directives, enabling crafted inputs to split linker flags and inject arbitrary arguments. Additionally, the two-argument form of "//go:cgo_import_dynamic" could overwrite external symbol names of symbols marked for cgo export. These issues have been addressed by rejecting commas in these directives, changing how the linker passes dynamic linker paths, and preventing symbol overwrites.
A vulnerability in Golang 1.10 allows a crafted ".syso" file to bypass cgo flag validation, enabling injection of arbitrary linker flags during linking. This occurs because the linker incorrectly parses certain ".syso" files as Go compiler objects, passing untrusted cgo metadata to the external linker without proper validation. Additionally, long ".syso" filenames lose their extension when truncated, causing further issues. The linker has been updated to reject unrecognized ".syso" formats and preserve the ".syso" suffix in archive headers.
A vulnerability in Golang 1.10 allows a malicious package using "#cgo pkg-config:" directives to load untrusted pkg-config ".pc" files or inject unvalidated compiler and linker flags. This occurs because the previous pkg-config flag allowlist permitted unsafe flags and local ".pc" paths, enabling potential path rewriting and unsafe linking. The issue is addressed by disallowing certain flags and inspecting cgoCPPFLAGS for internal linking safety.
A vulnerability in Golang 1.10 and certain related versions allows a malicious package containing ".syso" files or cgo linker inputs to inject arbitrary linker flags or execute code at link time. This occurs because linker input files were passed to the external linker without proper validation, enabling execution of disguised linker scripts or injection of unallowlisted linker flags. The go command has been updated to validate these inputs and disallow risky linker flags.
A vulnerability in Golang 1.10 and certain related versions allows arbitrary code execution at link time when building malicious packages that use cgo. This occurs due to improper handling of linker script files passed via "#cgo LDFLAGS" and certain linker flags that can be interpreted as linker scripts by GNU ld.bfd. The issue arises from accepting bare second arguments to split "-Wl," flags and improper validation of these flags. The Go command has been updated to require proper "-Wl," prefixes, verify flags do not reference linker scripts, and disallow certain unsafe flags.
On Darwin (macOS), Golang 1.10 and certain related versions contain a vulnerability where building a malicious package using cgo with specific linker flags can lead to arbitrary code execution. This occurs because the Apple linker recombines separated "-l" and "to_library" arguments into a single flag that loads an arbitrary LTO plugin dynamic library at link time. The Go command has been updated to disallow these dangerous linker flags and patterns to prevent exploitation.
A vulnerability in Golang 1.10 and related versions allows unexpected code execution or arbitrary file writes during build time when using Clang or GCC compilers with malicious packages that use cgo. This occurs due to improper handling of certain compiler and linker flags (-gen-* and -gnat*) in #cgo directives, which could be exploited to write files to arbitrary directories or cause desynchronized flag parsing. The flags -gen-* and -gnat* are now disallowed in #cgo compiler and linker flags to mitigate this issue.
Golang 1.10 and certain related versions have a vulnerability when using GCC to build malicious packages that use cgo. This can lead to arbitrary command execution at link time via untrusted GCC spec files. The vulnerability arises when linking with specific flags that cause GCC to evaluate spec files from directories that may be untrusted. The go command has been updated to reject certain directories containing GCC spec files and disallows specific compiler flag prefixes to mitigate this risk.
A vulnerability in Golang 1.10 allows arbitrary code execution at build time when building malicious packages that use cgo. This is due to unsafe compiler and linker flags permitted in "#cgo" directives, such as "--sysroot" and "-target", which can be exploited to execute attacker-controlled code. The Golang project has restricted these flags and imposed validations to mitigate the issue.
OpenSearch Dashboards versions 2.14.0 through 2.19.5 and 3.0.0 through 3.6.9 contain a Server-Side Request Forgery (SSRF) vulnerability in the fetchDataSourceMetaData route. This route does not validate endpoint URLs against configured deny or allow lists, unlike the sibling test_connection route. An authenticated user can exploit this to probe internal or loopback network resources. The vulnerability is fixed in versions 2.19.6 and 3.7.0.
A security vulnerability identified as CVE-2026-41988 affects the argo-workflows package, specifically versions before 4.1.6-r1 and 4.0.15-r2. The issue relates to the uuid component before version 14. The vulnerability has a low severity score and does not impact confidentiality or availability but may cause limited integrity issues. Fixed versions 4.1.6-r1 and 4.0.15-r2 are available.
A moderate severity security update for the gcc compiler addresses multiple vulnerabilities including an integer wrap and confirmed out-of-bounds read/write in libstdc++ parallel std, a stack overflow in std::bitset, and an out-of-bounds read in std::from_chars. These issues affect the gcc packages providing compilers for various languages and related support libraries. The vulnerabilities are fixed in version 14.4.1-5.el10_3.alma.3.
Multiple security issues were addressed in the xwayland-24.1.14-2.1 package included in the GA media of openSUSE Tumbleweed. These fixes resolve vulnerabilities present in prior versions of the xwayland component.
A denial of service vulnerability exists in Microsoft.AspNetCore.WebUtilities versions 2.3.0 through 2.3.13. The issue arises from the FileBufferingReadStream buffer allocation, which can allow unauthenticated multipart-form requests to exhaust memory. This vulnerability has a CVSS 3.1 base score of 7.5 (high severity). A fixed version 2.3.14 is available to address this issue.
An origin validation error vulnerability exists in Fortinet FortiClientMac versions 7.4.0 through 7.4.7, FortiClientWindows versions 7.4.0 through 7.4.7 and 7.2.0 through 7.2.14, and FortiClientWindowsPAM versions 7.4.7 and 7.2.14. This flaw may allow an unauthorized remote attacker to execute unauthorized code or commands if the victim interacts with malicious content. The vulnerability has a high severity score of 9.6 CVSS v3.1, indicating critical impact on confidentiality, integrity, and availability.