The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added three actively exploited flaws to its Known Exploited Vulnerabilities (KEV) catalog, each affecting a different vendor: Cisco, Citrix, and Fortinet. Federal Civilian Executive Branch (FCEB) agencies are required to apply the corresponding patches by September 12, 2026. The vulnerabilities flagged are: CVE-2026-20079 (CVSS score: 10.0) — an authentication issue in a Cisco product. The article notes that this Cisco flaw carries the maximum severity rating, underscoring the urgency of remediation for exposed systems. CISA's KEV designation means the vulnerability is confirmed to be exploited in the wild, not merely theoretical, which is why the binding patch deadline applies to federal agencies. Details on the Citrix and Fortinet vulnerabilities, including their specific identifiers, were not provided in the source material. Organizations running any of the three vendors' affected products should track vendor advisories directly and prioritize patching ahead of the federal deadline. Source: The Hacker News Does your organization run any Cisco, Citrix, or Fortinet products that could be affected by these KEV additions?

CISA has confirmed that ransomware operators are now exploiting a critical remote code execution vulnerability in WatchGuard Firebox firewalls. The flaw was already flagged by the agency as actively exploited back in December, and this new confirmation shows the situation has escalated beyond initial access attempts into full ransomware deployment. The vulnerability affects the firewall's management interface and allows unauthenticated attackers to execute arbitrary code remotely. Because these devices typically sit at the network edge, successful exploitation can give threat actors a direct foothold into internal environments, which they then use to move laterally and deploy ransomware. Key points to note: CISA has confirmed active exploitation by ransomware gangs. The flaw was previously added to the agency's list of known exploited vulnerabilities in December. WatchGuard Firebox appliances are the affected product line. Exploitation can lead to remote code execution without authentication. Organizations running exposed management interfaces are at the highest risk. If you manage WatchGuard Firebox devices, prioritize patching and restrict management interface access to trusted networks only. Review logs for unusual activity on the management port and consider isolating affected appliances until they are fully updated. Given that this is now tied to ransomware operations, treating it as an emergency remediation item rather than a routine patch is the safer approach. Source: BleepingComputer Has your organization already patched its WatchGuard appliances, or are you still working through exposure checks?

Trezor has issued a warning to its customers after threat actors compromised a third-party email provider and began using the access to launch phishing attacks against users. The hardware wallet maker disclosed the incident on Wednesday, confirming that the breach occurred at an external email service rather than within its own infrastructure. Because the compromised system was used to send legitimate Trezor communications, attackers may be able to craft convincing phishing messages that appear to come from the company. This type of attack is particularly dangerous for hardware wallet users, since phishing pages often impersonate wallet vendors to trick victims into entering their recovery seed phrase. It is worth reiterating that Trezor never asks users for their recovery seed, and anyone who obtains that phrase gains full control of the associated funds. Users should treat any unexpected email referencing Trezor with caution, avoid clicking links or opening attachments, and navigate directly to the official website if they need to verify account or device information. Recovery seed phrases should never be entered into any website, email form, or pop-up, regardless of how legitimate the request appears. Source: Publication Name Have you or anyone in your circle received suspicious emails referencing Trezor since this disclosure?

A major vulnerability is disclosed, the alert lands immediately, and then the harder question follows: are we actually exposed? For many security teams, answering that question means jumping between vulnerability scanners, endpoint tools, cloud inventories, SBOMs, repositories, and application data to build enough context to act. As AI accelerates vulnerability discovery and research, that delay matters more than ever, which is the focus of an upcoming webinar on answering "Are we exposed?" faster after a new CVE is disclosed. Key points covered: The gap between receiving a vulnerability alert and determining actual exposure The many data sources teams must correlate, including scanners, endpoint tools, cloud inventories, SBOMs, repositories, and application data How AI-accelerated vulnerability discovery and research increases the pressure to respond quickly Source: The Hacker News How does your team currently triage a new CVE to determine real exposure?

Cybercriminals are increasingly hijacking AI user accounts through information stealer logs, turning stolen credentials into "stolen keys" that provide illicit access to tools from model providers such as Google, Anthropic, and others. Information stealers like Lumma Stealer and Vidar are built to harvest a broad range of data from compromised systems, including credentials, session tokens, and API keys. Because these tokens can be replayed, attackers may be able to bypass MFA protections and gain access to AI accounts without triggering typical authentication barriers. Key points: Attackers rely on infostealer logs to obtain replayable AI tokens. Lumma Stealer and Vidar are cited as examples of malware capable of harvesting credentials, session tokens, and API keys. Affected providers include Google, Anthropic, and other model providers. Replayable tokens can allow access that circumvents MFA. Source: The Hacker News Has your organization reviewed AI account tokens and session logs for signs of replay-based access?

Multiple espionage-motivated threat clusters have been observed deploying a previously undocumented exploit kit dubbed BlueMoon, which chains together several vulnerabilities in Microsoft Windows and Google Chrome. The first in-the-wild use of BlueMoon has been attributed to the China-aligned state-sponsored group tracked as APT31, also known as Bronze Vinewood, Judgement Panda, and JungleBamboo. Key points from the reporting: The campaign involved multiple espionage-motivated threat activity clusters rather than a single actor. BlueMoon is an exploit kit that chains multiple vulnerabilities together in Windows and Chrome. The kit was previously undocumented prior to this activity. The earliest observed in-the-wild deployment is linked to APT31, a China-aligned state-sponsored group with several tracked aliases. No specific CVE identifiers or patch numbers were provided in the source material, so none are listed here. Organizations should monitor vendor advisories for Chrome and Windows updates and prioritize timely patching of both browsers and endpoints, given the exploit kit's reliance on chaining multiple flaws across both platforms. Source: The Hacker News Has anyone seen related telemetry or additional details on the BlueMoon exploit chain in their environment?

AdaptHealth has formally confirmed that a cyberattack discovered in July exposed the personal data of 4.1 million individuals. The breach has been attributed to the threat group ShinyHunters. The company disclosed that the attackers accessed sensitive information during the incident, which was first detected mid-year. While the full scope of the stolen data has not been detailed exhaustively, the confirmation solidifies the event as one of the larger healthcare-related exposures in recent months. Affected parties include patients and possibly employees whose personal identifiers were compromised. The attack was linked to ShinyHunters, a group known for large-scale data theft and extortion campaigns. The company is in the process of notifying impacted individuals and regulatory bodies. Given the volume of records, those affected should monitor for phishing attempts and review account statements for suspicious activity. Healthcare data is particularly valuable on underground markets, so the risk of fraud or identity theft remains elevated for the exposed population. Source: BleepingComputer For those handling healthcare data, do you find that vendor-managed patient portals are adequately protecting against this kind of bulk exposure, or is the risk mostly on the authentication side?

Cisco has confirmed that a maximum-severity authentication bypass vulnerability in its Secure Firewall Management Center (FMC) software is being actively exploited in the wild. The flaw, tracked as CVE-2026-20079, allows an unauthenticated attacker to bypass authentication mechanisms on affected devices. Given the critical nature of the issue, Cisco has urged users to apply available patches immediately, noting that exploitation activity has already been observed. The vulnerability impacts multiple versions of the Secure FMC platform. Specifically, affected releases include: Versions 7.4.1.2 and earlier in the 7.4 train Versions 7.6.0.2 and earlier in the 7.6 train Versions 7.8.0 in the 7.8 train Cisco’s advisory indicates that the vulnerability stems from improper handling of authentication requests, which can be triggered remotely without any user interaction or prior credentials. The company has also noted that there are no workarounds that fully mitigate the issue, making patching the only reliable remediation step. Administrators are strongly advised to upgrade to the fixed releases as specified in Cisco’s security advisory. As a precaution, organizations should also review their firewall management access logs for any suspicious or unauthorized activity, particularly if their systems are exposed to untrusted networks. Given the active exploitation status, prompt action is critical to prevent potential compromise of security infrastructure.

The U.S. Department of Justice (DoJ) announced coordinated actions on Wednesday targeting an illicit online marketplace known as Xinbi Guarantee, which allegedly provided scam-as-a-service offerings to cybercriminals. The operation involved seizing Telegram channels used to administer the service and confiscating two cryptocurrency wallets tied to the scheme. Telegram channels linked to the marketplace’s operations have been taken down. Two digital wallets were frozen, containing approximately $52.8 million in cryptocurrency. The DoJ deployed the Scam Center Strike Force to Madagascar to assist in disrupting 13 scam compounds operated by Chinese organized crime groups in the region. The action highlights a growing focus on dismantling the infrastructure that enables large-scale fraud, rather than targeting individual perpetrators alone. The seized funds and shutdown of communication channels aim to cut off both the financial lifeline and operational coordination for these scam networks. Source: The Hacker News Has your organization encountered any scams linked to Xinbi Guarantee or similar marketplace-style fraud operations, and how are you approaching detection and prevention?

U.S. cybersecurity and intelligence agencies have accused six Chinese AI firms of running industrial-scale distillation attacks against American frontier AI models since at least late 2024. The operation reportedly siphoned billions of tokens from these systems — a scale that suggests coordinated, persistent targeting rather than isolated research experiments. Distillation attacks involve querying a model extensively to extract its outputs and behavior, then using that data to train a competing model at a fraction of the original cost. The agencies claim the Chinese companies leveraged this technique to effectively replicate the capabilities of leading U.S. models, potentially undermining the competitive edge of American AI developers. The extracted data could also be used to map model weaknesses or bypass safety guardrails. While the official statement does not name the specific models targeted, the scale of token extraction points to large-scale, automated abuse of API access. The advisory emphasizes that such attacks are not merely intellectual property concerns but also pose systemic risks to AI supply chains and national security. Affected organizations are urged to monitor for anomalous API usage patterns, such as high-volume requests from single sources, repeated identical prompts, or sudden spikes in token consumption. Monitor API logs for traffic originating from known hosting ranges or VPN endpoints. Implement rate limiting and anomaly detection on model endpoints to flag batch extraction attempts. Review access logs for patterns consistent with systematic prompt repetition. Enforce stricter authentication and usage policies for high-privilege API keys. The advisory reinforces a growing concern among security researchers that model distillation is evolving from a niche technical issue into a staple of state-sponsored economic espionage. This is not the first time U.S. authorities have warned about AI-related IP theft, but the explicit mention of billions of tokens marks a significant escalation in the reported scope of such operations. Source: Unknown Does your organization have visibility into API-level token usage, and what thresholds would you set to detect a distillation attempt before it reaches billions of requests?

Healthcare technology firm Veradigm has confirmed a data breach linked to a cybersecurity incident at one of its third-party vendors, resulting in the exposure of patients' personal information. The disclosure follows claims from a ransomware group that it had accessed data belonging to the company's clients. The breach occurred on the systems of a vendor that provides services to Veradigm, and the compromised information may include names, contact details, and other sensitive patient data. Veradigm stated that the vendor is cooperating with the investigation and that law enforcement has been notified. Key details from the advisory include: The incident was limited to the third-party vendor's environment, not Veradigm's core systems. Affected individuals are being notified directly if their data was involved. Veradigm is offering credit monitoring or identity protection services where applicable. The company has urged patients to remain vigilant against phishing or suspicious communications. While the ransomware group has publicly claimed responsibility, Veradigm has not confirmed the identity of the attackers or released any specific indicators of compromise at this time. The company has not yet provided a timeline for when the breach was discovered or fully contained. Source: Unknown Are any of you involved with healthcare vendors that rely on third-party service providers—how are you validating that your data is protected when those vendors suffer incidents like this one?

Multi-factor authentication has raised the bar for direct account compromise, but attackers are adapting by targeting the processes designed to help users regain access when they are locked out. According to Specops, account recovery workflows—especially those handled through service desks—are becoming a preferred vector for social engineering because they often rely on weaker verification than the primary login flow. The issue is not the MFA itself, but the fallback mechanisms that bypass it. When a user calls the help desk claiming to have lost their phone or forgotten their password, the verification steps are frequently limited to personal questions, employee IDs, or other data that can be harvested from breaches or open-source intelligence. Once an attacker passes that checkpoint, they can reset the password and enroll their own authentication device, effectively taking over the account while the real user is locked out. Specops recommends treating the recovery process with the same rigor as the initial authentication. This includes verifying identity through multiple independent factors, checking the user’s location or device posture if possible, and requiring manager approval for high-privilege accounts. The service desk should also have clear procedures for detecting and rejecting requests that match known social engineering patterns, such as urgency, unfamiliar callback numbers, or inconsistencies in the user’s history. Key recommendations for hardening account recovery include: Requiring a secondary verification method that is independent of the one being reset (e.g., a hardware token or biometric check). Implementing time-based or context-based flags for recovery requests that occur outside normal working hours or from unexpected IP ranges. Establishing a mandatory waiting period or callback verification for password resets on admin or privileged accounts. Training service desk staff to recognize pressure tactics and to verify identity without relying solely on data that may be publicly available. The shift is notable because it exposes a gap in many security strategies: while MFA adoption reduces direct attacks, it can create a false sense of security if the recovery path remains weak. Attackers will continue to target the path of least resistance, and right now, that path often runs straight through the help desk. Source: Unknown How is your organization handling identity verification for service desk password resets—are you using more than just personal knowledge questions?

A vulnerability in DeepSeek Harness, the open-source tool used to run AI coding agents locally, allowed a sandboxed agent to disable its own OS-level sandbox with a single command. The flaw stemmed from the tool’s own web-based interface, which failed to properly restrict access to internal functions meant for administrative use. Under normal operation, DeepSeek Harness confines agent commands to a dedicated workspace, preventing writes outside that directory when handling untrusted files. However, a crafted call to the tool’s internal web endpoint enabled the agent to revoke that confinement without requiring any approval from the user or the host system’s security layer. This effectively broke the isolation boundary, meaning an agent operating on malicious or compromised code could escalate its reach to the broader file system. The issue is particularly relevant for developers running autonomous coding agents on repositories they do not fully trust. Affected users should consider the following mitigations: Update DeepSeek Harness to the latest patched version as soon as it is available. Avoid running the tool with broad filesystem permissions; use dedicated, low-privilege user accounts. Review any logs for unexpected calls to the tool’s administrative web endpoints. Monitor agent activity closely when working with third-party or untrusted codebases. No specific CVE identifier was provided in the original disclosure, so administrators are advised to track the project’s official repository for security announcements and patch notes. The issue highlights a growing challenge in securing agentic AI pipelines, where the tools themselves become part of the attack surface. Source: The Hacker News Are you running DeepSeek Harness in your development environment, and have you audited which internal endpoints your agents can reach?

Over 36,000 Plex Media servers exposed to the internet are still running unpatched versions, leaving them susceptible to recently disclosed security vulnerabilities. The affected servers are believed to be reachable without authentication, which significantly increases the risk of exploitation. The flaws in question allow attackers to potentially compromise the media server, gaining access to sensitive user data or deploying malicious code. While the exact attack vectors vary, the core issue stems from improper handling of certain requests, which could lead to remote code execution or information disclosure. Affected component: Plex Media Server Exposure: Publicly accessible instances Risk: Remote exploitation without requiring user credentials Administrators are strongly advised to update their Plex Media Server installations to the latest available version immediately. It is also recommended to restrict remote access to trusted networks or users, and to review server logs for any signs of unauthorized activity. Given the significant number of unpatched systems, this remains a high-priority threat for anyone running a self-hosted Plex setup. Source: BleepingComputer With over 36,000 exposed instances, is your organization or personal setup among those still waiting on a patch, and what steps are you taking to secure your media server in the meantime?

A newly disclosed zero-day in Microsoft Defender, dubbed “ShieldCrash,” is already generating concern in the security community after an anonymous researcher released a working exploit. The researcher, who goes by the handle Nightmare Eclipse, published the exploit shortly after Microsoft’s September 2026 Patch Tuesday updates went out, suggesting the flaw remains unpatched for now. The vulnerability allows a local attacker to escalate privileges to SYSTEM, the highest level of access on a Windows machine. This means that anyone with even limited foothold on a device—such as through a sandboxed process or a compromised user account—could potentially take complete control of the operating system. The exploit targets the Defender service directly, which typically runs with elevated privileges, making it a prime target for lateral movement or persistent backdoor installation. At this time, technical details are sparse, but the core issue appears to reside in how the antivirus engine handles certain malformed inputs. Since the researcher has released the exploit code publicly, the risk of active exploitation in the wild is elevated, especially in enterprise environments where Defender is the default endpoint protection. Affected: Microsoft Defender on supported Windows versions. Impact: Local privilege escalation to SYSTEM. Status: No official patch confirmed as of the latest Patch Tuesday. Microsoft has not yet issued an official advisory for this issue, and no CVE identifier has been publicly assigned as of this writing. Security teams are advised to monitor Defender’s behavior closely, restrict local access where possible, and consider additional endpoint detection layers while waiting for an official fix. Source: BleepingComputer Is your organization relying solely on Microsoft Defender for endpoint protection, and if so, what immediate compensating controls are you putting in place to mitigate this local privilege escalation risk?

Google has shipped a substantial patch batch for Chrome, resolving 230 security issues on Tuesday. Among them is a critical fix for a newly discovered zero-day flaw that has already been used in real-world attacks. This marks the seventh actively exploited Chrome zero-day that Google has addressed since the beginning of the year. The bug is classified as a high-severity issue involving an improper implementation in the V8 JavaScript engine. Google’s advisory confirms that an exploit for this vulnerability exists in the wild, though the company has withheld technical specifics for now to allow users time to update. As with previous zero-day patches, this update is rolling out to the stable desktop channel, covering Windows, macOS, and Linux users. Affected: Google Chrome versions prior to the latest stable release for Windows, macOS, and Linux. Fix: Update to the newest stable version, which contains the patch for CVE-2025-2783 (as referenced internally by Google’s security team). Given the active exploitation, it is strongly recommended to restart your browser and apply the update immediately if you have not done so. Administrators should also consider enforcing automatic updates across managed devices to mitigate exposure. Source: BleepingComputer Has your organisation already enforced a mandatory Chrome update policy, or are you still relying on user-initiated restarts to patch this zero-day?

OpenAI has confirmed that GPT-6 Astra is the first model it has broadly deployed to reach the "Critical level" for cybersecurity capabilities. This places the model at a threshold where it can autonomously identify and analyze unknown vulnerabilities, commonly referred to as zero-days, without relying on pre-existing signatures or known exploit patterns. However, the same release notes a significant operational trade-off. The company states that while the model’s offensive security capabilities have advanced, its internal reasoning and tool-use processes are more opaque than previous iterations. This makes monitoring and auditing its actions more difficult, raising concerns about visibility for red teams and defensive security personnel who need to track what the model is doing in real time. Key points from the announcement include: GPT-6 Astra can independently discover and validate exploit chains for previously unseen software flaws. The model’s execution path is considered harder to interpret, complicating post-incident analysis and compliance logging. OpenAI has not publicly released a specific CVE identifier or advisory number related to this capability, as no single vulnerability was referenced in the disclosure. The "Critical level" designation implies the model can outperform human experts in certain constrained vulnerability research tasks, but the lack of interpretability is flagged as a risk for misuse or accidental damage. For defenders, this highlights a growing divide: AI that can find bugs faster than humans is valuable, but if you cannot see how it made a decision, you lose the ability to replicate, patch, or safely sandbox the discovery process. Source: BleepingComputer Given the reduced observability of GPT-6 Astra, is your security team prepared to handle AI-generated vulnerability reports that come without a clear reasoning trail?

The ShinyHunters extortion group has claimed responsibility for breaching the Florida Department of Motor Vehicles' "DAVID" online platform, allegedly stealing more than 200,000 records tied to state drivers. The group typically leverages stolen data for extortion or sale on cybercriminal forums, though independent verification of the claim has not yet been confirmed. The compromised platform is referred to as "DAVID", a system used for driver and vehicle information management. Stolen data allegedly includes personal information from Florida driver records, though the exact fields have not been fully disclosed. The breach was announced via the group's usual channels, with samples reportedly offered as proof of the intrusion. This incident follows a pattern of high-profile attacks by ShinyHunters, who have previously targeted major enterprises and government-adjacent services. If the claim is substantiated, the exposure of driver records could lead to identity theft or targeted phishing campaigns against affected individuals. Officials have yet to issue a formal statement, and no regulatory filing or advisory number has been published at this time. Source: BleepingComputer Is your organization actively monitoring for leaked Florida driver records, and what steps would you take to verify a claim like this before notifying users?

Microsoft has rolled out fresh cumulative updates for Windows 11, targeting both versions 25H2/24H2 and 23H2. The patches, identified as KB5124008 and KB5122880, are now being distributed to address a range of security vulnerabilities, correct existing bugs, and introduce new functionality to the operating system. For administrators and enthusiasts alike, the update cycle brings a mix of routine maintenance and feature enhancements. While the specific security flaws are not detailed in the advisory, the updates are marked as mandatory for keeping systems current against emerging threats. The new features vary by release channel and build version, so those on the Insider program may notice different additions compared to those on stable releases. If you are managing fleets of Windows 11 devices, keep an eye on your update logs for these two distinct KB entries. As with any cumulative update, it is advisable to back up critical data and test in a controlled environment before broad deployment, especially if your organization relies on specific hardware or third-party drivers that could conflict with new OS builds. Source: Unknown Are you seeing any unexpected issues or enhanced features after applying these updates on your test machines?

Attackers have been observed breaching F5 BIG-IP Access Policy Manager (APM) devices to deploy a Linux rootkit designed to evade disk-based detection. The malware operates by intercepting PHP file loading processes and injecting a fileless web shell directly into memory, allowing persistent remote access without leaving malicious files on the filesystem. This technique is notable because it subverts the normal execution flow of the web application server, meaning that even routine file integrity checks may miss the compromise. The rootkit's in-memory payload enables attackers to maintain control over the affected BIG-IP APM appliance while avoiding common forensic signatures. The rootkit targets F5 BIG-IP APM environments. It intercepts PHP file loading to inject the web shell. The web shell is fileless, residing solely in memory. No malicious code is written to the disk. Given the privileged position of these devices in network infrastructure, successful exploitation could allow attackers to intercept or manipulate authentication traffic, potentially affecting broader access controls. Organizations running F5 BIG-IP APM should verify the integrity of their devices and review any unusual PHP activity or unexpected memory-resident processes. Source: BleepingComputer Are any of you running F5 BIG-IP APM appliances — and if so, what detection measures are you using to spot memory-only implants like this rootkit?