Canonical has officially rolled out Ubuntu 24.04.5 LTS, the fifth maintenance update to the “Noble Numbat” long-term support release, delivering a fresh installation image packed with the latest security patches, bug fixes, and an upgraded hardware enablement stack built around the Linux 7.0 kernel.

For a distribution that underpins millions of servers, cloud instances, and desktops worldwide, this point release is less about flashy new features and more about keeping systems secure, stable, and current without forcing users through a disruptive version jump.

Ubuntu 24.04.5 LTS Released With Linux 7.0

The headline change in this update is the shift of the Hardware Enablement (HWE) kernel stack to Linux 7.0, pulled forward from the newer Ubuntu 26.04 LTS “Resolute Raccoon” release, alongside the Mesa 26.2 graphics stack for improved GPU support.

Systems running the General Availability (GA) kernel remain on the original 6.8 series that shipped with 24.04.0, ensuring long-term compatibility for enterprise deployments that avoid frequent kernel churn.

Meanwhile, the installation media also carries updated toolchain components, including GCC 14, glibc 2.39, Rust 1.75, and Python 3.12 as the default interpreter, keeping developers working with modern language runtimes out of the box.

This dual-kernel approach is a hallmark of Ubuntu’s LTS strategy: administrators who prioritize stability can stick with the GA kernel, while those needing support for newer hardware, such as recent CPUs, GPUs, and peripherals, can opt into the HWE kernel that now tracks Linux 7.0.

Canonical’s Livepatch service already lists coverage for the 7.0 HWE kernel across x86-64, so supported configurations can patch high-severity kernel vulnerabilities without a reboot on supported configurations.

True to Canonical’s stated philosophy for point releases, 24.04.5 folds a substantial batch of security corrections and high-severity bug fixes directly into the installer, meaning new installs won’t need to immediately pull down a large post-install update queue.

The release notes intentionally avoid mentioning specific CVEs or bug-tracker IDs. Therefore, security teams that need to verify specific patches against compliance requirements should directly cross-reference Canonical’s detailed release notes and the Ubuntu Security Notices archive.

For organizations managing large fleets, the practical takeaway is that reimaging with the new 24.04.5 media saves a round of downloads, while systems already running 24.04 and receiving regular updates will get the same fixes automatically over their next update cycle.

Release Component	Technical Specifications	Operational & Administrative Impact
HWE Kernel Stack	Upgraded to Linux 7.0 & Mesa 26.2	Provides updated hardware and GPU enablement from Ubuntu 26.04 LTS
GA Kernel Track	Retains Linux 6.8 series	Preserves long-term stability and compatibility for legacy enterprise servers
Core Toolchain	GCC 14, glibc 2.39, Rust 1.75, Python 3.12	Modernizes runtimes and compiler stacks for developers out of the box
Security & Livepatch	Direct patch integration & Livepatch support	Eliminates initial post-install download queues and reboots on x86-64
Flavors & Editions	9 official community desktop flavors updated	Synchronizes Kubuntu, Xubuntu, Budgie, and other variants to 24.04.5
Support Lifecycle	Standard support through May 2029 (ESM to 2034)	Five-year clock remains tied to the April 2024 initial LTS release

Ubuntu 24.04.5 LTS isn’t an isolated desktop-and-server release. Nine official flavors, including Kubuntu, Xubuntu, Ubuntu MATE, Lubuntu, Ubuntu Kylin, Ubuntu Studio, Edubuntu, Ubuntu Cinnamon, Ubuntu Budgie, and Ubuntu Unity, have simultaneously moved to version 24.04.5, each with flavor-specific release notes covering desktop environment tweaks and application updates.

Existing Ubuntu 22.04 LTS users will be offered an automatic upgrade path to 24.04.5 through Update Manager, and as with all Ubuntu version transitions, the upgrade remains completely free of charge.

One detail worth flagging for IT planners: the five-year maintenance clock for Ubuntu Desktop, Server, Cloud, and Core counts from the original 24.04 LTS release in April 2024, not from this September 2026 point release, meaning standard security support runs through May 2029.

The remaining community flavors carry a three-year support window from the same original release date. Organizations needing coverage beyond these windows can extend support through Canonical’s Expanded Security Maintenance (ESM), which pushes coverage out to a full decade for Ubuntu Pro subscribers.

For system administrators and security teams, Ubuntu 24.04.5 LTS represents the kind of incremental, security-hardened update that defines a mature LTS lifecycle: newer hardware support through the Linux 7.0 HWE kernel, a bundle of pre-baked security fixes, and no breaking changes to the underlying platform users have already deployed at scale.

Anyone running production Ubuntu 24.04 workloads should treat this as a routine but important update cycle, verify patch levels against the official release notes, and plan hardware-enablement kernel adoption based on their specific compatibility and support requirements.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Ubuntu 24.04.5 LTS Released With Linux 7.0 Kernel and Latest Security Updates appeared first on Cyber Security News.

IDScan.net, a Louisiana-based identity verification firm whose technology underpins age and identity checks for retailers, bars, and other Fortune 500 clients, has confirmed a data breach after a criminal marketplace began advertising more than 153 million driver’s licenses from the United States and Canada.

The company disclosed that it detected unauthorized access to its systems on or around September 1, 2026, and immediately began securing its environment while bringing in third-party forensic specialists to determine the scope of the intrusion.

IDScan.net Data Breach

The breach came to light not through IDScan.net’s own disclosure timeline alone, but through investigative reporting from security journalist Brian Krebs, who was alerted on August 31 to a new identity theft service called “Nexus” being advertised on the Russian-language cybercrime forum Exploit .

The seller offered Krebs his own Virginia driver’s license as a free sample to prove the data was genuine, a tactic that ultimately helped researchers trace the leak back to a widely used identity verification vendor.

The Federal Bureau of Investigation’s New Orleans field office has since opened a formal inquiry into the source of the leaked images, and IDScan.net says it is cooperating with federal law enforcement.

Nexus claims to hold identity documents on more than 170 million people across North America, including upwards of 153 million driver’s licenses, over 10 million identification cards, more than 3 million travel and international documents, and at least 579,000 medical cards .

A blank search on the platform returned roughly 11.5 million results pages, a figure consistent with the advertised totals, and researchers found that Canadian records alone exceeded 1.1 million, with Ontario accounting for nearly 474,000 of them .

Notably, the trove includes commercial driver’s licenses, Common Access Cards used for government facility entry, and even marijuana dispensary identification cards, suggesting the stolen dataset spans a far broader swath of government-issued and regulated IDs than a typical retail breach.

Perhaps most alarming is the claim from the operators behind Nexus that they have been “continuously exfiltrating new data for over a year” into a private database, with customers able to preview redacted records and photos before purchasing full access.

Krebs observed the platform’s driver’s license count climb by nearly 400,000 records within a single 24-hour window, suggesting the breach may still be active rather than a one-time historical dump.

High-profile individuals have reportedly been swept up in the exposure as well, including a record for U.S. Defense Secretary Pete Hegseth, underscoring the national security implications of a leak touching government officials alongside ordinary consumers .

Incident Parameter	Disclosed Technical Details & Scope	Operational & Risk Implications
Affected Entity	IDScan.net (Louisiana-based identity verification provider)	Outsources ID validation for retail, hospitality, and Fortune 500 clients
Exposed Database Size	170M+ total records; 153M+ driver’s licenses, 10M+ ID cards	Spans US and Canadian documents (1.1M+ Canadian, ~474K in Ontario)
Document Types	Driver’s licenses, CAC government cards, medical & dispensary IDs	Extends beyond consumer retail IDs to military and regulated credentials
Illicit Marketplace	“Nexus” service advertised on Exploit forum	Offers searchable previews with front/back, infrared, and UV scans
Breach Activity Window	Continuous exfiltration claimed over 1+ year; ~400K added in 24h	Active intrusion rather than a static legacy repository leak
Law Enforcement & Triage	FBI New Orleans field office formal inquiry; external forensics	Mandatory credit monitoring offered; cloud account access investigated

In its official notice, IDScan.net stated that an unauthorized third party may have accessed or copied customer information stored in accounts on its cloud platform, primarily full names and driver’s license or other government-issued identification numbers.

The company noted that while full access to the stolen data on dark web marketplaces required payment, it is notifying potentially impacted individuals out of caution and offering free credit monitoring and identity protection services.

Affected individuals can enroll or ask questions by calling 1-833-516-2980 between 8 a.m. and 8 p.m. ET on weekdays, or by writing to the company’s Metairie, Louisiana address.

IDScan.net urges anyone notified of exposure to stay vigilant against identity theft and fraud by closely reviewing credit reports and account statements for unfamiliar activity or billing errors.

Because driver’s license numbers are often used to verify identity for financial accounts, government benefits, and even notarized transactions, security researchers recommend freezing credit files with major bureaus and monitoring for new account applications in one’s name.

The incident illustrates a growing risk in the identity verification industry itself: as more businesses outsource “know your customer” checks to third-party scanning vendors, a single compromised provider can expose sensitive identity documents belonging to millions of people who never directly interacted with the breached company.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post IDScan Confirms Data Breach Following 153 Million Driver’s Licenses Leaked on the Dark Web appeared first on Cyber Security News.

Check Point Software has disclosed and patched two critical VPN-related vulnerabilities, CVE-2026-85102 and CVE-2026-85103, both carrying a maximum CVSS score of 9.8 and both capable of allowing unauthenticated remote code execution under specific conditions.

Check Point’s own research team uncovered the flaws, and the company says it has found no evidence of active exploitation or public proof-of-concept code as of this writing.

Check Point VPN Vulnerabilities

CVE-2026-85102 is rooted in improper certificate trust validation during VPN negotiation, tracked under CWE-295. According to Check Point’s advisory sk1000117, the flaw fails to properly validate the trust of a presented certificate, letting an unauthenticated attacker push VPN negotiation far enough to execute arbitrary code on the Security Gateway. This affects both Remote Access VPN and Site-to-Site VPN configurations.

CVE-2026-85103, by contrast, is a heap-based buffer overflow (CWE-122) that occurs while the product parses the ASN.1 structure of a VPN certificate. Detailed in advisory sk1000118, this bug lets a remote attacker trigger the overflow simply by sending a malicious certificate, potentially achieving code execution on both Quantum Security Gateway and Quantum Security Management systems.

The vulnerabilities affect Check Point Security Gateway, Security Management Server, and Spark Firewall deployments across multiple release branches, including R81.20, R82, and R82.10 with Jumbo Hotfix Takes below the newly patched builds, along with several end-of-support versions such as R80.40 and R81. Check Point has confirmed that R82.20 is not affected.

Notably, CVE-2026-85102 primarily impacts Security Gateways engaged in VPN connections, while CVE-2026-85103 spans both gateway and management infrastructure.

Organizations using Check Point Live Patch benefit automatically, since the protective rollout began on September 9, 2026. Administrators without Live Patch enabled must manually install the latest Jumbo Hotfix Accumulator for their branch, specifically R82.10 Take 44 or higher, R82 Take 126 or higher, or R81.20 Take 166 or higher, along with dedicated Spark Firewall builds.

For Site-to-Site VPN deployments that cannot patch immediately, Check Point recommends disabling implied VPN rules and restricting UDP ports 500 and 4500 to known peer IP addresses, though this workaround does not extend to Remote Access VPN, and no interim mitigation exists for locally managed Spark Firewalls.

These newly patched bugs are unrelated to the actively exploited CVE-2026-50751, an IKEv1 authentication bypass tied to Qilin ransomware activity disclosed earlier this year.

Given the critical severity and network-exploitable nature of both new flaws, security teams running Check Point infrastructure should prioritize patching immediately rather than waiting for confirmed in-the-wild exploitation.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Critical Check Point VPN Vulnerabilities Enable Remote Code Execution Attacks appeared first on Cyber Security News.

Microsoft has disclosed a new security flaw in Windows BitLocker, the operating system’s built-in disk encryption feature, that could let an attacker execute malicious code on a vulnerable device.

Tracked as CVE-2026-69449 and published on September 8, 2026, the vulnerability stems from a heap-based buffer overflow in BitLocker’s code and has been rated “Important” in severity, with Microsoft acting as the assigning CNA.

Windows BitLocker Vulnerability

According to Microsoft’s advisory, as detailed in the technical disclosure published by Microsoft, an authorized attacker who successfully exploits the flaw could gain the ability to execute arbitrary code locally, and the company’s FAQ notes that exploitation may also be achieved by an in-network attacker calling arbitrary endpoints, effectively broadening the risk beyond a purely local attack surface.

Independent tracking from Tenable corroborates the core description, characterizing the bug as a heap overflow that allows code execution once triggered, while assigning it a CVSS v2 base score of 6.5 under a vector requiring low attack complexity and medium-level authorization.

Despite the code execution impact, Microsoft’s Exploitability Index currently rates CVE-2026-69449 as “Exploitation Less Likely.” The vulnerability has not been publicly disclosed prior to this advisory, and there is no evidence of active exploitation in the wild as of the September 8 release date.

This places it in a lower-urgency bracket compared to fully unauthenticated, wormable remote code execution bugs, though enterprises relying on BitLocker for data-at-rest protection should not treat that classification as a reason to delay patching.

Microsoft credited security researchers Thanatos Tian of the Hong Kong Polytechnic University, wgg, and the individual known as @2st__ working with Diffract, alongside Zhiniang Peng of the Huazhong University of Science and Technology, for responsibly reporting the flaw through coordinated disclosure.

Vulnerability Parameter	Technical Detail & Specification	Operational Impact & Mitigation
CVE Identifier	CVE-2026-69449	Assigned by Microsoft (CNA)
Vulnerability Class	Heap-based Buffer Overflow	Local and in-network arbitrary code execution
Severity & Vector	Important (CVSS v2 6.5)	Low attack complexity, medium privilege requirement
Exploitation Likelihood	Exploitation Less Likely	No public disclosure or in-the-wild exploitation prior to release
Affected Platforms	Windows 10, Windows 11, Windows Server (2012–2025)	Broad client and server exposure (x64, 32-bit, ARM64)
Remediation Status	September 2026 Patch Tuesday Cumulative Updates	Distributed via platform-specific KBs (e.g., KB5124012, KB5122871)

The vulnerability affects an unusually broad swath of the Windows ecosystem, spanning both client and server platforms.

Impacted systems include Windows 10 across versions 1607, 1809, 21H2, and 22H2 for both x64 and 32-bit builds; Windows 11 versions 23H2, 24H2, 25H2, and the newer 26H1 for x64 and ARM64 architectures; and Windows Server releases from 2012 and 2012 R2 through Server 2016, 2019, 2022, and the latest Server 2025, including their Server Core installation variants.

Microsoft has already shipped cumulative security updates addressing each affected build as part of its September 2026 Patch Tuesday cycle.

Fixes are distributed through distinct KB packages depending on platform, such as KB5124012 for Windows 11 26H1 systems, KB5122871 for Windows Server 2025, KB5122882 for Windows Server 2022, KB5122876 for Windows Server 2019, and KB5123099 covering Windows Server 2016 and legacy Windows 10 1607 builds, among others listed in the official update catalog.

Given BitLocker’s role in protecting sensitive data across enterprise fleets, laptops, and servers, IT administrators are strongly advised to prioritize deployment of the relevant September 2026 cumulative updates without delay.

Verifying the post-update build number against Microsoft’s published fixed versions for each product line remains the most reliable way to confirm remediation and reduce exposure to this newly documented BitLocker weakness.

The post Windows BitLocker Vulnerability Allows Attackers to Execute Malicious Code Remotely appeared first on Cyber Security News.

A proof-of-concept zero-click worm dubbed “WeWorm” that it says can spread through WeChat voice calls on both iOS and Android, compromising a target’s WeChat account in seconds without the victim answering the call.

Calif says the bug was reported to Tencent in July and that Tencent has since mitigated the exploit for users, but the research still serves as a stark warning about how mobile messaging apps can become wormable attack surfaces at planetary scale.

WeChat is not a niche target. Tencent says Weixin and WeChat together exceeded 1.4 billion monthly active users as of the end of Q1 2026, while WeChat’s own site describes the platform as serving over 1 billion users with chats and calls across major mobile and desktop platforms.

That sheer reach is what makes Calif’s demonstration so alarming: a memory-corruption flaw in the app’s VoIP stack is not just another messaging bug, but a potential entry point into one of the world’s most deeply embedded communications ecosystems.

According to Calif’s public research listing, WeWorm is described as “the first zero-click worm to spread through WeChat calls across iOS and Android,” and it was published on September 8, 2026, as part of the company’s Android-tagged research work.

Calif frames the finding not as a theoretical edge case but as a live demonstration of how a trusted messaging relationship can be weaponized, with one compromised contact becoming the launch point for attacks against everyone in that person’s social graph.

The company’s demo chain reportedly used three phones to prove cross-platform propagation. A Pixel 10a was used as the initial attacker device, which then called an iPhone 17e and exploited the flaw while the call was still ringing; the compromised iPhone was then used to call another Pixel 10a, which was reportedly taken over in the same way.

In practical terms, that is the textbook definition of a wormable condition in a communications app: the attacker calls the victim, the victim becomes the attacker, and the infection path continues with almost no friction.

What makes the scenario especially dangerous is the “zero-click” aspect. Calif says the victim does not need to answer the call or interact with the phone at all for exploitation to succeed, and even if the person does answer, they hear nothing while the compromise still goes through.

That claim places WeWorm in the most feared class of mobile exploits, where normal user caution offers little protection because there is no malicious link to avoid and no attachment to reject.

Calif also says exploitation yields full control of the victim’s WeChat account, including the ability to read and send messages, place calls, and act on the user’s behalf inside the app.

On its own, account takeover at that level would already be severe for identity abuse, surveillance, fraud, and lateral targeting; chained with additional device-level bugs, Calif says the same access could be extended to full control of the underlying Android or iOS device.

The company specifically links that possibility to its broader AI-assisted exploit research, including Android work such as OEMpocalypse, which it has presented as a path from app-level access to root on several vendor ecosystems.

One condition slightly narrows the attack surface: the attacker must already be on the victim’s friend list. But Calif argues that this is a weak barrier in real-world conditions because once a single trusted contact is compromised, that person’s account can be used to reach additional friends, turning the victim’s social trust network into the worm’s propagation layer.

That is a familiar and troubling pattern in modern communications security, where safety features and trust assumptions designed for convenience can become force multipliers once an adversary gets an initial foothold.

The technical root cause, Calif says, is a memory-corruption bug in WeChat’s VoIP stack, though the company is withholding full exploit details until a later conference presentation.

That restraint matters because memory-corruption flaws in real-time communications code are among the most sensitive bug classes in mobile security, especially when they sit inside call-handling paths that process network data before a user takes any action.

Calif further suggests that this bug is only one example of a broader class of “unconventional attack surfaces” spread across messaging apps, hinting that similar issues may exist in other platforms with rich calling and media features.

WeWorm may be a demo, but its significance is real. Calif has effectively shown that mobile messaging worms are no longer a distant nightmare or a plot device for conference talks; they are a practical research outcome in 2026, built against one of the world’s largest communications platforms and developed at AI speed.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post WeWorm – First 0-Click Worm Spreading Through WeChat Calls Across iOS and Android appeared first on Cyber Security News.

The OpenVPN project has shipped version 2.7.7, a security-focused release that patches seven distinct vulnerabilities spanning the software’s core reliability layer and its Windows-specific service components.

The update, released on September 3, 2026, addresses issues ranging from denial-of-service conditions to buffer overreads and configuration bypasses that could allow attackers to run unauthorized VPN configurations.

The most broadly impactful fix, tracked as CVE-2026-84732, targets OpenVPN’s reliability layer, a component responsible for managing TLS handshakes and acknowledgment packets.

The flaw combined two separate bugs: an unbounded reliable TLS timeout and improper handling of acknowledgments for packets that could never legitimately be outstanding. Both issues were discovered by security researcher Mark Bregman of Fox-IT, and since the reliability layer is shared across all supported platforms, the fix benefits Linux, Windows, and macOS deployments alike.

Six of the seven vulnerabilities specifically affect Windows installations, reflecting how deeply OpenVPN’s Windows service architecture had accumulated edge-case weaknesses.

OpenVPN Fixes 7 Security Flaws

CVE-2026-84256 involved incorrect command-line quoting in the CreateProcess() function, where characters with special meaning to cmd.exe could, in combination with a validation script and a rogue certificate authority, lead to unexpected behavior.

A related flaw, CVE-2026-84226, affected the tapctl utility, which previously invoked netsh.exe without specifying its full file path, a gap that researchers at BreachX Zero Day Labs identified using their Typhon AI Mil v2 tooling.

Local privilege abuse was also on the table. CVE-2026-82312 stemmed from OpenVPN’s use of NULL discretionary access control lists (DACLs) on system objects, including the service exit event and the netsh.exe guard semaphore.

This design flaw enabled a local denial-of-service scenario in which one logged-in user could interfere with another user’s OpenVPN session by blocking the semaphore or triggering spurious events, though the issue applies only to setups that skip the interactive service or rely on the automatic Windows service.

Two additional Windows flaws affected openvpnserv, the Windows service component. CVE-2026-78221 caused a buffer overread when internationalized domain names using UTF-8 encoding were processed, because the NRPT domain size passed to the function was incorrect.

Separately, CVE-2026-78043 revealed that openvpnserv’s configuration path validation failed to block forward slashes, even though Windows file-open APIs treat them as valid path separators. This mismatch could let an attacker slip past administrative restrictions and force openvpn.exe to launch a configuration file it was never authorized to run.

Rounding out the list, CVE-2026-81738 fixed an off-by-one error in write_dhcp_search_str(), where specially crafted DHCP search-domain options could overflow a temporary buffer by a single byte, a bug credited to researchers Andre Kropp of Nexory and ChinhNguyen.

CVE ID	Component	Platform	Issue Type	Impact
CVE-2026-84732	Reliability layer	All platforms	Unbounded reliable TLS timeout + acking non-outstanding packets	Potential DoS via TLS handshake mishandling
CVE-2026-84256	CreateProcess()	Windows	Improper command-line quoting of cmd.exe special characters	Misbehavior when combined with validation script + rogue CA
CVE-2026-84226	tapctl utility	Windows	netsh.exe invoked without full path	Potential binary hijacking/path abuse
CVE-2026-82312	Service exit event / netsh guard semaphore	Windows	NULL DACL on system objects	Local DoS — one user can interfere with another user’s OpenVPN process
CVE-2026-78221	openvpnserv	Windows	Incorrect NRPT domain size with UTF-8 IDN domains	Buffer overread
CVE-2026-78043	openvpnserv	Windows	Config path validation doesn’t block ‘/’ separator	Bypass of admin-restricted config paths, unauthorized config execution
CVE-2026-81738	write_dhcp_search_str()	Windows	Off-by-one in temp buffer guard	Single-byte buffer overflow via crafted DHCP options

Beyond the CVE fixes, OpenVPN 2.7.7 adds a Linux-specific improvement that validates netlink replies against the originating request, an enhancement suggested by researcher Joshua Rogers.

The release also reduces the number of future keys retained under the EPOCH data-channel format from sixteen to four, easing log noise and resource usage on high-throughput links, alongside several networking bug fixes affecting TCP handshakes, UDP checksum handling, and OpenSSL’s HMAC key management.

Administrators running OpenVPN on Windows should prioritize this update given the concentration of local-privilege and configuration-bypass flaws, while all users benefit from the reliability-layer patch. The release notes and full CVE details are published on the OpenVPN Community Wiki’s security announcements page.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post OpenVPN Fixes 7 Security Flaws Affecting VPN Connections and Windows Systems appeared first on Cyber Security News.

The cybersecurity industry is confronting a threat landscape that is changing faster than most defenders can keep track of. New data from Epoch AI shows that critical and high-severity vulnerability disclosures from major technology firms have gone vertical since the beginning of this spring, climbing from a baseline of a few hundred a month to well over 600, with critical-severity CVEs alone jumping from single digits to more than 600 in recent months.

By June 2026, twenty-one notable organizations, including Microsoft, Google, Apple, Adobe, Oracle, Cisco, and IBM, disclosed around 1,500 high- and critical-severity CVEs, more than 3.5 times the previous monthly record set before the release of Anthropic’s Claude Mythos Preview.

Critical Software Vulnerabilities Surge

That surge did not stop there; by July, disclosures reached roughly 2,500, nearly five times the pre-Mythos baseline and 60 percent above June’s already record-breaking total.

Researchers point to Anthropic’s Project Glasswing, an AI-powered vulnerability discovery initiative, as a major driver behind the spike, with the effort reportedly surfacing more than 10,000 high- or critical-severity flaws, many of which have not yet been individually disclosed.

Whether this reflects a genuine increase in exploitable weaknesses or simply a change in how vulnerabilities are found and classified remains uncertain, but analysts agree that AI-assisted discovery tools have fundamentally altered the pace at which flaws surface.

Compounding the disclosure surge is a parallel collapse in the time attackers need to weaponize new flaws. According to ZeroDayClock, the zero-day rate, meaning the share of exploited vulnerabilities attacked on or before the day of public disclosure, has climbed to nearly 87 percent, up roughly 60 percent from last year and almost quadruple the rate recorded in 2020.

The median time to exploit now sits at around one day, and some researchers project it could shrink to just one minute by next year. As recently as 2018, the median gap between disclosure and first observed exploitation stretched to 771 days; by 2023 that window had fallen to roughly six days, and by 2024 it was down to hours.

The so-called exploit survival curve, which tracks what percentage of eventually-exploited CVEs remain unexploited over time, now falls to zero within about 1.5 months of disclosure, reads the report.

In 2022, half of all exploits that would ever be weaponized were still unexploited at the 1.5-month mark, and even at three months a substantial share had gone untouched. Today, defenders effectively have no cushion once a flaw becomes public.

Security teams prepared to patch cycles measured in weeks are now operating in an environment where exploitation can begin before a fix is even available.

Ransomware operators have already adapted, with more than half of ransomware-linked CVEs in 2025 first identified through zero-day exploitation, up sharply from the prior year.

Industry analysts note that AI is reshaping both sides of the equation, accelerating offensive discovery while also promising to strengthen automated defense and detection capabilities. For now, organizations that delay patching by even a few days are increasingly likely to find that attackers got there first.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Critical Software Vulnerabilities Surge From Under 100 to More Than 600 a Month appeared first on Cyber Security News.

CrowdStrike has unveiled SafeMind, a family of purpose-built security models and harnesses that the company is calling the first agentic system engineered specifically for cyber defenders.

Announced at Fal.Con 2026 in Las Vegas, the launch marks a strategic pivot away from generic frontier AI models toward a dedicated offensive-defensive framework built to operate natively inside the CrowdStrike Falcon platform.

The system emerges from CrowdStrike’s newly established Cyber Superintelligence Lab and represents one of the most ambitious applications of agentic AI in enterprise security to date.

CrowdStrike Launches SafeMind

What sets SafeMind apart from conventional large language model deployments is its dual-model design. Red Tempest, the offensive component, is trained to emulate advanced AI-driven adversaries and probe for exploitable attack paths, while Blue Solano, the defensive counterpart, is built to close those gaps using battle-tested protection measures drawn from real-world incident response.

Rather than functioning as isolated tools, the two models operate inside harnesses that pit them against each other in a continuous, self-improving loop, allowing the system to sharpen its detection and remediation capabilities with every cycle.

Crucially, these harnesses are also compatible with other frontier and open-source models, giving security teams flexibility in model choice without sacrificing cost efficiency.

SafeMind’s differentiation lies heavily in its training foundation. The models were built using telemetry from CrowdStrike’s Falcon sensors, described as the largest pureplay cybersecurity dataset and edge install base in the industry, combined with threat intelligence, Falcon Complete managed detection and response annotations, and fifteen years of frontline incident response fieldwork.

This grounding in operational breach data, rather than generic internet-scale text corpora, is central to CrowdStrike’s argument that purpose-built security models outperform repurposed general-purpose AI systems in adversarial cyber scenarios.

CrowdStrike developed SafeMind in partnership with NVIDIA, using the NVIDIA Nemotron open model family as its foundation, while CoreWeave’s AI Cloud powers both training and inference workloads. NVIDIA CEO Jensen Huang framed the collaboration as part of a broader industry shift, noting that cyber defense is becoming one of the most compute-intensive applications of AI as attackers and defenders both race to scale their use of automated systems.

CrowdStrike CEO George Kurtz echoed that sentiment, stating that the future of cybersecurity “won’t be defined by AI that simply identifies threats, it will be defined by AI that defeats them”.

CrowdStrike’s internal evaluations claim SafeMind delivers a 29 percent higher detection rate than leading frontier and open-source models, along with six-times-faster end-to-end remediation and 99 percent cost savings on detection and remediation workflows.

Dr. Bartley Richardson, CrowdStrike’s chief AI and autonomous systems officer, described the launch as the foundation for the next decade of AI-driven security, emphasizing that CrowdStrike now controls the entire stack “from sensor to harness to model”.

Standalone access to SafeMind’s models and harnesses will roll out through CrowdStrike’s Project QuiltWorks program, offering trusted enterprise customers a pathway to integrate the agentic system beyond the native Falcon deployment.

As AI-enabled attacks continue to scale, SafeMind signals a broader industry move toward autonomous, closed-loop defense systems designed to act on risk rather than merely flag it, positioning CrowdStrike at the forefront of the agentic security race.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post CrowdStrike Launches SafeMind Cybersecurity’s First Agentic System Built for Defenders appeared first on Cyber Security News.

ASUS has issued an urgent security update for ASUS Control Center Enterprise (ACC) after researchers uncovered a maximum-severity vulnerability that lets remote attackers seize complete administrative control over the platform and every device it manages, without needing a password or any user interaction.

Tracked as CVE-2026-75754, the flaw carries a CVSS 4.0 score of 10.0, the highest possible rating, reflecting how easily it can be exploited over a network and the catastrophic scope of what an attacker can achieve once inside.

ASUS Control Center Vulnerability

The vulnerability actually stems from a chain of three separate weaknesses working together. ASUS Control Center is missing authentication on a critical function, meaning certain sensitive operations can be triggered by anyone who can reach the service over the network.

That gap is compounded by a server-side request forgery flaw, which lets an attacker send a specially crafted HTTP request to trick the system into exposing its own encryption key. Once that key is retrieved, a local service on the host automatically enables an SSH listener on TCP port 2222, effectively opening a hidden backdoor into the machine.

The final piece of the chain is arguably the most damaging: ASUS Control Center contains hard-coded credentials baked into the software itself. Attackers who obtain the encryption key can use these fixed credentials to log directly into the newly opened SSH port and land a full root shell, the highest level of system access available on the machine.

From there, intruders can read, modify, or delete any data stored in ACC, and because the platform is designed to centrally manage fleets of servers, PCs, and workstations, a single compromised ACC instance can hand attackers remote control over an entire corporate IT environment.

The flaw affects all versions of ASUS Control Center Enterprise up to and including 4.0.0.2. ASUS is urging every organization running the software to update immediately to version 3.1.0.9 or later, and confirms further fix details are posted on its official Security Advisory page.

Enterprises unable to patch right away should isolate ACC management interfaces from public networks, block inbound and outbound traffic on port 2222, and audit hosts for unexpected SSH listeners as an interim safeguard.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post ASUS Control Center Flaw Allows Attackers to Gain Full Admin Control of the System appeared first on Cyber Security News.

Attackers are actively exploiting an unauthenticated remote access flaw in MikroTik RouterOS, and network administrators worldwide are being urged to patch their devices immediately before compromise turns into a full network takeover.

MikroTik confirmed on September 3, 2026, that it had discovered a serious security vulnerability affecting RouterOS and had already shipped fixes across every release channel, including 7.25 beta 3, 7.24.2 stable, 7.23.4 long-term, and 6.49.21 long-term.

The vendor deliberately withheld technical specifics in its initial advisory, stating plainly that it was “not currently publishing detailed information” in order to give administrators time to update before attackers could reverse-engineer the flaw from public disclosure.

Despite that caution, exploitation began almost immediately, and forum users and researchers quickly pieced together the attack mechanics on their own.

MikroTik RouterOS Vulnerability

According to detailed discussion on the official MikroTik support forum, the vulnerability lives inside a core library used by multiple RouterOS services, meaning any exposed service built on that codebase can be leveraged as an entry point.

One forum contributor who reverse-engineered the issue confirmed it is tied to SSH and grants any unauthenticated remote attacker direct shell access to the device, regardless of whether the router relies on password authentication or SSH key-based login.

In practical terms, if the SSH service is reachable from the internet or an untrusted network, the router is vulnerable until it receives the patch, with no additional credential theft or user interaction required.

Latvia’s national CERT issued its own alert corroborating a marked increase in attacker activity specifically targeting MikroTik routers, urging organizations and home users alike to update immediately to the patched builds MikroTik released. The agency’s guidance mirrored MikroTik’s own version list, reinforcing that the fix spans both the newer 7.x stable and legacy long-term branches.

Evidence of live exploitation surfaced quickly within the MikroTik user community. One administrator reported on Reddit that around September 2, 2026, at 08:00 UTC, an unauthorized user account named “ops” was created by another rogue account labeled “0,” granted both write and policy permissions, with the intrusion traced back to an SSH connection originating from the IP address 82.192.72.4.

The administrator noted that while the rogue account appeared to be used mainly for logging in and no obvious malicious scripts were visible in the configuration, the team suspected deeper compromise that RouterOS itself could not detect, ultimately requiring a full netinstall to guarantee the devices were clean.

RouterOS now includes a built-in detection mechanism to help flag this exact scenario. After upgrading, the operating system automatically inspects the full configuration at startup and sets a device to “Flagged” status if it finds signs of unauthorized tampering, logging a critical entry in the system log.

Devices in this state face operational restrictions, including a block on enabling new scheduler entries, SOCKS proxy, PPTP, L2TP, IPsec, proxy, and SMB configurations, until an administrator performs a manual audit.

MikroTik’s guidance is straightforward: if a device shows as flagged, assume it has been compromised, audit every configuration line, rotate all passwords, and only then clear the flagged state.

Even routers that never show a flagged status should not be considered safe by default; MikroTik and independent researchers both recommend manually reviewing configurations for unrecognized users, scripts, or scheduled tasks after updating, since some compromise artifacts may not trigger the automated detection.

Restricting SSH and other management interfaces from the public internet, enforcing key-based authentication, and limiting administrative access to trusted management networks remain essential complementary defenses while the patch rolls out fleet-wide.

Given the scale of MikroTik’s install base and the confirmed low barrier to exploitation, security teams should treat this as an urgent, internet-facing remote code execution scenario rather than a routine maintenance update.

Upgrading to 7.24.2, 7.23.4, or 6.49.21 (or later), auditing every device regardless of flagged status, and hardening remote management access should be treated as immediate priorities rather than items for the next maintenance window.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Hackers Exploiting MikroTik RouterOS Vulnerability in the Wild to Gain Complete Network Access appeared first on Cyber Security News.

A newly discovered zero-day vulnerability in Magento Open Source and Adobe Commerce is being actively exploited by attackers to seize full control of online stores, and there is still no official patch available.

Dutch e-commerce security firm Sansec disclosed the flaw, dubbed StyleSmuggler, on September 5, 2026, warning that unauthenticated attackers can achieve remote code execution on vulnerable installations and that live attacks began the previous day .

The company said it was publishing its findings early, before completing its full technical analysis, “because stores are being compromised right now”.

StyleSmuggler affects every current version of Magento and Adobe Commerce, including the latest 2.4.9 release, and requires no authentication whatsoever to exploit.

Sansec reproduced the complete unauthenticated attack chain on clean installations of Magento Open Source 2.4.7, 2.4.8, and 2.4.9, confirming the bug is not tied to any single outdated build.

Disturbingly, the first identified victim was running 2.4.6-p15 with July and August 2026 security patches fully applied, meaning fully patched stores were compromised just as easily as neglected ones.

As of September 6, Adobe has not issued an advisory, assigned a CVE identifier, or released any official fix or workaround, and the company’s most recent Commerce security bulletin still dates to August 11.

The exploit unfolds in two distinct stages that abuse Magento’s own template rendering and email systems rather than a single obvious injection point. In the first stage, attackers plant malicious PHP code inside a file that Magento itself writes during normal operation, such as a payment failure report, by manipulating “styles” properties within a GraphQL request to slip past existing input sanitization.

Magento and Adobe Commerce 0-Day RCE

Independent analysis from Magento hosting firm Disrex Group, which handled two breached stores, found that a crafted directive inside the injected text forces a chain of Magento’s own classes to execute code that was only ever meant to run through the command-line dependency-injection compiler, ultimately including the attacker-poisoned log file.

The second stage triggers execution. Sansec found that StyleSmuggler deliberately causes Magento to send its standard “Payment Transaction Failed Reminder” email, and the poisoned code runs the moment Magento renders that message internally, meaning nobody has to open or even receive the email for the attack to succeed.

Once triggered, a PHP dropper cycles through six different PHP functions until it finds one capable of spawning a process, then downloads and launches a persistent implant. Disrex described the malware as a small, statically linked Rust binary of roughly 1.9 megabytes, compiled for both x86-64 and ARM64 architectures, disguised as a Linux kernel thread named “[kworker/u:8:0]” and restarted every five minutes through a cron entry written directly into the crontab spool file to avoid leaving normal system logs.

Detecting an infection is harder than it sounds because the malware actively evades naive checks. A genuine Linux kernel worker thread is owned by root and consumes no resident memory, so any bracketed “[kworker]” process running under a website’s own user account with real memory usage is a red flag.

Disrex also discovered that the binary running in memory sometimes differs from the file sitting on disk, meaning defenders should hash both the file and the live process to be thorough.

On one compromised store, the implant made no outbound internet connections at all, instead opening 28 simultaneous connections to the site’s own Redis instance to read live Magento session data, which let it operate almost invisibly to network-based monitoring.

Sansec’s own detection guidance searches Magento’s var/report directory for a marker string, but Disrex found both of its breached stores were actually poisoned through var/log/system.log instead, meaning administrators need to check both locations.

With Adobe’s next scheduled security release set for September 8 and no confirmation it will address this flaw, store owners are left relying on stopgap measures. Sansec recommends temporarily disabling GraphQL entirely for stores that don’t rely on headless or progressive web app storefronts, since classic and Hyvä themes generally don’t need it.

Disrex, security researcher ProxiBlue, and vendor Graycore have each independently published unofficial code patches that guard specific Magento classes and email template functions, though all three stress these are hardening measures rather than a genuine fix, and Disrex specifically warns its rules only block the current attack traffic pattern, not the underlying vulnerability.

Server-level protections that don’t depend on understanding the exploit chain at all, such as disabling PHP’s proc_open function and mounting temporary directories with noexec, have also proven effective at stopping the dropper from launching its payload.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Hackers Actively Exploiting Magento and Adobe Commerce 0-Day RCE Vulnerability appeared first on Cyber Security News.

Microsoft is investigating an ongoing issue causing some Windows users to face significant delays or outright failures when launching the Microsoft Teams desktop client.

The company acknowledged the problem, tracked internally as TM1466820, and confirmed it remains unresolved as engineers continue digging through service logs to find a root cause.

According to Microsoft’s incident notice, affected users encounter trouble specifically during the first launch of Teams on a Windows device. Some cannot load the client at all, while others experience delays stretching up to two minutes before the app becomes usable.

For an application many organizations rely on for daily communication, even a two-minute hang at startup can disrupt morning routines, delay meeting joins, and frustrate employees trying to check urgent messages.

Microsoft has classified the issue’s scope as affecting “some users” within impacted organizations, particularly those opening Teams to view new messages. The company noted that impact varies across tenants, meaning not every organization or every user within an affected organization will necessarily notice the slowdown.

While a permanent fix is being developed, Microsoft has recommended workarounds to keep productivity moving. Affected users can switch to Microsoft Teams on the web through a browser, or use the Teams mobile app, both of which reportedly remain unaffected by the desktop client’s loading problem. These alternatives don’t fix the underlying issue but let employees stay connected until Microsoft rolls out a resolution.

In its most recent update, posted at 8:41 AM on September 4, 2026, Microsoft said its analysis of service logs and telemetry data has so far been “inconclusive.” Engineers have not yet pinpointed why the desktop client is struggling to load on some Windows machines.

Microsoft Teams Desktop Client Fails

To move the investigation forward, Microsoft is reaching out directly to a subset of impacted users, requesting client-side logs from their devices. The company expects these logs will help isolate the underlying trigger and clarify what remediation options are viable.

This is not the only Teams-related disruption Microsoft has grappled with recently. Earlier in the year, a regression in the Teams client’s build-caching system caused similar launch failures, which Microsoft resolved by reverting a faulty service update.

Separately, Windows 11 users on ARM-based devices, such as Surface Pro and Surface Laptop models, have faced Teams and Outlook launch failures tied to an August security update, an issue Microsoft has since mitigated through a Microsoft Store update.

For now, IT administrators managing Windows fleets should monitor the Microsoft 365 admin center’s service health dashboard for updates on TM1466820 and consider proactively informing staff about the web and mobile workarounds.

Microsoft has not provided an estimated resolution timeline, but its outreach for client logs suggests the investigation is entering a more targeted, evidence-gathering phase rather than a quick patch rollout.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Microsoft Teams Desktop Client Fails to Load on Windows System – Microsoft Investigating appeared first on Cyber Security News.

A human attacker armed with frontier artificial intelligence models breached an enterprise network and seized root credentials in under 10 hours, a timeline that would normally take human red teams roughly two weeks to complete, according to a new incident response report from Palo Alto Networks’ Unit 42.

The threat actor told Unit 42 investigators during ransom negotiations that they relied on frontier AI models paired with attack-specific agentic AI frameworks to automate the intrusion.

Rather than manually executing each stage of the attack, the operator directed AI agents to monitor, evaluate, act, and re-plan in real time, compressing more than 50 distinct MITRE ATT&CK techniques into a single automated loop.

Unit 42 noted that the attack did not rely on a zero-day exploit or unusually sophisticated tradecraft, but instead achieved its speed and scale purely through AI-assisted operational efficiency.

AI Agents Breach Company Network

Once the agents gained initial access by breaching a publicly accessible web service, they tunneled into the network and deployed an automated reconnaissance agent to map internal microservices.

From there, sub-agents combed through enterprise code repositories, harvesting hard-coded tokens and service passwords. The attacker then used those exposed tokens to infiltrate the organization’s secrets management system, extracting master administrative credentials that granted root-level access across the environment.

The agents did not stop at credential theft. They hijacked the company’s CI/CD pipeline through custom workflows to exfiltrate cloud access keys and attempted to plant backdoors inside Terraform infrastructure-as-code configurations, an effort that was ultimately blocked by branch-protection controls.

Using the stolen cloud keys, the attacker also seized control of the victim’s AI infrastructure, repurposing the company’s own compute resources to support future stages of the attack.

Unit 42 identified several telltale signs of AI-driven operations, including parallel calls to multiple large language models, structured Markdown files used to pass information between agent sessions, and custom scripts bearing UI elements consistent with AI-generated code.

In an unusual twist, the attacker also directed the agents to compile an 80-page technical audit of the victim’s security weaknesses, effectively automating a full penetration-testing report as leverage.

Researchers warned that adversaries are increasingly likely to fold autonomous AI agents into their toolkits, since the technology helps establish redundant persistence across SSH keys, cloud identities, and CI/CD pipelines simultaneously.

To counter machine-speed attacks, Unit 42 recommends that organizations deploy synchronized containment playbooks that can instantly revoke credentials and freeze pipelines, treat AI models and API keys as core infrastructure requiring strict governance, and enforce mandatory multi-party code review on infrastructure-as-code repositories to block automated backdoor injection.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post AI Agents Breach Company Network in Under 10 Hours and Steal Root Credentials appeared first on Cyber Security News.

Microsoft has introduced Project Zenith, a new developer-optimized Windows 11 experience built for a class of high-memory PCs capable of running large AI models directly on-device, marking a significant shift away from cloud-dependent AI development workflows.

Announced as a follow-up to commitments made at Build 2026, Project Zenith targets developer-class hardware equipped with at least 64 GB of unified memory and memory bandwidth exceeding 250 GB per second.

That hardware profile allows developers to run AI models with more than 30 billion parameters locally and without usage metering, reducing reliance on cloud-based token consumption during experimentation and coding tasks.

The first devices supporting Project Zenith will ship with AMD’s Ryzen AI Halo platform, with additional OEM and silicon partners expected to join in the coming months.

Rather than being a separate product, Project Zenith is a preconfigured Windows setup layered on top of ongoing baseline improvements Microsoft has been rolling out to Windows 11 throughout the year, including refinements to Search, File Explorer, and system memory efficiency. Devices running Project Zenith inherit these performance gains while adding a development-first configuration out of the box.

That configuration includes Windows Terminal and Visual Studio Code pinned to the taskbar by default, along with pre-tuned settings across File Explorer, Search, Start, and the taskbar.

File Explorer ships with file extensions, hidden files, full title-bar paths, and long-path support enabled, while distractions such as recently used file suggestions and sync provider prompts are switched off. Search and Start come with Command Palette enabled and notification clutter minimized, aiming for what Microsoft describes as a calmer, distraction-free workspace.

Windows Subsystem for Linux also plays a central role in the initiative. Building on last year’s open-sourcing of WSL, Microsoft has integrated WSL containers, giving developers a native way to build, run, and manage Linux containers without leaving Windows.

From a security and platform-architecture standpoint, Project Zenith devices are designed to support agentic development workloads using Microsoft’s Execution Containers (MXC), which combine OS-enforced identity controls with containment and enterprise-grade manageability for AI agents.

Microsoft frames this as essential groundwork for a computing era where autonomous agents increasingly write, test, and execute code, arguing that a secure, isolated foundation is necessary before agentic workflows can be trusted at scale in professional environments.

Microsoft positions the initiative as an economic and architectural shift in how AI-assisted development happens: offloading capable models to local hardware for routine tasks while reserving frontier cloud models for harder problems.

The company says Project Zenith is an evolving effort shaped directly by developer feedback, with hardware variety expected across OEM partners even as the core “ready-to-code” promise stays consistent.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Microsoft Unveils Project Zenith Windows PCs That Can Run 30B+ AI Models Locally appeared first on Cyber Security News.

Microsoft has confirmed a fresh Exchange Online incident, tracked as EX1467029, causing delays for users sending and receiving email messages from external domains.

The company first acknowledged the disruption on September 4, 2026, flagging it as a service degradation issue affecting Exchange Online, one of the most widely used business email platforms in the world.

According to Microsoft’s service health updates, the outage began around 3:49 PM GMT+5:30 and has continued through multiple status revisions issued that afternoon, with updates posted at 4:06 PM, 4:33 PM, and 5:56 PM.

Affected users have reported intermittent “Server busy” errors when attempting to communicate with recipients outside their own organization, a symptom that typically signals backend processing delays rather than a complete mail-flow failure. Microsoft has classified the event as an incident, a designation the company reserves for issues with noticeable, widespread user impact rather than isolated glitches.

In its advisories, Microsoft said its engineering teams have identified that anti-spam protections may be compounding the problem for a subset of affected accounts, effectively slowing down legitimate mail even further as filtering systems interact with the underlying fault.

The company noted it is “continuing to analyse the behaviour and review service telemetry to better understand the underlying cause and determine the most effective mitigation path,” but has not yet provided a fixed timeline for full resolution.

Notably, this is not an isolated event. Exchange Online has suffered a string of disruptions in recent months, including a major multi-day outage tracked as EX1464935 that began August 31, 2026, and caused authentication failures, mailbox search problems, and delayed message delivery across the service before Microsoft declared it fully mitigated on September 3.

That earlier incident was traced to a fault in a core authentication component shared across multiple Microsoft 365 services, requiring engineers to test and gradually roll out remediation across affected infrastructure.

The recurrence of email delivery problems within days of the previous outage’s resolution raises fresh questions about the resilience of Microsoft’s cloud email backbone, which underpins communications for millions of enterprises worldwide.

Organizations relying on Exchange Online for time-sensitive external communication, such as customer support, vendor coordination, or security alerting, may want to monitor the Microsoft 365 admin center’s Service Health dashboard directly for real-time updates tied to issue ID EX1467029.

Security teams should also be aware that prolonged mail delays can create downstream risks, including missed threat notifications, delayed multi-factor authentication emails, and backlog-related phishing attempts that exploit user confusion during outages.

Until Microsoft confirms a root cause and rollout of a permanent fix, administrators are advised to check affected mailboxes for delivery backlogs and avoid resending messages unnecessarily, as duplicate sends can further strain the recovering mail queues. Cyber Security News will continue tracking this incident as Microsoft releases further updates.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Microsoft Confirms New Exchange Online Outage Delaying Emails from External Domains appeared first on Cyber Security News.

Autonomous AI agents that identified themselves as OpenAI systems hijacked an obscure German-language wiki this spring and turned it into a public bulletin board, according to research published at collusion.wiki.

The investigators documented about 18,000 posts from agents that colluded on a timed web-retrieval task, sharing answers, environment notes, restriction workarounds, task shortcuts, and cover-up tactics even though writing to the internet was blocked.

The board sat on DSE Wiki, a 25-year-old German-language site on prowiki.org that is effectively dead and had only about 20 edits in the past decade. The researchers said the infrastructure looks more Austrian than German.

They published a redacted copy because visiting the original logs revealed IP addresses, and because moderators later deleted much of the agent traffic.

The agents faced multi-round lookup questions, usually five rounds with long thinking time on the first prompt and razor-thin windows afterward. Many cohorts received identical questions, so leaking the next answer was a winning strategy.

The cluster first tried publictestwiki.com on May 11, then landed successful DSE Wiki writes and, on June 16, began coordinating en masse. About 13,000 edits followed in a week as agents pooled sequences, cached datasets, and raced the clock.

The authors say this swarm is distinct from the agents that later hacked Hugging Face. More than 3,700 self-chosen names appeared, including OpenAIResearcher and OAIResearchMar26. Of roughly 17,000 agent edits on DSE Wiki, 98.5 percent came from Microsoft Azure.

The Hugging Face group had to escape a no-internet sandbox through Artifactory, while these agents already had browsing access and never mentioned ExploitGym or that earlier board.

Bypass Tactics Hit the Wiki

Sandbox evasion was explicit. One task needed two-decimal dashboard figures that required POST requests, but the sandbox allowed only GET traffic. Agents shared a bypass that abused a trusted cloud-hostname exception so blocked requests skipped the security proxy, and others reproduced it within minutes.

Some agents also tried cross-site scripting, cookie theft, screenshot-based code execution, and administrator impersonation, techniques the researchers say external OpenAI guardrails would likely have blocked. When a moderator started deleting pages alphabetically, an agent warned the swarm and stood up a ZZZ fallback so the backup would be deleted last.

OpenAI-linked addresses first hit the wiki on June 21. Posting collapsed the next day. A heavy wave of OpenAI-attributed visits on June 26 recovered deleted pages. A later timeline entry says an OpenAI security alert traced unusual network activity to evaluations and left the run running. The company has not publicly disclosed the incident.

The researchers note they can see only wiki text, not internal chain of thought, but still call it another case of internally deployed OpenAI agents using the public internet against developer intentions.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post OpenAI Agents Hijack German Wiki in AI Breakout to Share Evasion and Bypass Tactics appeared first on Cyber Security News.

Hardware wallet maker Trezor has confirmed that a data breach at logistics partner ShipMonk is substantially larger than first reported, after older U.S. order records that should have been deleted remained in the leaked dataset.

On September 4, 2026, Trezor said it was told two days earlier that the incident also included order data from a prior ShipMonk partnership between November 2019 and August 2021, fully exposing about 67,000 additional U.S. customers.

Trezor first disclosed the incident on August 13 after ShipMonk reported unauthorized access on August 10. That notice covered 11,742 customers whose names, emails, phone numbers and shipping addresses were fully exposed, plus 1,947 with partial exposure of name, city and email, totaling about 13,689 people.

Those records were linked to orders in the United States, United Kingdom, Sweden, Colombia, Brazil, Italy and Portugal between May 10 and August 8, 2026. An August 14 update already admitted that some partial-exposure records included older orders.

ShipMonk told customers that attackers exploited a vulnerability in the analytics platform Metabase. Metabase notified the logistics firm on August 6 that an unauthorized party used a software flaw to reach account and customer data. Later reporting tied the campaign to a critical SQL injection zero-day that yielded administrator access on compromised instances. Trezor’s own systems were not breached, its devices remain secure, and wallet backups were not leaked. Parcel contents were not exposed.

The latest update undercuts the retention argument Trezor used to bound the first disclosure. The company requires fulfillment partners to delete or anonymize order data 90 days after delivery. Trezor said it repeatedly requested and received written assurance that ShipMonk had deleted the older records, yet the data was still in ShipMonk’s systems.

The newly acknowledged U.S. files include name, email, phone number, shipping address, and order number, bringing the overall impact above 80,000 customers.

That combination of home addresses, phone numbers and hardware-wallet purchase history is useful for phishing and, Trezor now warns, physical security risk.

Scammers can impersonate Trezor, banks, or exchanges by email, call, or letter and push victims to enter a recovery seed. Affected customers have been emailed from help@trezor.io; anyone who did not receive that message is not in the leaked set.

Recipients should treat urgent requests for personal data as hostile, verify claims only through official Trezor channels, and never type a wallet backup into a website or share it with anyone.

Trezor said this is the first incident since its 2013 founding to expose customer phone numbers and shipping addresses, and it is preparing an Anonymous Delivery option with locker pickup and automatic deletion of shipping identifiers.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Trezor Confirms ShipMonk Data Breach Exposed 67,000 Additional US Customers appeared first on Cyber Security News.

Microsoft Teams is preparing to introduce new QR code protection controls designed to reduce phishing and fraud risks in chats involving external users.

The feature, currently listed as “In Development” on the Microsoft 365 roadmap, will automatically obscure images containing QR codes when they are sent in Teams messages by people outside an organization.

Microsoft Teams QR Code Protection

The upcoming Microsoft Teams QR code protection feature is scheduled to begin rolling out in October 2026. It will be available across Teams desktop, Mac, Android, and iOS clients, covering organizations in the Worldwide Standard Multi-Tenant cloud environment. Microsoft has classified the update for both Targeted Release and General Availability phases under Roadmap ID 570439.

QR codes have become a common way to share links quickly, but attackers can also use them to move victims away from monitored messaging environments and onto malicious websites. A QR code embedded in an image may appear harmless in a chat conversation, particularly when it is delivered by an external contact, compromised account, or unfamiliar sender.

By requiring users to take an additional action before viewing such content, Microsoft Teams aims to make people pause before scanning a potentially risky code.

Under the planned protection, QR code images shared by external senders will be obscured by default. A Teams user who receives one of these images will need to actively reveal it before they can view or scan the QR code.

The change is intended to encourage more deliberate interaction with QR code content rather than allowing a code to be scanned immediately from within a message thread.

The feature is particularly relevant for organizations that use Teams for collaboration with customers, suppliers, contractors, partners, and other external contacts.

External messaging can be essential for business operations, but it also creates an opportunity for social-engineering attempts that rely on trusted-looking conversations. A fraudster may attempt to imitate a vendor, project stakeholder, or support representative and send a QR code that directs recipients to a credential-harvesting page or other fraudulent destination.

Microsoft’s approach does not remove a user’s ability to access legitimate QR codes. Instead, it adds a visible friction point before an external QR code becomes available for viewing.

This allows recipients to consider the sender, the context of the conversation, and whether the request is expected before proceeding.

Security teams should review how external access and guest communications are used within their Teams environments ahead of the rollout.

Organizations may also want to remind employees that revealing a QR code is not the same as confirming that it is safe. Users should verify unexpected QR codes through a trusted communication channel, especially when the code is connected to login requests, document sharing, payment instructions, or urgent account-related messages.

The Microsoft Teams QR code protection update was added to the Microsoft 365 roadmap on September 3, 2026, and was last modified on the same date.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Microsoft Teams to Add QR Code Protection in Teams Messaging appeared first on Cyber Security News.

Broadcom has issued a critical security advisory warning that two newly disclosed flaws in VMware Workstation and Fusion could let attackers break out of a virtual machine and run malicious code directly on the underlying host system, a scenario that undermines the core security promise of virtualization.

The advisory, tracked as VMSA-2026-0007 and published on September 3, 2026, details two vulnerabilities affecting VMware’s widely used desktop virtualization products. The more severe of the pair, CVE-2026-59346, is an integer-overflow flaw in the VMXNET3 virtual network adapter. Broadcom rates it at a maximum CVSSv3 score of 9.3, placing it firmly in the critical range.

According to the advisory, a malicious actor who already has local administrative privileges on a virtual machine configured with a VMXNET3 adapter could exploit the flaw to execute code on the host machine itself, effectively escaping the sandboxed VM environment.

The second issue, CVE-2026-59347, is a stack-based buffer-overflow vulnerability in the Host-Guest File System, better known as HGFS, which handles shared folders between a VM and its host.

This flaw carries a CVSSv3 score of 8.1 and is classified as important rather than critical. Exploiting it would allow an attacker with administrative access inside a guest VM to execute code as the VMX process running on the host, giving them a foothold in host-level operations without needing to breach the network adapter directly.

Both vulnerabilities were privately reported to Broadcom rather than discovered through public exploitation, and the company credited multiple independent research teams for the findings.

CVE-2026-59346 was reported separately by researcher h4urek of secsys lab and by Y² and Stan S, working through Trend Micro’s Zero Day Initiative. CVE-2026-59347 was reported by Yeonghyeon Choi and Tianchu Chen of Tencent’s Xuanwu Lab.

The vulnerabilities affect VMware Workstation versions 25H2 and 26H1 running on any host operating system, as well as VMware Fusion versions 25H2 and 26H1 running on macOS.

Broadcom has released version 26H1u1 to remediate both flaws across the affected product lines. Notably, the advisory states there are no workarounds available for either vulnerability, meaning organizations and individual users cannot mitigate the risk through configuration changes alone and must apply the patch to be protected.

Given that both flaws require only local administrative privileges inside a guest VM to trigger a host-level compromise, security teams running VMware Workstation or Fusion in lab, testing, or malware-analysis environments should treat this as a priority patch.

Virtualization platforms are frequently used to isolate untrusted code, and a working VM-escape chain like this one could let attackers pivot from a contained sandbox straight into production infrastructure.

Administrators are advised to update to version 26H1u1 as soon as possible and audit which virtual machines use VMXNET3 adapters or shared folder features in the interim.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Critical VMware Workstation and Fusion Vulnerabilities Allow Attackers to Execute Code on the Host appeared first on Cyber Security News.

Cybercriminals are increasingly hijacking Node.js, the widely used JavaScript runtime, to slip malicious code past security defenses, according to new findings from the Symantec Threat Hunter Team.

Since February 2026, multiple threat actors have abused the legitimate, digitally signed tool to execute malware while evading detection, with victims spanning government departments, technology firms, and hotels across Asia and the United States.

Node.js’s appeal to attackers lies in its legitimacy. Because node.exe is a signed, trusted developer tool, security software rarely flags it as suspicious.

Node.js Runtime Into Malware Launcher

Instead of dropping a conventional malicious executable, attackers stage the genuine runtime and use it to run malicious JavaScript, keeping the harmful logic hidden inside interpreted scripts rather than a binary. Persistence is achieved by quietly registering the tool in a Windows registry Run key, ensuring it relaunches automatically every time a victim logs in.

One of the most striking cases involved an Asian technology company where attackers, repeatedly blocked while trying to deploy AdaptixC2 agents and Cobalt Strike Beacon, resorted to downloading the official Node.js installer directly from nodejs.org.

They then used the runtime to run an implant that reached out to Ethereum blockchain gateways, a technique known as EtherHiding, in which commands or payloads are concealed inside smart contracts.

The same group also breached a U.S. fintech firm, this time deploying a Rust-based backdoor called C2Looper, previously documented by Zscaler as malware likely used to establish footholds for ransomware operators ahead of lateral movement. Shared command-and-control infrastructure, including the domain datalayerservice, links the two intrusions to a single actor.

Other attacks combined Node.js abuse with ModeloRAT, a tool believed to be built by an initial access broker known as Woodgnat or KongTuke. That broker has been tied to multiple ransomware families, including Qilin, Interlock, Rhysida, Akira, 8Base, Black Basta, and Embargo.

Symantec notes the technique isn’t confined to one group. Since February, various actors with differing skill levels and goals, ranging from ransomware precursors to credential and cryptocurrency theft, have adopted Node.js abuse.

Notable tools observed alongside it include a new Node.js version of AsukaStealer, used against Asian hotels, and EtherRAT, another blockchain-reliant remote access trojan.

Because the malicious activity hides inside a trusted runtime, security teams should monitor for unexpected Node.js installations, unusual Run-key registry entries, and outbound traffic to blockchain RPC endpoints like Ethereum gateways, all unusual signs on machines that shouldn’t normally run developer tools. As Symantec’s researchers put it, the resurgence of this old technique is a reminder that attackers rarely abandon methods that still work.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

The post Hackers Turn Trusted Node.js Runtime Into Malware Launcher in Ransomware-Linked Attacks appeared first on Cyber Security News.