Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Latest News

319 Chrome Extensions Have Been Quietly Routing Your Searches Through Private Servers for Years

  For roughly a decade, a cluster of Chrome browser extensions has been siphoning users' search queries through private servers before d...

All the recent news you need to know

Drupal Patches Critical RCE Flaw, Urges Immediate Updates

 

Drupal has released urgent security updates after patching a critical remote code execution (RCE) vulnerability that could allow attackers to take control of vulnerable websites. The flaw, tracked as CVE-2026-132165, affects Drupal’s core installer and can potentially be exploited by unauthenticated users under specific conditions. Drupal is widely used by government bodies, universities, major research institutions, media organisations and large enterprises, often across complex multi-site installations. That broad deployment makes the vulnerability particularly concerning for organisations that manage sensitive data or operate high-traffic public websites. 

The vulnerability exists in Drupal’s install.php file, which is used to set up a new Drupal installation. Under certain conditions, an attacker can use the installer to attempt to reinstall Drupal, potentially leading to a full site takeover or remote code execution. Drupal’s security team said some attack paths are mitigated when the web server cannot write to, or change permissions on, the settings.php configuration file. However, that protection is not guaranteed across all hosting environments, making prompt patching essential. The issue was discovered by Anthropic’s OSS Scanner and has been rated critical because it can be exploited by anonymous users.

Administrators should update immediately to Drupal 10.6.22, 11.3.22, or 11.4.13. Sites using the paid Drupal Steward web application firewall are already protected against known attack vectors, but Drupal still recommends upgrading because additional attack paths may emerge. Organisations unable to update immediately should block external access to /core/install.php through their web-server configuration or the .htaccess file in the web root. This temporary measure reduces exposure while a full upgrade is scheduled. Security teams should also identify all exposed Drupal installations, prioritise internet-facing systems, and review server logs for suspicious requests to the installer endpoint.

Drupal also patched a separate moderately critical gadget-chain vulnerability, CVE-2026-132166, which could allow administrators to achieve RCE if the application deserialises untrusted data through another flaw. Although this second issue requires an administrator account, it still represents a serious risk in environments where privileged accounts may be compromised or misused. The company warned that exploits may be developed “within hours or days,” reflecting the speed at which attackers often weaponise critical web-application vulnerabilities. This warning is especially relevant because Drupal has previously disclosed actively exploited flaws, including an SQL injection issue and a Commerce Core access-bypass vulnerability. 

For organisations running Drupal, the immediate priority is clear: apply the available security releases, restrict installer access where patching is delayed, and monitor logs for suspicious activity. CISA has flagged five Drupal vulnerabilities as exploited in the wild since 2021, underlining why delayed patching can leave organisations exposed to real attacks rather than theoretical risks. A fast, coordinated response—covering updates, access restrictions, logging and incident monitoring—can substantially reduce the likelihood that this critical RCE flaw is exploited before attackers develop working exploit chains.

China-Linked Hackers Exploit VMware vCenter Zero-Day to Steal Data

 

A China-linked hacking group, previously named UNC5221, and now known as Armory Castle, has exploited a zero-day vulnerability in VMware vCenter Server to gain administrative privileges and exfiltrate data. 

The vulnerability, which has been assigned the identifier CVE-2026-123890, has a CVSS score of 9.8 and affects VMware Directory Service. It can be exploited by unauthenticated attackers to bypass authentication by leveraging a vulnerability in SRP-6a session keys in DCE/RPC. If exploited, attackers can gain administrative privileges within the system, allowing them to run commands and access sensitive files. 

Within the attack, the hackers used a custom tool written in Golang known as BONESAW. This can be used to extract database files, take control of VMware’s Security Token Service, and establish admin accounts for Single Sign-On. As part of a wider attack, the same threat actors exploited a zero-day (CVE-2026-102764) within BeyondTrust Remote Support. 

Once inside the system, they performed reconnaissance, established persistence, and deployed a proxy tunneling tool (BARECLAW). From here, they moved into an internal Linux appliance and increased their access. Several other tools were used in the attack. These included SLIMSAVAGE, CAGEMATCH (web shells), SAWSNAKE (to bypass SAML authentication), BEARBONES (to collect plaintext credentials), and LAZYBONES (backdoor using Slack for C2). 

The tools allowed the threat actors to run commands, masquerade as users, persist within systems and move between systems. Once inside vCenter, the threat actors set up a local admin account, enabled SSH access, and investigated ESXi file systems. They mounted virtual machine storage volumes, and added an SSH key to the root account. Data was collected, and stored and passed through the compromised Remote Support appliance for later exfiltration. 

The BONESAW binary had a build date of July 13 2026, which may suggest that the threat actors were aware of the vulnerability prior to it being made public. However, this information can be changed, and does not confirm at what point in time the tool was developed. On 19th November 2026, Broadcom released patches for affected products. 

These include VMware vCenter, Cloud Foundation, vSphere Foundation, and Telco Cloud. Patches should be applied to prevent exploitation. This is the second zero-day vulnerability exploited by Armory Castle in 2026. Previously, in CVE-2026-41709, the group exploited a poor logging vulnerability within VMware ESX to make their actions less visible. 

In this attack, it can be seen that Armory Castle can use zero-day vulnerabilities in combination with bespoke malware to compromise enterprise infrastructure.

FastUnlock Windows Vulnerability Allows Code Execution from the Lock Screen


Using a newly disclosed Windows zero-day vulnerability, dubbed FastUnlock, individuals with physical access to a locked computer can launch programs without entering valid login information. It bypasses certain lock screen restrictions by exploiting Windows' Narrator screen reader and Microsoft account recovery options. There has been no security update from Microsoft that addresses the issue. 

The vulnerability was discovered on November 19 by a security researcher operating under many aliases, including Nightmare Eclipse and MSNightmare. On GitHub, the researcher provided proof-of-concept demonstrations that illustrated how the technique could allow users access to Windows systems without requiring them to complete a normal login process.

ThreatLocker, an endpoint security firm, independently tested the method on the same day and confirmed that it is effective. FastUnlock does not provide complete control over the compromised computer. Instead, successful exploitation allows programs to run under a restricted Windows account designated as WsiAccount that does not possess administrator privileges. Even so, the capability to execute programs from a locked session presents a security risk, particularly when devices are left unattended or become accessible to unauthorized individuals. 

To conduct the attack, physical access to the target computer and a Microsoft account are required. These accounts can be reached through the recovery options on the lock screen of the computer. Windows Narrator is used to facilitate this process, which is an accessibility feature that reads on-screen content aloud and assists users in navigating the operating system. 

Using an attacker's manipulation of the recovery environment's interface, an attacker may have access to system settings and components normally unavailable without authentication by manipulating its interface. A Windows 11 26H2 system with November security updates was used to demonstrate the technique. There has yet to be a comprehensive testing of other Windows versions, and an official list of affected versions has not yet been published. 

ThreatLocker however has confirmed that its independent testing was successful in gaining access to the restricted account and executing a program. Microsoft's built-in drive encryption technology BitLocker has also been cited as a concern by this technique. Even though BitLocker protects data stored on a device, its effectiveness against FastUnlock depends largely on how the drive is configured to unlock when the drive is powered on. 

Automatic TPM-based unlocking involves releasing the encryption key at boot time without the need for a separate PIN by the Trusted Platform Module (TPM). Thus, the drive may already be accessible when the Windows lock screen appears. Rather than cracking BitLocker encryption directly or retrieving its encryption keys, FastUnlock operates after the system has completed its normal startup process and unlocked the drive. 

The technical concern underlying FastUnlock is in how Windows handles accessibility features prior to requesting the authentication of users. A hidden background window that should not be accessible during a locked session has been accessed by the attack, allegedly by utilizing Narrator's ability to interact with system interfaces from the lock screen. In order to initiate the process, the researcher explained that the process begins by opening the Microsoft account recovery option and activating Narrator using a shortcut provided by Windows. 

By using keyboard navigation, an attacker is able to access Narrator's settings and open Windows Settings without logging in. Once there, changing the AutoPlay settings can cause a USB drive to open in File Explorer, enabling a program stored on the drive to be launched under the restricted WsiAccount context. Narrator's interface changes may have caused the underlying issue. 

Microsoft redesigned the accessibility feature without properly restricting its new interface to operate within the lock screen environment, according to the researcher. As a result of this, an inconsistency exists between protections meant to prevent unauthorized access and accessibility tools. However, the restricted account does not necessarily reflect the full extent of the potential impact. Earlier in November, the researcher revealed SignDrop, another zero-day privilege-escalation technique for Windows. 

Using both vulnerabilities together, the researcher claims that on systems that are susceptible to both flaws, access could be elevated beyond the WsiAccount privileges. For laptops using BitLocker's automatic TPM-based unlocking feature, FastUnlock is particularly concerning since physical access to an unattended computer may significantly increase the consequences of physical access. 

By bypassing the Windows sign-in screen once the drive is unlocked during startup, users may expose sensitive data that they expect encryption to protect. However, this technique does not constitute a remote attack, and its reported capabilities should not be construed as a complete compromise of all affected systems. 

In the absence of a patch or official assessment by Microsoft, the researcher's claims and independent testing remain significant references. In addition to being tested with Windows 11 26H2 version, FastUnlock is not confirmed to be compatible with Windows 10. It is also unknown whether FastUnlock has been used in active attack campaigns. It will be necessary for organizations and individuals to take additional precautions until Microsoft releases an official security update to reduce the risk posed by FastUnlock. 

As a result, physical security must be strengthened and additional authentication must be required before Windows devices can reach an unlocked operating environment. This is the most effective method. With BitLocker startup PIN enabled, in conjunction with TPM-based protection, an additional layer of security can be provided for systems running Windows 11 Pro, Enterprise or Education. This configuration requires a PIN before Windows starts and the encrypted drive becomes accessible as opposed to automatic TPM unlocking. 

Additionally, when carrying a device during travel or using it in a shared work environment, computers should be completely shut down or hibernated prior to being left unattended. Users of Windows 11 Home will have fewer choices due to the fact that its Device Encryption feature does not offer the same setup of startup PINs. It is therefore particularly important to keep laptops under physical supervision and to prevent unattended devices. 

Organizations may also consider restricting Narrator using tools such as Windows Defender Application Control (WDAC) or AppLocker to review application-control policies. The blocking of Narrator could result in adverse consequences for users who use accessibility features, making careful assessment prior to deployment essential. 

The research indicates that the USB-based execution route described in the study can also be reduced by disabling AutoPlay for removable media, although it should not be considered a complete fix. Chaotic Eclipse, also known as Abdelhamid Naceri, has previously disclosed vulnerabilities affecting Microsoft Defender, BitLocker, and other Windows components as a result of this disclosure. 

The vulnerability of YellowKey, which had previously been related to BitLocker, was later assigned a CVE and addressed by Microsoft's security updates. Despite the requirement for physical access to FastUnlock, it remains a security concern rather than a verified actively exploited threat at present. 

Although remote exploitation is limited by the requirement for physical access, unattended laptops and poorly protected workstations may be vulnerable to cyberattacks since they can bypass normal sign-in barriers. Microsoft users and IT administrators should monitor official security advisories and apply patches as soon as they become available.

Cyberattack on Wellington IT Exposes Payee Information Across 40 Irish Credit Unions

 



A cybersecurity incident involving Belfast-based technology provider Wellington IT has exposed sensitive financial information associated with members of approximately 40 Irish credit unions, raising concerns about third-party security risks and delayed breach disclosures within the financial sector.

Wellington IT provides banking software and technology services to approximately 50 credit unions, including 43 institutions in Ireland. The company reportedly became the target of an attack that exploited an authorization vulnerability in its infrastructure, allowing an unauthorized actor to retrieve saved payee records from its CU Online platform.

Ireland's Minister of State with responsibility for Credit Unions, Robert Troy, confirmed to RTÉ that Wellington IT was the third-party service provider involved in the incident. Approximately 40 of Ireland's 172 credit unions are believed to have been affected.


Authorization Flaw Exploited Through Automated Requests

According to breach notifications reviewed by the Irish Examiner, Wellington IT informed affected credit unions that an automated script generated approximately five million requests between October 2 and October 4, 2026, exploiting an authorization flaw within its systems.

The requests reportedly originated from an automated client using valid member login credentials. The attacker subsequently accessed saved payee records without authorization.

However, the precise scope of the intrusion remains undetermined. Wellington IT acknowledged that the activity logs required to establish which individual records were requested and retrieved were unavailable. Consequently, the company cannot currently identify every affected member or verify the exact information accessed.

There is also a discrepancy in publicly reported activity figures. Irish League of Credit Unions CEO David Malone told RTÉ that approximately 1.4 million activities were attempted during the attack window. The five-million figure comes from Wellington IT's reported notification to customers. The difference has not yet been reconciled.

The incident reportedly went undetected as a data breach until November 15, when Wellington IT identified the potential compromise. Credit unions were notified on November 16, more than six weeks after the reported attack. Minister Troy criticized the delay, describing it as unacceptable and seeking an explanation from the provider.


Financial and Personal Information Potentially Exposed

At least six credit unions have independently acknowledged their involvement: Capital Credit Union, Phoenix Credit Union, St. Canice's Credit Union, First South Credit Union, Malahide Credit Union, and Limerick & District Credit Union.

The compromised information concerns saved payment beneficiaries rather than the account holders' own banking credentials. Depending on the records involved, exposed information may include:

  • Payee names and associated bank account names.
  • Nicknames assigned to saved beneficiaries.
  • International Bank Account Numbers (IBANs).
  • Bank Identifier Codes (BICs).
  • Bank account numbers and sort codes.
  • Payee addresses.
  • Payment references associated with saved beneficiaries.

The records could also establish which credit union member had saved a particular beneficiary within the online banking platform.

Importantly, the affected credit unions have indicated that members' passwords, PINs, payment card information, online banking credentials, account balances, and funds were not compromised.

Nevertheless, the exposed information creates opportunities for targeted social engineering. Attackers possessing legitimate payment details could impersonate credit union representatives, familiar beneficiaries, or financial service providers to convince members to disclose additional information or redirect legitimate payments.

Such attacks could involve fraudulent emails, text messages, and telephone calls containing accurate financial details to establish credibility.


Wellington IT Responds to the Incident

In a statement provided on November 19, Wellington IT CEO Colin Mitchell confirmed that the company had notified its credit union customers about a cybersecurity incident potentially involving information maintained within its CU Online platform.

Mitchell stated that the company had implemented measures to address the issue and engaged external cybersecurity specialists to investigate the incident and determine its full scope.

The investigation remains ongoing, with Wellington IT working alongside the Data Protection Commission (DPC), National Cyber Security Centre (NCSC), and Garda National Cyber Crime Bureau (GNCCB).

The company also stated that it is assisting affected credit unions in assessing potential exposure and meeting their regulatory obligations.


Regulatory Scrutiny and Third-Party Security Concerns

The incident has prompted scrutiny from Irish authorities, with the Data Protection Commission receiving multiple breach notifications from affected credit unions. The Central Bank of Ireland has also been notified, while the Department of Finance is engaging with relevant stakeholders.

Under Article 33 of the General Data Protection Regulation (GDPR), organizations must notify the relevant supervisory authority of qualifying personal data breaches without undue delay and, where feasible, within 72 hours of becoming aware of them. Data processors must also notify their controllers without undue delay after discovering a breach.

The incident additionally raises questions about third-party oversight within financial institutions. The Central Bank's credit union outsourcing guidance requires institutions to conduct appropriate due diligence, monitor service providers, and maintain controls addressing operational risks associated with outsourced activities.

Credit union members have been advised to remain particularly cautious about unexpected communications requesting payments, banking information, or changes to beneficiary details. Any suspicious communication should be verified directly with the relevant credit union.

While investigations have yet to establish the total number of affected individuals, the incident demonstrates how a vulnerability within a shared technology provider can expose information across multiple financial institutions.

Critical Cisco Expressway Vulnerability Exploited By Hackers Shortly After Public PoC Release

 

A Russian organisation was compromised via a vulnerability in Cisco Expressway. Shortly after public exploit code was published, attackers exploited this vulnerability to gain access to Internet facing systems within the organisation. Once in the network, attackers gained root access. Custom tools were then created to allow lateral movement within the network, and to search for sensitive data. 

Cisco Expressway is a collaboration gateway which allows remote employees, partners and third parties to access enterprise communications such as video calling, phone calling and instant messaging. As external users can connect to internal systems, vulnerabilities within these systems can pose a significant risk. The vulnerability was assigned the ID CVE-2026-76466, and has a CVSS score of 9.8. It allows unauthenticated attackers with network access to execute arbitrary commands with root privileges. 

This affects Expressway Core and Expressway Edge systems, both in virtual and hardware appliance form. However, this is only applicable to systems which are in ‘cluster’ configurations. This vulnerability was disclosed by Cisco on 21st October 2026. It exists within the Expressway database service component and relates to cookies being stored persistently. If an attacker can gain access to these cookies, they can access the database service and execute certain remote procedure call commands. 

This allows command execution with root privileges within the underlying operating system. Cisco published a patched version of Expressway (X15.5.20). No workarounds are available. Customers using versions before X15 should upgrade to a patched version to resolve this vulnerability. Although Cisco’s initial advisory stated that there was no public announcement of exploit code or exploitation, exploit code was published on GitHub. The incident detailed by F6 occurred shortly after this exploit code was published. 

Attackers exploited two Internet facing Cisco Expressway systems running version X15.5.3. Attackers then laterally moved to two other cluster nodes within the internal network, using one compromised system. Once root access had been obtained, attackers began creating tools to allow lateral movement. Custom tools were created in Python to allow scanning of network infrastructure, discovery of Server Message Block (SMB) resources, and interacting with Microsoft SQL Server and Windows Remote Management (WinRM). 

The tools were also used to search GitLab repositories. This suggests attackers were attempting to find credentials or sensitive data within the system. Throughout the attack, F6 observed that attackers made changes to their scripts. Comments within the code, and descriptions of changes made within the scripts, suggest that an AI assistant may have been used to create/modify the tools. F6 has not identified which organisation was impacted, or linked this incident to any known threat actors. 

They have however provided some indicators of compromise (IPs and file paths) to assist defenders in investigating whether they may have been compromised. F6 also recommends checking the Erlang system log on Expressway systems for evidence of exploitation. If organisations cannot apply the patch immediately, F6 recommends limiting access to TCP ports 4371 and 4372 in the firewall. Only trusted cluster node IPs should be allowed to connect. This is not an officially recommended workaround from Cisco. In the long term, it is recommended to upgrade to a patched version.

Major Financial Firms Disclose Data Exposure Following Third-Party Security Breach


After a cyberattack on a third-party service provider, JPMorgan Chase, Visa, and Mastercard disclosed a customer data exposure incident. A spokesperson from each company stated on Thursday, November 19, that attackers gained access to limited customer information, including names and email addresses, stored by an external vendor. However, it is noted that their internal systems and payment networks have not been compromised. 

A preliminary investigation by JPMorgan Chase indicates that attackers accessed marketing-related information maintained by certain of the company's service providers. The exposed data may include customer names and email addresses. As a result of the incident, the bank has clarified that it did not impact its banking services and that customers' transactions were not disrupted. 

According to a spokesperson for the bank, affected customers will be contacted directly. Further assistance will also be provided, including complimentary credit monitoring services, where appropriate. Furthermore, the company clarified that the data exposure was unrelated to technical problems reported by some customers earlier in the week, which were caused by a software defect that affected the transaction processing process. 

According to Visa, the allegations are related to a security breach involving a third-party service provider in Asia-Pacific. The company maintained that its own infrastructure remained secure and that no payment-related information, including card numbers, had been accessed. Mastercard also confirmed that it had recently been made aware of an incident involving an external service provider. 

According to the company, a limited number of email addresses belonging to a small group of cardholders enrolled in a particular benefit program were exposed as a result of the breach. This information was classified by MasterCard as non-payment data and the payment network remained unaffected. The disclosures followed the announcement of the hacker group N0n's claim to responsibility on November 16, 2017. 

In its leak website, the group claims to have published files containing customer-related information related to all three financial institutions. There is rumored information that the attackers offered for download was accompanied by a list of three companies as organizations that had not paid. As a result of the incident, financial institutions are exposed to security risks associated with third-party service providers, particularly when external companies are involved in marketing activities and customer information management.

It is reported that the exposed data does not include payment credentials, but it is still possible to target targeted phishing campaigns and conduct social engineering attacks based on customer contact information. Especially within the financial services industry, where external providers often manage customer engagement, marketing campaigns and benefit programs, this incident has highlighted the risks associated with third-party data handling. 

The exposed information did not contain payment credentials, but the availability of customer contact information and email addresses could still provide attackers with an opportunity to commit targeted fraud. A sample of the alleged information has been published on a dark web leak site by the ransomware group N0n, who claims responsibility for the intrusion. 

In the material, according to cybersecurity firm SOCRadar, customer and employee email addresses are reported, along with some telephone numbers and postal codes for some records. However, no independent determination has been made regarding whether N0n was responsible for the attack or whether the published data is authentic. There was a reasonable probability that SOCRadar's available evidence suggests that the breach involved a third-party vendor and information related to marketing and cardholder benefits. 

According to the cybersecurity firm, targeted phishing is the most immediate concern for customers affected by this breach. In some cases, attackers may use exposed contact information to send phishing emails or messages impersonating JPMorgan, Visa or Mastercard, which may trick recipients into divulging information such as passwords, banking credentials, or other sensitive information. 

In most cases, attacks are carried out through social engineering rather than exploiting technical vulnerabilities in banking infrastructure. A fraudulent message can appear more credible if it uses legitimate customer details, thus making it difficult for recipients to differentiate genuine communications from malicious ones. 

The information may also be used to prepare follow-up scams, impersonate customer service representatives, and direct victims to fraudulent login pages. Additionally, the breach raises questions concerning the management of information shared with external suppliers by financial institutions. 

Vendor services such as customer communication, promotional campaigns, and loyalty programmes are frequently used by organizations, creating additional places for sensitive information to be protected. It is therefore possible to expose information related to several major companies through a security failure at one supplier, even if their internal networks remain secure.

Security specialists have also stressed how such incidents could negatively affect the reputation of the company. The financial institution itself is generally regarded as liable for protecting customers' information, regardless of whether compromised systems are the property of an external provider. This incident highlights the importance of performing rigorous vendor security assessments, limiting customer access to information, and strengthening authentication procedures to reduce identity-based fraud risks. This incident also emphasizes the importance of protecting personal contact information, especially telephone numbers and email addresses that can be used to perpetrate follow-up scams. 

Cybercriminals may use these details to impersonate banks, credit card providers, or customer support teams and send convincing messages to steal credentials and financial information by impersonating banks, card providers and customer service representatives. Whenever possible, customers are advised to be alert to emails, text messages, and telephone calls claiming to be from JPMorgan, Visa, or Mastercard, especially those requesting account details, passwords, or one-time verification codes. This breach also raises concerns regarding the increasing reliance on external service providers by financial institutions.

The outsourcing of marketing and customer engagement activities can increase operational efficiency, however it also increases security risks beyond the capabilities of the organization itself. Financial companies must ensure that vendors adhere to strict data protection policies, limit access to customer information, and maintain adequate safeguards to prevent unauthorised access to customer information. It is also essential to conduct regular security assessments of third-party systems and monitor them more closely in order to identify vulnerabilities before attackers can exploit them. 

There are still uncertainties regarding the extent of the incident, since the companies have not disclosed the identities of the affected service providers or the exact number of customers affected. Neither the authenticity of the leaked files nor the claims made by the N0n group have been independently verified. 

While the incident had significant consequences for numerous major financial institutions, it illustrates how a security breach at a single external supplier can result in severe data exposure risks, even in the case of secure core banking systems and payment systems.

Featured