BITTER is a cyberespionage group targeting South Asian government, energy, and engineering sectors using a custom remote access trojan called PapRAT. PapRAT is deployed through multiple infection chains involving malicious LNK files, VHDX disk images with MSI installers, and URL shortcuts combined with WebDAV. The malware exists in C++ and Rust variants, with capabilities such as command execution, file and directory manipulation, screenshot capture, and secondary payload delivery. Persistence is maintained via scheduled tasks, and communication with command-and-control servers occurs over HTTP. The Rust variant adds enhanced features including PowerShell execution and sleep commands.
Over 100 stores across multiple European countries experienced cyberattacks targeting internet-exposed refrigeration controllers, causing fridges and freezers to heat up and spoil food. The attacks affected stores in Belgium, Sweden, Ireland, and other countries, with some units set as high as 50°C. The incidents resemble a prior wave of attacks in France that disrupted around 700 supermarkets. The compromised devices include legacy Danfoss and Copeland refrigeration controllers, many of which have management interfaces exposed to the internet and lack available patches. The attackers exploited default credentials and internet exposure to force refrigeration units into defrost mode. Physical modifications alongside software updates are needed to fully mitigate the vulnerability. Investigations are ongoing, and no group has claimed responsibility.
Kvazaar versions up to 2.3.2 have an infinite loop vulnerability in the read_header() function caused by a truncated Y4M header missing a terminating newline. This flaw allows attackers to hang the command-line encoder indefinitely by supplying a crafted .y4m file, resulting in high CPU usage.
The FBI has attributed the $6 billion Binance cryptocurrency heist to North Korea’s state-sponsored hacking group TraderTraitor. The attackers compromised Binance’s infrastructure, including multiple breach points beyond an initially suspected compromised laptop, and rapidly emptied hot wallets across multiple blockchains. The stolen funds are being laundered primarily into Ethereum and then through decentralized finance (DeFi) and instant swap services. The FBI has identified over 600 cryptocurrency addresses linked to the theft and is coordinating with industry partners to block transactions from these addresses. Binance has pledged to cover all losses and has already replaced about 95% of the stolen funds using company resources. The laundering activity appears to be highly automated, with continuous fund movements across numerous addresses and chains.
CVE-2026-120344 is a critical OS command injection vulnerability in the WAVLINK WN551X3-A device, specifically in the system function of /bin/ioos within the WireGuard CLI Group Handler component. The vulnerability allows remote attackers to manipulate the group_name argument, leading to command injection. Public exploit code has been disclosed. No patch or fixed versions are currently indicated.
CVE-2026-120277 is a critical OS command injection vulnerability in the WAVLINK WN536AX6-A device firmware version V260507_2.0.0. The flaw exists in the WireGuard CLI Group Handler component, specifically in the function sub_41a1d8 within /bin/ioos, where manipulation of the group_name argument allows remote attackers to execute arbitrary OS commands. Public exploit code has been disclosed, increasing the risk of exploitation. No patch or fixed version information is currently available.
A critical vulnerability (CVE-2026-120240) exists in WAVLINK WN553X1-B firmware version V260403_2.0.0, specifically in the WireGuard CLI Group Handler component. The flaw is in the function sub_41A748 within /bin/ioos, where manipulation of the group_id or group_name arguments can lead to OS command injection. This vulnerability is remotely exploitable and has a very high severity score of 9.9. Public exploit code has been disclosed, though no known exploitation in the wild is reported. The vendor was notified early about this issue. No patch or remediation information is currently available.
CVE-2026-117635 is an improper access control vulnerability in Gitea affecting the /api/v1/admin route group. Public-only personal access tokens with admin scope issued by site administrators could bypass restrictions and perform unauthorized actions such as listing private organizations, accessing user email addresses, creating organizations, obtaining runner registration tokens, and creating persistent site administrator accounts. This vulnerability affects Gitea versions prior to 28.3.0 and has been fixed in version 28.3.0.
imagecodecs versions 2026.3.6 through 2026.10.10 contain an infinite loop vulnerability in the ccitt_fax4_decode_size() function. This flaw allows attackers to cause a denial of service by supplying a crafted CCITT Group 4 stream that lacks an End Of Facsimile Block (EOFB), causing the decoding process to hang and consume full CPU until terminated.
The BuddyBoss Platform WordPress plugin is affected by a stored cross-site scripting (XSS) vulnerability in the Group Name field. This vulnerability exists in all versions up to and including 3.6.0 and allows authenticated users with subscriber-level access or higher to inject malicious scripts. Exploitation requires the default setting that enables social group creation by all members; if group creation is restricted to administrators, exploitation is not possible.
The PHP2Shell vulnerability involves critical PHP flaws (CVE-2026-109618 and CVE-2026-109619) that have been actively exploited for over a week. Attackers, notably a China-linked group, have successfully chained these PHP2Shell flaws with the Fragnesia Linux kernel privilege escalation bug to gain root access on Palo Alto Networks PAN-OS firewalls. Despite over 22.6 million exposed PHP instances potentially vulnerable, successful exploitation has been limited, with WordPress sites remaining largely unaffected. Palo Alto Networks has released patches for multiple PAN-OS versions and urges customers to restrict internet access to management interfaces. The attacks appear opportunistic and originate from a small number of IP addresses, targeting various sectors including healthcare and technology.
This vulnerability allows a member of the Veeam Virtualization Extensions Users group to execute remote code on servers running the Veeam Management Pack for Microsoft System Center Collector service. It is identified as CVE-2026-107239 with a high severity score of 8.8. The vulnerability involves a path traversal issue (CWE-23) that could lead to remote code execution. No affected versions or patch information are provided, and there are no known exploits in the wild at this time.
A vulnerability in the filelock library versions 3.22.0 through 4.2.0 allows a local user with write access to a lock marker file (but without permission to remove it) to forge the process ID recorded in the marker. This causes the lock to be incorrectly judged stale, enabling another process running as the lock owner or root to remove the live marker and acquire the lock simultaneously. This results in two processes concurrently entering a critical section without error notification. The issue requires specific filesystem permissions and directory configurations, such as group or other write bits on the marker and a sticky or non-removable directory. The vulnerability is fixed in version 2.19.0_2.
A symlink swap vulnerability in the SoftFileLock implementation of the filelock library (versions 3.32.6 through 4.2.0) allows a local user with write access to the lock directory to leak one bit of information about whether a target path exists and is writable by the lock user. The vulnerability arises from a time-of-check to time-of-use (TOCTOU) race condition during writability checks that follow symlinks. This leak is mitigated on Linux by the fs.protected_symlinks kernel setting in sticky world-writable directories like /tmp, but not in non-sticky or group-writable directories. The vulnerability has a low CVSS score of 2.5 due to its local scope, high attack complexity, and limited confidentiality impact. A fix is available in version 0.32.2_1.
A vulnerability in filelock's ReadWriteLock and AsyncReadWriteLock components allows a local user with write permissions to the directory containing the SQLite lock database to manipulate symlinks or journal files. This manipulation can cause the lock user’s SQLite-backed lock to write arbitrary data into their own files, create or unlink files, or cause lock acquisition failures. The issue affects filelock versions from 3.20.4 through 4.2.0, with the fixed version being 1.79.0_1. The vulnerability requires a writable directory without the sticky bit, such as a 0777 or group-writable directory, and is limited to local users on the same host. The CVSS 3.1 score is 7.1 (High), reflecting high integrity and availability impacts but no confidentiality impact.