A vulnerability has been found in OpenBMB XAgent up to 1.0.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /conv/community. The manipulation leads to path traversal.
This vulnerability is known as CVE-2025-6281. The attack needs to be approached within the local network. Furthermore, there is an exploit available.
A vulnerability, which was classified as critical, was found in TransformerOptimus SuperAGI up to 0.0.14. Affected is the function download_attachment of the file SuperAGI/superagi/helper/read_email.py of the component EmailToolKit. The manipulation of the argument filename leads to path traversal.
This vulnerability is traded as CVE-2025-6280. Access to the local network is required for this attack to succeed. Furthermore, there is an exploit available.
A vulnerability, which was classified as critical, has been found in Upsonic up to 0.55.6. This issue affects the function cloudpickle.loads of the file /tools/add_tool of the component Pickle Handler. The manipulation leads to deserialization.
The identification of this vulnerability is CVE-2025-6279. Access to the local network is required for this attack. Furthermore, there is an exploit available.
A vulnerability classified as critical was found in Upsonic up to 0.55.6. This vulnerability affects the function os.path.join of the file markdown/server.py. The manipulation of the argument file.filename leads to path traversal.
This vulnerability was named CVE-2025-6278. The attack needs to be initiated within the local network. Furthermore, there is an exploit available.
A vulnerability classified as critical has been found in Brilliance Golden Link Secondary System up to 20250609. This affects an unknown part of the file /storagework/custTakeInfoPage.htm. The manipulation of the argument custTradeName leads to sql injection.
This vulnerability is uniquely identified as CVE-2025-6277. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
A vulnerability was found in Brilliance Golden Link Secondary System up to 20250609. It has been rated as critical. Affected by this issue is some unknown functionality of the file /storagework/rentTakeInfoPage.htm. The manipulation of the argument custTradeName leads to sql injection.
This vulnerability is handled as CVE-2025-6276. The attack may be launched remotely. Furthermore, there is an exploit available.
A vulnerability was found in WebAssembly wabt up to 1.0.37. It has been declared as problematic. Affected by this vulnerability is the function GetFuncOffset of the file src/interp/binary-reader-interp.cc. The manipulation leads to use after free.
This vulnerability is known as CVE-2025-6275. It is possible to launch the attack on the local host. Furthermore, there is an exploit available.
A similar issue reported during the same timeframe was disputed by the code maintainer because it might not affect "real world wasm programs". Therefore, this entry might get disputed as well in the future.
A vulnerability was found in WebAssembly wabt up to 1.0.37. It has been classified as problematic. Affected is the function OnDataCount of the file src/interp/binary-reader-interp.cc. The manipulation leads to resource consumption.
This vulnerability is traded as CVE-2025-6274. Attacking locally is a requirement. Furthermore, there is an exploit available.
A similar issue reported during the same timeframe was disputed by the code maintainer because it might not affect "real world wasm programs". Therefore, this entry might get disputed as well in the future.
A vulnerability was found in WebAssembly wabt up to 1.0.37 and classified as problematic. This issue affects the function LogOpcode of the file src/binary-reader-objdump.cc. The manipulation leads to reachable assertion.
The identification of this vulnerability is CVE-2025-6273. Local access is required to approach this attack. Furthermore, there is an exploit available.
The real existence of this vulnerability is still doubted at the moment.
The code maintainer explains that this issue might not affect "real world wasm programs".