Nitori, a major Japanese furniture and home accessories retailer, discovered that an attacker accessed a system on its network and may have stolen 37.62 million customer records. The intrusion was detected on November 6, and the company blocked the unauthorized access. However, an investigation into the incident revealed that the attacker likely had access to the system since mid-October. Nitori, often called the “IKEA of Japan,” is a major furniture and home furnishings retailer that operates 879 stores in Japan and another 219 stores across China, South Korea, Taiwan, Thailand, Singapore, and Hong Kong. The firm has an annual revenue of $5.8 billion. According to the company's notification, the incident impacts individual customers, corporate members, and non-members who placed orders through official Nitori stores and online shops.
A critical authentication bypass vulnerability in Xen Orchestra is being actively exploited in attacks that could grant administrator privileges and allow takeover of XCP-ng virtualization hosts. Xen Orchestra is a web-based management platform developed by French software company Vates, used to manage XCP-ng virtualization environments, including virtual machines, hosts, and pools. The vulnerability, tracked as VSA-2026-062, affects Xen Orchestra and the Xen Orchestra Appliance (XOA) and allows remote attackers with network access to the management interface to bypass authentication using a specially crafted cookie. A CVE identifier and CVSS score have not been assigned yet. According to a Vates security advisory, the flaw stems from how Xen Orchestra processes authentication tokens sent through REST API requests.
SAP patched 35 vulnerabilities in its November 2026 security updates, including four maximum-severity issues affecting its NetWeaver, Web Dispatcher, and Gateway software. The company addressed memory corruption (CVE-2026-76964) and missing authentication (CVE-2026-120017) flaws in the NetWeaver Application Server ABAP's Internet Communication Manager and SAML2 Service Provider components. NetWeaver is the core app platform that underpins SAP's business software and handles application integration, authentication, user management, and data processing. The other two maximum severity vulnerabilities stem from a broken access control weakness (CVE-2026-89103) in SAP Gateway and a memory corruption issue (CVE-2026-89126) in SAP Web Dispatcher. Gateway is a core framework that enables external apps to securely connect to SAP backend systems, while Web Dispatcher (deployed in almost every enterprise SAP environment) is a specialized component that acts as a load balancer and reverse proxy for web requests entering an SAP system architecture.
Cybersecurity company Barracuda Networks warned that attackers have begun exploiting two recently patched Email Security Gateway (ESG) vulnerabilities that let them run commands with root privileges. Barracuda released security updates to address the two flaws (tracked as CVE-2026-116606 and CVE-2026-111560) one week ago. The first stems from an Email Security Gateway (ESG) authentication weakness that can be exploited to modify an appliance's global configuration, while the second lets unauthenticated attackers inject OS commands that execute with root privileges. Barracuda also said that successful attacks require access to the administrative user interface (Admin UI) of targeted devices and advised customers to restrict access to trusted internal networks and use appropriate network access controls to limit exposure.
Google has released emergency security updates to patch a new Chrome vulnerability exploited in zero-day attacks, the eighth such flaw since the start of the year. "Google is aware that an exploit for CVE-2026-125350 exists in the wild," the company said in a Monday security advisory. As Google explained, this flaw stems from a Use-After-Free (UAF) weakness in the XML component of the Google Chrome web browser, which occurs when the browser's XML parser processes data, deletes an object from the computer's memory, but fails to clear the pointer referencing that object. Attackers can exploit this high-severity memory corruption vulnerability when the browser later tries to use or read that "freed" memory space to manipulate the memory layout and execute malicious code. While Google has found evidence of attackers exploiting this zero-day bug in the wild, it has not shared additional details about these incidents.
At some point your security will fail. This isn’t pessimism. It’s not because your team and tools aren’t sophisticated enough. It’s the reason we have detections in the first place. And, it’s why once we accept that prevention has its limits, we arrive at an interdiction strategy: finding and disrupting what got in. After the alert The alert tells you something happened. However, gaining
An iMessage flaw could let a remote attacker join a group chat and receive its messages, Apple said yesterday, and it released updates to fix it. The updates also fix a separate iMessage flaw that could let someone added to a group access messages sent before they joined. As of today, other updates released yesterday for the iPhone XS, XS Max and XR, the iPad (7th generation) and some Apple
France blames Iran for supermarket fridge attacks. What’s known, what remains unclear, and how to secure exposed controllers. French Foreign Minister Jean-Noël Barrot said Iran’s Revolutionary Guard Corps was behind the attacks on supermarket fridges in France on 11 and 12 October. He said they hit 700 sites and raised refrigerator temperatures. Some stores threw away their entire stock of perishable food, and fires broke out in several. “France attributes destabilization and sabotage campaigns against French interests to the Islamic Republic of Iran (electronic and cyber center of the Islamic Revolutionary Guard Corps of Iran – IRGC-ECC).” reads the announcement published by French cybersecurity agency ANSSI. “Following its investigation, C4 is able to attribute these destructive actions to the Shahid Kaveh cyber-offensive unit, affiliated with the electronic and cyber center of the Islamic Revolutionary Guard Corps of Iran (IRGC-ECC): infrastructure characteristics, use of signing tools, relay of the attack by a propaganda organ linked to Shahid Kaveh, traces of the use of Persian in the attack infrastructure.” Foreign Minister Jean-Noël Barrot described the attack as “unprecedented in both its scale and its level of aggression” and called it the first major cyber sabotage operation on French soil. He promised EU-level sanctions, and France summoned the Iranian ambassador. EU foreign policy chief Kaja Kallas said the response should be strong, adding that she had only just learned about France’s attribution. “I can confirm that this attack was carried out by the Islamic Revolutionary Guard Corps of the Islamic Republic of Iran,” Foreign Minister Jean-Noël Barrot said of the cyberattacks on French supermarkets, which occurred on October 11 and 12, and reported Le Monde. “This attack is unprecedented in both its scale and its level of aggression,” said Barrot. “It marks the first large-scale cyberattack aimed at sabotage on our national territory, and it constitutes a major attack on the nation’s interests and the security of the French people.” “We will implement sanctions at the European level against all those responsible,” he added. Paris prosecutors opened a judicial investigation into the head of Shahid Kaveh, an offensive cyber unit tied to the Guards’ Electronic and Cyber Center, and his two deputies. Anyone else they identify can be added to the case. The attribution cites shared infrastructure, attack tools, Persian-language traces, and amplification by a group-linked propaganda outlet. French authorities say Iranian cyber operations targeting French interests date back to at least 2020. Previous incidents include a planned attack against Charlie Hebdo, a 2023 breach of its online store attributed to Emennet Pasargad, and a 2024 attempt to hijack digital advertising kiosks to display anti-Israel messages ahead of the Paris Olympics. C4 attributes these operations to the IRGC-linked Shahid Shoostari unit. France wasn’t alone. On 2 November, supermarkets in at least nine other European countries reported a suspected attack on their freezer systems. Barrot spoke only about the French case, so nothing official yet ties the second wave to Iran. This is where we need to be careful. When a government names a country as responsible for an attack, that’s a serious accusation. But the reports I’ve read don’t explain the technical evidence behind it. We should treat it as an official claim, not a proven fact, and stick to what we know. Fear and uncertainty can be used to spread distrust, and that risk applies to all sides involved in this story. The key issue isn’t just identifying the attackers, but understanding whether someone is exploiting these incidents to promote a hybrid warfare narrative. Hacktivist claims may serve propaganda and visibility more than reflect actual responsibility. If French investigations confirm Iran’s role in the October attacks, the pro-Russian groups claiming November’s incidents could face a serious credibility problem. They may have tried to take credit for someone else’s operations. Still, their involvement in some incidents remains possible. In today’s hybrid warfare, uncertain attribution, strategic ambiguity, and information manipulation make it increasingly difficult to separate real attacks from propaganda. The method used in supermarket fridge attacks, at least, is documented. On 5 November, CISA, the FBI and other US agencies published a fact sheet on the same kind of activity. The actors may exploit vulnerabilities or weaknesses in unpatched or internet-accessible controllers to remotely alter settings and force units into continuous heating and defrost cycles, which can cause widespread inventory loss and equipment hazards. The agencies list three ways in: bypassing authentication, injecting code and weak settings. They also warn that operators can lose sight of the real temperatures, which is a bad thing to discover after the cheese has gone. The fixes are dull and they work. Keep controllers off the internet, and if you need remote access, put an updated firewall in front of it. Separate industrial devices from the office network, change default passwords, add phishing-resistant multifactor authentication, patch firmware and replace devices the maker no longer supports. Then limit who can change settings with an allowlist of approved devices and IP addresses. Keep tested backups offsite and offline, turn on logging and read the logs. The last control is the cheapest: Define and maintain reasonable setpoint limits for devices operating downstream of controllers to stay within safe ranges and establish alerting for deviations. Follow me on Twitter: @securityaffairs and Facebook and Mastodon Pierluigi Paganini (SecurityAffairs – hacking, Iran)
Taiwanese vendor QNAP urges users to update Plex Media Server after reports of NAS compromises through the Plex2Shell vulnerability chain. QNAP urges users to update Plex Media Server through the QNAP App Center after reports that threat actors exploited the Plex2Shell vulnerability chain to compromise NAS devices. “QNAP has received reports from some users that Plex Media Server on their NAS appears to have been compromised through these vulnerabilities, and QNAP Technical Support is assisting the affected usersadvisory published by QNAP. ” reads the report published by the vendor. “The QNAP Product Security Incident Response Team (QNAP PSIRT) has confirmed that the vulnerabilities exist only in Plex Media Server; QTS, QuTS hero, and other QNAP operating systems are not themselves affected.” Plex Media Server is designed to make movies, music, and other media available across devices. But when a server is exposed to the internet and runs vulnerable software, it can become an entry point for attackers who have little interest in your film collection. On October 16, 2026, security researcher Zach Main published technical details and proof-of-concept (PoC) code for a vulnerability chain dubbed Plex2Shell. Within a day, researchers had observed attackers using the exploit against an internet-facing honeypot, deploying cryptocurrency-mining malware and proxy software. The incident is a reminder of how quickly a public exploit can be weaponized by threat actors. The chain combines four vulnerabilities in Plex Media Server: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656. Together, they can allow attackers to execute arbitrary code on vulnerable servers without valid credentials, provided the required conditions are met. The code runs with the privileges of the Plex service, giving attackers an opportunity to install additional software and abuse the host. The technical details are available in Main’s original analysis, Plex2Shell. Plex had been notified of the vulnerabilities on July 27 and acknowledged the report on August 4, awarding a bug bounty. The company released fixes in September, before the exploit code became public. The loader does not check the library’s name, executable permissions, digital signature, or symbols. As a result, the library’s ELF constructor can run with the same privileges as the Plex service. “It doesn’t check for a lib prefix, doesn’t require the execute bit, doesn’t verify any signature, and doesn’t look for any specific symbol.” reads the report published by zmain.com. “When dlopen loads a shared object, it runs the ELF’s DT_INIT_ARRAY (constructor functions) before doing any symbol resolution. A .so that only has a constructor and no exported symbols will still execute its code on load. We then trigger a second transcode. The codec directory gets re-enumerated, the .so we wrote in Stage 4 gets loaded, and the constructor runs as uid=1000(plex).” That detail matters because the final stage can exploit how Plex loads shared libraries. The chain uses a setting related to transcoding to influence execution, allowing a specially crafted library to run when Plex loads it. The result can be code execution under the service account, without requiring the attacker to obtain an interactive login first. QNAP urges users to update Plex Media Server immediately, users should go to App Center, open My Apps and update Plex Media Server to version 1.43.3 or later. They should then check in Plex Web, under Settings and General, that the installed version is 1.43.3.10861 or later. QNAP will release further updates after verifying them, but users should not wait. If Plex was reachable from the internet while running version 1.43.2 or earlier, users should treat the NAS as potentially compromised. This may apply if Plex Remote Access was enabled, port 32400 was forwarded, or the port was opened automatically through UPnP or router settings. Updating alone will not remove anything an attacker may have installed. In those cases, users should follow QNAP’s FAQ to perform a clean reinstall, check for signs of compromise and reset both their Plex and NAS credentials. The company also advises disabling Plex Remote Access if it is not needed and avoiding port forwarding for port 32400. Users who need remote access should use a VPN instead. QNAP also recommends keeping QTS or QuTS hero and all installed apps up to date. Step-by-step instructions are available in the Plex2Shell: Check and Remediation FAQ for QNAP NAS Users. CISA added Plex2Shell flaws to its Known Exploited Vulnerabilities catalog on October 20, 2026, urging federal agencies to addresse them by October 23, 2026. Follow me on Twitter: @securityaffairs and Facebook and Mastodon Pierluigi Paganini (SecurityAffairs – hacking, QNAP)
The US Department of the Treasury has cut off the MEXC Global crypto exchange from the US financial system over sanctions evasion and links with cybercrime gangs. Founded in 2018, the Seychelles-based MEXC is one of the world's largest crypto exchanges, giving more than 40 million users from more than 170 countries access to 3,000 cryptocurrencies and tokenized assets. According to a Financial Crimes Enforcement Network (FinCEN) order, MEXC has allowed illicit transactions of at least $16 billion linked to cybercrime operations and Iranian, North Korean, and Russian sanctions evasion between May 2021 and May 2026. The Treasury Department said that, as recently as June 2026, MEXC was still processing transactions with sanctioned Russian entities Garantex and Grinex, and it also facilitated or processed at least $226 million in transactions benefiting or connected to the Russia-based, OFAC-sanctioned A7 sanctions evasion network.
Confirm this action.
Leaving now will discard your changes.