In October alone, the suspected Russia-based group added more than 185 victims to its leak site — claiming to be behind recent cybersecurity incidents at Japanese beverage giant Asahi, the Texas city of Sugar Land, a county government in North Carolina and multiple power companies in Texas.
A vulnerability marked as problematic has been reported in BESSystem BES Application Server up to 9.5.x. This affects an unknown function of the file bes-web.xml. Performing manipulation results in information disclosure.
This vulnerability is reported as CVE-2025-60805. The attacker must have access to the local network to execute the attack. No exploit exists.
A vulnerability labeled as problematic has been found in Clear2Pay Bank Visibility Application 1.10.0.104. The impacted element is an unknown function. Such manipulation of the argument ID leads to cross site scripting.
This vulnerability is documented as CVE-2025-61080. The attack can be executed remotely. There is not any exploit available.
A vulnerability identified as problematic has been detected in zhangyd-c OneBlog up to 2.3.8. The affected element is an unknown function of the component FreeMarker Template Handler. This manipulation causes improper neutralization of special elements used in a template engine.
This vulnerability is registered as CVE-2025-60355. The attack requires access to the local network. No exploit is available.
You should upgrade the affected component.
A vulnerability categorized as critical has been discovered in blog-vue-springboot. Impacted is an unknown function. The manipulation results in improper authorization.
This vulnerability is cataloged as CVE-2025-60354. The attack must originate from the local network. There is no exploit available.
A vulnerability was found in jshERP. It has been rated as critical. This issue affects some unknown processing of the file /jshERP-boot/user/info of the component GET Request Handler. The manipulation leads to improper access controls.
This vulnerability is listed as CVE-2025-60800. The attack must be carried out from within the local network. There is no available exploit.
A vulnerability was found in Bitcoin Core up to 29.0. It has been declared as problematic. This vulnerability affects unknown code. Executing manipulation can lead to resource consumption.
This vulnerability is tracked as CVE-2025-54605. The attack is only possible within the local network. No exploit exists.
A vulnerability was found in Bitcoin Core up to 29.0. It has been classified as problematic. This affects an unknown part. Performing manipulation results in resource consumption.
This vulnerability is identified as CVE-2025-54604. The attack can only be performed from the local network. There is not any exploit available.
A vulnerability was found in Hotta Studio 7.23.4.7 and classified as critical. Affected by this issue is some unknown functionality in the library GameDriverX64.sys of the component IOCTL Handler. Such manipulation leads to denial of service.
This vulnerability is referenced as CVE-2025-61155. The attack can only be performed from a local environment. No exploit is available.
A vulnerability has been found in Prevx 3.0.5.220 and classified as problematic. Affected by this vulnerability is an unknown functionality in the library pxscan.sys of the component IOCTL Handler. This manipulation causes denial of service.
The identification of this vulnerability is CVE-2025-60349. The attack needs to be done within the local network. There is no exploit available.
A vulnerability, which was classified as problematic, was found in Wazuh File Integrity Monitoring. Affected is an unknown function. The manipulation results in time-of-check time-of-use.
This vulnerability was named CVE-2025-34294. The attack needs to be approached locally. There is no available exploit.
It is best practice to apply a patch to resolve this issue.
A vulnerability, which was classified as problematic, has been found in Reolink Video Doorbell Wi-Fi DB_566128M5MP_W. This impacts an unknown function of the component DDNS Handler. The manipulation leads to information disclosure.
This vulnerability is uniquely identified as CVE-2025-60858. Local access is required to approach this attack. No exploit exists.
A vulnerability classified as very critical was found in IBM Maximo Application Suite up to 9.0.15/9.1.4. This affects an unknown function. Executing manipulation can lead to authentication bypass by primary weakness.
This vulnerability is handled as CVE-2025-36386. The attack can be executed remotely. There is not any exploit available.
Upgrading the affected component is advised.