Microsoft is developing the Windows 11 27H2 update, focusing on core system stability, new wallpapers, and 64-bit speed via Intel APX register expansion.
Related Posts:
The post Windows 11 27H2 Update Brings Intel APX Boost appeared first on Daily CyberSecurity.
Discord is rebuilding its Discord Rust desktop client with GPUI, ditching Electron to slash memory consumption and share native code with mobile.
Related Posts:
The post Discord Rust Desktop Client Ditches Electron for GPUI appeared first on Daily CyberSecurity.
Google is testing Chrome tab scrolling in Canary, letting users navigate crowded tabs via mouse wheels, gestures, and dedicated scroll arrows.
Related Posts:
The post Chrome Tab Scrolling Returns to Canary Builds appeared first on Daily CyberSecurity.
Apple announced steep internal AI budget cuts, curbing daily token allowances for engineers as corporate technology spending faces tighter scrutiny.
Related Posts:
The post Apple AI Budget Cuts Target Internal Model Usage appeared first on Daily CyberSecurity.
Google announced the Google Quick Share SDK for Android and iOS, bringing cross-platform file sharing and native AirDrop compatibility to third-party apps.
Related Posts:
The post Google Quick Share SDK Brings Seamless Cross-Platform Sharing appeared first on Daily CyberSecurity.
The Raspberry Pi 16GB price jumps to $385 as persistent DRAM supply shortages force manufacturer price hikes across high-memory flagship boards.
Related Posts:
The post Raspberry Pi 16GB Price Surges Amid Memory Shortages appeared first on Daily CyberSecurity.
GitHub has launched Copilot Fusion, a system that automatically selects AI models for coding tasks, helping developers balance code quality, speed, and cost.
Instead of choosing a model for every request, users select Fusion and let it decide how to handle the work. It is generally available in Visual Studio Code, Copilot CLI, the GitHub Copilot app, and JetBrains IDEs.
Fusion is a model router and coordinator, not a new standalone model. It checks each request for reasoning, code generation, debugging, and tool needs, then chooses the models and steps needed to produce one final answer. It also considers system health and model availability when making those choices.
Fusion uses three execution patterns. In Single mode, one model completes the task. Cascade starts with an efficient model, then uses a judge to inspect the draft and decide whether a stronger model should take over.
Critique sends a draft to several models for independent reviews before the original model revises its answer using their combined feedback.
These patterns can change within the same conversation. A simple request may use one model, while a difficult follow-up may trigger extra review.
GitHub says choosing a pattern adds little delay, although Cascade and Critique take longer because they involve additional model calls. Developers can follow progress and inspect which models contributed to the final response.
Fusion Standard selects one model for everyday work. Fusion High supports larger, clearly defined tasks, including difficult bug fixes and changes across several files.
Fusion Max targets work needing deeper reasoning. Fusion Fast serves speed-sensitive requests in Visual Studio Code inline chat and cannot be selected directly by users.
According to GitHub’s documentation, paid Copilot users get a 30% discount on Fusion model costs through November 30, 2026, though High and Max can consume more AI credits than Standard.
Fusion keeps the main conversation on the same model where possible to preserve cached tokens. Supporting models receive only the context they need.
Model selection also follows subscription limits, administrator restrictions, data residency rules, and FedRAMP requirements. Supported local models can participate through Fusion Standard in a public preview.
Extra AI review should not be mistaken for a security guarantee. Earlier reporting on GitHub Copilot prompt injection and the RoguePilot repository takeover flaw shows why untrusted project content remains a concern. Both issues were patched, and neither report establishes a vulnerability in Fusion.
GitHub also warns that discarding a draft does not automatically undo file edits that draft already made. Developers must review workspace changes before committing them. Fusion works separately from subagents and doesn’t launch them, so its role is coordination rather than independent agent management.
Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.
The post GitHub Launches Copilot Fusion for Smarter and Cheaper AI Coding appeared first on Cyber Security News.
Microsoft has introduced a new command-line tool that gives IT admins a faster way to check and manage OneDrive sync across company devices. Microsoft introduced the OneDrive Sync Client Command Line Interface (CLI) at the OneDrive + Copilot event held today. It is aimed at teams that look after large Microsoft 365 setups.
The tool runs with a simple command called odsync and can be used from PowerShell. In the live demo, Microsoft’s Andrey Esipov showed how admins can pull detailed device health information without clicking through settings screens or digging through log files.
According to the demo, the CLI lists every OneDrive account set up on a device, including machines with more than one account, and it can narrow the results down to a single account. It also shows the version of both the sync client and the CLI, whether OneDrive is running, and how it was installed on the system.
Admins can also see Folder Backup settings, including which folders are being backed up to the cloud. One of the most useful features for security teams is the ability to view the Group Policy settings applied to the sync client. This helps confirm that a device actually follows company rules.
The tool also reports overall status at the client, account, and Folder Backup level. When something goes wrong, admins can switch on verbose output for deeper troubleshooting.
A key detail is that the CLI can return results in JSON format. This makes it easy to plug the output into scripts, Microsoft Intune remediation jobs, or reporting tools. Microsoft says the tool works in both interactive and non-interactive modes. It is designed for admins, developers, scripts, and AI agents such as GitHub Copilot CLI.
For example, an admin could run a script across many devices to spot machines where Folder Backup is turned off or where OneDrive is not running at all. Until now, this kind of check often needed custom scripts, registry checks, or third-party utilities.
OneDrive sync is a common blind spot in many companies. Settings that drift away from policy can leave sensitive files outside approved storage or sync them to places they should never reach.
Cyber Security News has earlier reported how OneDrive auto-sync exposed enterprise secrets in SharePoint Online, showing how small sync mistakes can grow into real data leaks. Threat actors have also abused the sync client itself, as seen when hackers exploited OneDrive.exe through DLL sideloading to run malicious code.
A tool that quickly shows the sync client’s real state on each device gives defenders better visibility. It also helps them catch weak setups before they turn into security incidents.
The OneDrive Sync CLI is not yet generally available. Microsoft says it is coming soon to private preview. The company has not shared a public release date, the supported platforms, or a full list of commands. Based on what has been shown so far, the tool focuses on reading and reporting device state rather than changing settings.
Admins who want to get ready can review Microsoft’s guidance on planning file sync for SharePoint and OneDrive and watch the official OneDrive sync release notes for updates.
Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs.
The post Microsoft Unveils New OneDrive Command-Line Tool to Manage Sync Deployments appeared first on Cyber Security News.
Revolut suffered a major service outage on Tuesday, October 20, 2026, disrupting payments, cash withdrawals, and access to its banking app. The digital bank said customer money and data remained safe while engineers worked to restore affected services. The disruption came as Google Cloud reported problems in its London region.
Reuters reported that a person familiar with the matter linked Revolut’s outage to the Google Cloud disruption. Google said its engineering team was investigating an issue affecting europe-west2, its London cloud region. The reports did not establish the technical cause or provide a confirmed recovery time.
The outage affected everyday banking tasks rather than a single app feature. Revolut’s status page listed 28 services as partially unavailable, including account sign-ins, card payments, transfers, currency exchange, stock trading and live support chat. Reuters also reported disruption to ATM withdrawals.
For customers, that meant problems could extend beyond opening the app. An affected card payment could interrupt a purchase, while unavailable transfers or cash withdrawals could limit access to funds. Disruption to support chat also affected a channel customers would normally use to ask about payment failures or account access.
“We are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe,” Revolut said. The company added that it had been working to fix the issue since identifying it that morning and apologized to affected customers.
The reported connection to Google Cloud places the focus on service availability and cloud dependencies. However, neither the Reuters report nor Revolut’s quoted statement identified malware, ransomware or an intrusion as the cause. The available evidence supports reporting this as an outage, not a confirmed cyberattack or data breach.
A banking service can become unavailable without customer records being stolen. Revolut’s statement addresses the safety of funds and data, while the service reports describe problems accessing banking functions. These are separate questions, and an investigation would need to establish what failed before assigning a more specific cause.
Previous incidents show why the underlying failure matters. Cybersecurity News covered a Google Cloud outage linked to its API management system in June 2025. That incident involved a software failure affecting request processing across services. There is no evidence in the reports reviewed that Tuesday’s disruption shares that cause.
The publication also reported Google Cloud’s accidental deletion of UniSuper’s private cloud account in 2024. Recovery involved rebuilding services and using backups held with another provider. That case offers a separate example of how cloud failures can disrupt financial services, rather than evidence explaining the current Revolut incident.
At the stage described in the cited reports, Google was investigating, and Revolut was working to restore service. Neither report supplied a complete technical explanation or a confirmed time for full recovery. Any later update should distinguish restored functions from services that remain partly unavailable.
For security and operations teams, the immediate issue is understanding the scope of the disruption without confusing downtime with compromise. The unanswered questions include which cloud component failed, how that failure affected Revolut’s services, and whether recovery measures restored all affected functions for affected customers. Those details will determine what lessons can reasonably be drawn from this incident.
An EDR alert reveals an attack. But can it tell the full story? Discover how to reconstruct the attack timeline.
The post Revolut Outage Disrupts Payments and Banking Services as Google Cloud Reports London Issues appeared first on Cyber Security News.
Microsoft has confirmed that Windows Server security updates released on October 13, 2026, can disrupt Exchange Server email services, blocking webmail access and leaving messages undelivered.
The issue affects some on-premises systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition. Microsoft has published a workaround and advises administrators not to uninstall the Windows updates.
The failures stem from changes in Windows Server, not the separate October Exchange Server security updates. Servers can experience problems even without installing the latest Exchange patches, making the underlying operating system update the key factor when investigating these outages.
Microsoft identified four Windows updates linked to the failures. These are KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016. The impact depends on server workload, and some systems may never develop symptoms.
Users may be unable to sign in to Outlook on the web, while messages sent through Outlook remain stuck in the Outbox. Administrators may notice growing mail queues, failed mailbox access during replication, or problems with Database Availability Group members reaching quorum. Restarting an affected server may restore service temporarily.
One error administrators should watch for is MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142). Affected systems may also record Event ID 1006 in the Application log, providing a useful sign when checking whether an outage matches Microsoft’s report.
According to Microsoft’s Windows release health notice, the October updates introduced a default limit of 512 simultaneous Endpoint Lookup calls. This limit controls memory use by Endpoint Mapper, a Windows component involved in remote procedure call communications. Heavy Exchange workloads can exceed the default allowance.
Increasing the limit allows Endpoint Mapper to use more memory to handle these calls. Microsoft currently lists the issue as mitigated rather than resolved and says its investigation remains ongoing. An additional mitigation is available through Microsoft Support for affected organizations.
Microsoft’s Exchange Team advisory instructs administrators to open an elevated Command Prompt on the Exchange server and run reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f. The server must then be restarted.
After the reboot, administrators should monitor the environment for recurring failures. Microsoft says the limit should be raised further if problems return, although its advisory does not specify a second value. The company reports that this approach has resolved the issue in customer cases it has handled.
Keeping security updates installed remains important. Cybersecurity News recently covered Microsoft’s reissued Exchange Server security update, highlighting the continuing need for supported patches.
The disruption also arrives as Exchange 2016 and 2019 approach the end of their final paid update period. Following earlier reporting on out-of-support Exchange servers, Microsoft says October 2026 marks their last scheduled ESU security release, with future updates limited to Subscription Edition.
An EDR alert reveals an attack. But can it tell the full story? Discover how to reconstruct the attack timeline.
The post Microsoft Confirms October Windows Updates Can Break Exchange Server Email Services appeared first on Cyber Security News.
Microsoft fixed a Windows 11 update issue that could leave users staring at a black screen after signing in or cause Windows Explorer to crash.
The problem mainly affected Azure Virtual Desktop hosts using FSLogix, and some existing user profiles were more likely to fail to load the desktop. Microsoft marked the issue as resolved on October 13, 2026.
The fix is included in KB5127646 for Windows 11 version 26H1 and later updates. Microsoft recommends installing the latest available update on each device. Systems running the October 13 update or later no longer need the temporary workarounds for this issue.
According to Microsoft’s Windows release health notice, the problem began after the August 2026 non-security preview update, KB5120996. It continued through subsequent updates for Windows 11 version 26H1; that originating update carried OS Build 28000.2804.
Affected users could sign in but found their desktop session did not load automatically. Instead, a black screen appeared, leaving them unable to access the desktop until they started the session manually. Application event logs could also show Windows Explorer crashes, giving administrators a useful sign when checking affected systems.
Microsoft lists Windows 11 versions 26H2, 26H1, 25H2, and 24H2 as affected client platforms. This issue does not affect Windows Server. Although reports mainly involved Azure Virtual Desktop environments using FSLogix, Microsoft did not describe every device running those Windows versions as affected.
Cybersecurity News previously covered the Windows 11 update bug causing black screens, including the temporary recovery steps available before this fix. The new resolution removes the need to rely on those measures once an affected device receives the appropriate update.
Users still running an update released before October 13 can temporarily restore desktop access by pressing Ctrl+Shift+Esc to open Task Manager. They can then select Run new task, enter explorer.exe, and choose OK. Microsoft provides this method as a workaround, not a replacement for installing the fix.
For enterprise-managed devices, administrators can also use Known Issue Rollback, or KIR, through a special Group Policy. The supplied notice identifies KB5124006 260924_20071 for Windows 11 26H1 and KB5124010 260924_20021 for Windows 11 26H2, 25H2, and 24H2.
Administrators must install and configure the policy that matches their Windows version, then restart affected devices. This turns off the change responsible for the issue.
Cybersecurity News also reported on another Windows 11 update fix that replaced a temporary rollback, showing why a workaround and a permanent update aren’t the same.
First, match the symptoms to Microsoft’s health notice and confirm the installed Windows version and update level. Reported signs include a black screen after sign-in, failure to load the desktop, and Windows Explorer crashes. The notice does not identify malware or an attack as the cause.
Microsoft’s Windows 11 release information lists KB5127646 as the October 13 security update for version 26H1, bringing it to Build 28000.3231. Administrators should use the update appropriate for each supported Windows release rather than assume the same package applies across every affected version
Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs.
The post Microsoft Fixes Windows 11 Update Issue that Causes Black Screen Errors or Windows Explorer crash appeared first on Cyber Security News.
Mozilla Firefox 158.0 is officially available, featuring default JPEG XL image format support, CSS enhancements, and advanced WebDriver automation capabilities.
Related Posts:
The post Firefox 158.0 Released: Default JPEG XL Support appeared first on Daily CyberSecurity.
A massive French supermarket cyberattack targeted Danfoss refrigeration systems, causing catastrophic food spoilage and fires across 400 retail locations.
Related Posts:
The post Massive Cyberattack Paralyzes French Supermarket Refrigeration appeared first on Daily CyberSecurity.
Discover the new Qualcomm AI Wi-Fi 8 broadband technology. Learn how gFiber and Gemtek are transforming routers into edge computing smart service gateways.
Related Posts:
The post Qualcomm AI Wi-Fi 8: The Next Broadband Evolution appeared first on Daily CyberSecurity.
Discover the official release of LineageOS 24.0 based on Android 17. Explore new system updates, synchronized security patches, and the WebUSB flashing tool.
Related Posts:
The post LineageOS 24.0 Released: Android 17 & Web Flashing Tool appeared first on Daily CyberSecurity.
Microsoft is investigating an Exchange admin center access issue that may prevent some administrators from opening the web portal used to manage Exchange Online. Affected admins may encounter an “Internal Server Error” message, according to the Microsoft 365 Status update provided for this report.
The company is tracking the incident under EX1500900 and has directed customers to the Microsoft 365 admin center for further information. The notice describes an access problem affecting some admins. It does not establish a global outage or confirm that users are unable to send and receive email.
“We’re investigating an issue in which some admins may be unable to access the Exchange admin center (EAC) and may encounter an ‘Internal Server Error’ message,” the supplied notice states.
The Exchange admin center is Microsoft’s web-based console for managing Exchange Online. IT teams use it to manage mailboxes and groups, review mail flow reports, and handle migrations. Microsoft’s Exchange admin center documentation explains that available features depend on the administrator’s assigned roles and permissions.
Losing access can delay these tasks, particularly when teams need to review delivery problems or make urgent mailbox changes. However, an unavailable management portal does not, by itself, show that the underlying email service has stopped working. The supplied incident notice identifies admin access as the reported problem.
The brief announcement does not identify a root cause, affected regions, the number of impacted organizations, or a recovery timeline. It also does not announce a confirmed workaround. Those gaps mean the incident should not be described as a cyberattack or linked to a specific service change.
Administrators should check Health > Service health in the Microsoft 365 admin center and look for EX1500900. Microsoft’s service health guidance explains that this dashboard lists active incidents and advisories, with individual pages providing further details about each issue.
The Microsoft 365 Admin mobile app also supports service health updates and push notifications. This gives teams another way to follow Microsoft’s investigation without relying on the Exchange management interface itself. Updates should be checked against the incident record rather than inferred from reports about unrelated outages.
For essential work, Exchange Online PowerShell provides a separate command-line management interface. It supports Exchange Online administration, including security features. However, Microsoft’s supplied notice does not confirm that PowerShell is unaffected, so it should be treated as a possible alternative rather than a verified workaround.
Cybersecurity News previously covered a Microsoft Exchange admin center outage tracked as EX1051697. That incident involved HTTP 500 errors and reports of an alternative portal address helping some administrators. Those earlier findings do not establish a working fix for EX1500900.
The publication also reported a separate Exchange Online disruption tracked as EX1464935, which concerned broader service functionality. Its different incident number and reported impact underline why administrators should keep individual service events separate when assessing business disruption.
For now, the supported scope remains limited to the access failure described in the supplied announcement. Organizations should follow EX1500900 for confirmed impact, recovery progress, and any approved mitigation. Email delivery failures, if observed, need separate verification rather than being automatically attributed to this admin portal issue.
Cut every SOC alert investigation by 21 min. Power your SOC with instant IOC context for immediate response: Integrate TI Lookup into your SOC
The post Microsoft Exchange Admin Center Issue Blocks Web Portal Access to Admins With “Internal Server Error” appeared first on Cyber Security News.
Discover details of the Ledger hardware wallet hack. Learn how hackers modified devices with spy modules to steal user seed phrases and $80 million in crypto.
Related Posts:
The post The Devastating Ledger Security Breach appeared first on Daily CyberSecurity.
Explore how massive Apple Intelligence storage demands in macOS 27 Golden Gate face fierce backlash regarding enterprise security and user limitations.
Related Posts:
The post The Growing Backlash Against Apple Intelligence Integration appeared first on Daily CyberSecurity.
Discover the controversy surrounding ICANN gTLD applications for the .lan domain. Learn how this impacts OpenWrt and local network configurations worldwide.
Related Posts:
The post Controversy Surrounding the .lan Domain Application appeared first on Daily CyberSecurity.
Discover the MonsterCloud ransomware decryption fraud. Learn how Zohar Pinhasi allegedly deceived clients by secretly paying hackers for data recovery keys.
Related Posts:
The post The Reality of Ransomware Recovery Services appeared first on Daily CyberSecurity.
Entrar