Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7

Attackers exploit N-able RMM auth bypass, and the first fix did not hold

N-able is warning that attackers exploited an authentication bypass in N-central, the remote monitoring and management platform used by managed service providers and IT teams to administer customer endpoints. The flaw, CVE-2026-18556, allows unauthenticated administrative account takeover, and N-able's initial fix in one release proved incomplete: it found another way to exploit the same weakness, tracked as CVE-2026-18577, that widened the affected range. After taking over a server, attackers used its remote-control feature to reach managed endpoints and installed Cloudflare tunnels as services, which kept access alive even after the route through the N-central server was cut. Build 2026.3.1.7 is the first unaffected version.

Check
Upgrade N-central to build 2026.3.1.7 immediately, then hunt managed endpoints for unexpected Cloudflare tunnel services and other persistence, since patching the server does not remove footholds already placed.
Affected
Managed service providers and IT teams running N-able N-central before build 2026.3.1.7 (CVE-2026-18556, CVE-2026-18577); an unauthenticated attacker can take over the server and pivot to every managed customer endpoint.
Fix
Apply the hotfix, review N-central and endpoint logs for unauthorized access and tunnel installs, revoke and rebuild trust where compromise is found, and restrict management platform exposure to the internet.

Hugging Face Diffusers flaws turn loading a model into running attacker code

Researchers at Zafran disclosed three flaws, collectively named FaceHugger, in Hugging Face's widely used Diffusers library that let a crafted model repository run arbitrary code on any machine that loads it. All three bypass trust_remote_code, the safeguard meant to stop unreviewed code from executing, by exploiting a timing gap: the trust check runs against the first of two separate download requests, so anything that makes the loader see custom code the check did not slips through. One variant abuses a default None.py filename, another a race condition, and a third cross-repository pipeline loading. Because Diffusers runs inside production pipelines, CI/CD, and container images, one poisoned model load can mean deep initial access.

Check
Upgrade the Diffusers library to 0.38.0 or later across development, CI/CD, and container images, and check the transformers library, which has a related flaw, is current too.
Affected
Anyone loading Hugging Face models with Diffusers before 0.38.0 (CVE-2026-44827, CVE-2026-45804, CVE-2026-44513); a malicious model repository executes code on load, bypassing the trust_remote_code safeguard and reaching CI/CD and production.
Fix
Update Diffusers and transformers, treat model repositories as untrusted code rather than data, load untrusted models only in isolated sandboxes, and apply egress controls and credential hygiene around machine learning pipelines.

Alleged Żabka leak advertises source code, Jira data, and a reused GitLab token

A data-leak forum listing is advertising an alleged dataset from Polish convenience-store chain Żabka for 5,000 euros, claiming roughly 541,000 Jira issues, about 230,000 IT service-desk tickets, and source code from 89 GitLab repositories. The post names real internal systems, including the chain's point-of-sale platform and SAP environment, and more than 20 outside vendors. A reviewer of the sample archive found the counts internally consistent and noted that a single GitLab access token appears across all 89 repository dumps, pointing to reused credentials rather than a code flaw. Żabka has not confirmed the breach, and the seller's account has no trading history.

Check
Treat the claim as unverified, but use it as a prompt to check whether single tokens or credentials in your own environment grant access across many repositories or systems.
Affected
Żabka and its listed vendors if the data is genuine; the pattern, one reused access token unlocking 89 repositories, is the same stolen-credential route behind many recent source-code and project-tracker thefts.
Fix
Scope access tokens narrowly per repository, rotate and expire them regularly, enforce phishing-resistant MFA on developer accounts, and watch for bulk exports from source and project-tracking systems that signal credential abuse.

Pass-ta-key attacks let malware on a PC steal and export Google-synced passkeys

Palo Alto Networks Unit 42 described three techniques, collectively Pass-ta-key, in which malware already running on a compromised Windows PC abuses Google Password Manager's synced passkeys. None break the underlying cryptography; they target how Chrome stores device keys, re-enrolls a device, and whether a site verifies that a person was present. The techniques can silently obtain a valid login assertion without any unlock prompt, register an attacker-controlled verification key that defeats user-verification checks, or extract the secret that decrypts all of a user's synced passkeys for reuse elsewhere. Passkeys still resist phishing, but a fully compromised endpoint undermines the synced-passkey model.

Check
Recognize that endpoint compromise, not phishing, is the threat to synced passkeys, and confirm your important services actually require and validate the user-verification flag on passkey logins.
Affected
Users of Google Password Manager synced passkeys in Chrome on Windows whose device is infected; malware can forge logins, bypass user verification, and export all synced passkeys, even for strict accounts.
Fix
Prioritize endpoint security since these attacks need local malware, require and strictly validate user verification on sensitive accounts, and consider hardware-bound passkeys or security keys rather than synced ones for high-value access.

Malicious npm packages split a RAT across files to slip past code review

Researchers at Socket found 18 malicious npm packages that deliver a cross-platform remote access trojan to users of Alibaba developer tools, splitting the attack across many packages so each looks harmless on its own. Ten lure packages with no real function depend on a bridge package, which pulls in loaders that fetch a rule-engine configuration from GitHub and use it to run OS-specific payloads from a server disguised as Alibaba infrastructure. On Windows it even replaces a legitimate Alibaba security app with a trojanized copy. The final trojan can steal data, run commands, and move laterally, and the campaign stayed hidden for about three months.

Check
Analyze dependency trees as a whole rather than one package at a time, since this campaign hid its logic across lure, bridge, and loader packages that each look benign in isolation.
Affected
Developers using Alibaba tooling who installed the malicious packages; the fragmented loader assembles a remote access trojan that steals data, runs commands, and moves laterally, evading per-package review.
Fix
Vet dependencies and their transitive graph, watch for packages that only pull in others or fetch configuration from external repositories, pin trusted versions, and monitor developer machines for unexpected outbound connections.

INC ransomware becomes the main group exploiting SonicWall VPN appliances

Resecurity reports that the INC ransomware operation has become the dominant group exploiting two SonicWall SMA1000 VPN appliance flaws, accelerating its attacks since early August. The pair, CVE-2026-15409 and CVE-2026-15410, were exploited as zero-days before SonicWall patched them in mid-July, and can be chained to gain root on the appliance and extract credentials, session databases, and one-time-password data. Many appliances remain unpatched or already compromised, leaving footholds attackers can reuse. Victims listed recently span private and government organizations across several countries, and some reported follow-up emails and phone calls from people claiming to help with the ransomware.

Check
Confirm SonicWall SMA1000 appliances have the mid-July fixes, and because pre-patch exploitation was common, run a compromise assessment and rotate credentials, sessions, and one-time-password secrets the appliance handled.
Affected
Organizations running SonicWall SMA1000 appliances (CVE-2026-15409, CVE-2026-15410); INC ransomware is actively chaining the flaws to root devices, and unpatched or already-compromised appliances remain reusable footholds.
Fix
Patch, then re-image compromised appliances and reset all credentials and one-time-password tokens they processed, restrict management access, and treat unsolicited offers of ransomware help as part of the extortion.

Critical Adobe Campaign Classic flaw gives unauthenticated attackers code execution

Adobe patched a critical flaw in Campaign Classic, its enterprise marketing automation platform, that can let an attacker run code without any user interaction. Tracked as CVE-2026-48449 and scored 10.0, it is an incorrect authorization issue leading to arbitrary code execution in the context of the current user. The same update fixes a high-severity SQL injection flaw that allows arbitrary file reads. Affected versions are Campaign Classic v7 build 9397 and earlier on Windows and Linux, mostly on-premises and hybrid deployments, with a fix in build 9398. Adobe says it is not aware of exploitation, and separately patched eight critical flaws in Adobe Bridge.

Check
Identify on-premises or hybrid Adobe Campaign Classic instances, confirm the build number, and update to 7.4.3 build 9398, prioritizing any instance reachable from untrusted networks.
Affected
Organizations running Adobe Campaign Classic v7 build 9397 or earlier (CVE-2026-48449); the incorrect authorization flaw allows code execution with no user interaction, and a companion flaw enables arbitrary file reads.
Fix
Apply Adobe's update to build 9398, restrict access to the Campaign Classic interface, and review the server for unexpected code execution or file access, since the flaw needs no interaction to exploit.

Coldcard wallet firmware flaw let attackers guess seeds and steal 70 million dollars

A firmware flaw in Coldcard Bitcoin hardware wallets let attackers reconstruct wallet seeds offline and sweep roughly 70 million dollars from 1,196 addresses in 41 minutes on July 30. A March 2021 build error routed seed generation to a weak software random number generator instead of the device's hardware one, because the check confirmed a configuration macro existed rather than that it was enabled. That collapsed the randomness behind seeds to as little as 40 bits on older models, letting an attacker who can constrain the device identifier and timer state reproduce candidate seeds and match them to funded addresses. Coinkite shipped emergency firmware, but updating does not repair an already-generated seed.

Check
If you use a Coldcard wallet, check whether your seed was generated on affected firmware, and if so, generate a new wallet on patched firmware and move funds to fresh addresses.
Affected
Coldcard hardware wallet users whose seeds were generated on affected firmware from March 2021 onward; the weak randomness lets attackers reconstruct seeds offline and drain funds.
Fix
Generate a new seed on patched firmware and move funds to new addresses, treat any wallet made on affected firmware as compromised, and verify hardware RNGs are enabled, not just present.

Amgen says patient health and research data stolen from third-party cloud systems

Biotechnology company Amgen disclosed that attackers stole patient and corporate data from multiple cloud systems run by third-party providers, rather than from its own servers. In a securities filing, Amgen said it detected the intrusion in July, confirmed data was exfiltrated, and determined the incident material based on the volume and sensitivity of affected files. Confirmed stolen data includes proprietary company information and patient protected health information, and the company is still assessing whether intellectual property, research and development data, and further patient records were taken. Operations, product supply, and financial systems were not disrupted. Amgen has not named a provider, entry point, or responsible party.

Check
Organizations relying on third-party cloud providers should confirm what sensitive data those providers hold, how it is protected, and whether breach notification and monitoring obligations are covered in contracts.
Affected
Amgen patients and partners whose protected health information and proprietary data sat in third-party cloud environments; intellectual property and research data may also be affected, deepening the impact beyond ordinary personal information.
Fix
Minimize and segment sensitive data held by vendors, require strong access controls and logging on third-party cloud environments, monitor for bulk exfiltration, and prepare for extortion and phishing after healthcare breaches.

Poisoned Adform ad script swapped crypto wallet addresses on customer sites

Attackers compromised a widely used tracking script from advertising firm Adform, turning it into a browser-side tool that rewrites cryptocurrency wallet addresses. The malicious code was appended in obfuscated form to Adform's trackpoint-async.js library, served from the company's own infrastructure, so any site loading it ran the altered script in visitors' browsers. It swapped Bitcoin, Ethereum, and Tron addresses both in the clipboard and in form fields, redirecting transfers to the attacker. Adform detected and removed the code on July 27 and says it did not install software or persist after a page closed, but cached copies may linger. It has not said how many page loads were affected.

Check
Warn people who sent cryptocurrency after visiting sites recently to clear their browser cache and verify every wallet address, and review whether your own sites embed third-party scripts that could be poisoned.
Affected
Anyone who copied or entered a crypto wallet address on a site loading Adform's tracking script on July 27; the swapped address silently redirected funds, and cached copies may still be active.
Fix
Limit and monitor third-party scripts, use subresource integrity where possible, isolate payment and wallet pages from ad and tracking code, and treat any shared external script as a single point of compromise.