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

OVSwrap kernel flaw gives local users root on most Linux distributions

A researcher disclosed OVSwrap, a Linux kernel flaw in the Open vSwitch datapath that lets an ordinary local user gain root, and published a working exploit covering roughly 800 builds. Tracked as CVE-2026-64531, it is an integer wraparound in how Open vSwitch handles internally generated network action streams, giving a deterministic memory-corruption path. The attacker needs no existing switch, no running daemon, and no special privileges: where unprivileged user namespaces are enabled, they create a private namespace, gain network capabilities inside it, and reach the vulnerable code. The module can even auto-load on demand, so an empty module list does not mean safety. Default configurations of most major distributions tested as exploitable.

Check
Install the patched vendor kernel, which upstream fixed on July 24, and where you cannot patch immediately, disable unprivileged user namespaces to cut off the main path to the flaw.
Affected
Most default-configured Linux systems with the Open vSwitch module available and unprivileged user namespaces enabled (CVE-2026-64531); an ordinary local user can corrupt kernel memory and gain root, with a public exploit available.
Fix
Apply patched kernels and reboot, restrict unprivileged user namespaces where feasible, and prioritize shared and multi-tenant hosts, since any local foothold from another flaw or stolen access can escalate to full control.

Critical Gitea flaw lets anonymous users read server secrets from public repos

Gitea patched a critical flaw in the self-hosted Git platform that lets an unauthenticated attacker read any file the service account can access, needing only a public repository and crafted Org-mode markup. Tracked as CVE-2026-59774 and scored 9.8, it stems from the markup-rendering endpoint: Gitea initializes its Org-mode library without restricting file access, so the include directive accepts absolute paths and returns their contents. No login or write access is required. Gitea warns it can chain to command execution: read the configuration file, extract the internal token, inject a Git hook, and trigger it during an anonymous clone. It affects versions 1.22.1 through 1.27.0, fixed in 1.27.1.

Check
Upgrade self-hosted Gitea to 1.27.1 immediately, and if logs show requests to the markup endpoint on an affected build, treat all secrets readable by the Gitea service account as exposed.
Affected
Organizations running Gitea 1.22.1 through 1.27.0 with any public repository (CVE-2026-59774); an unauthenticated attacker can read configuration files, internal tokens, and signing keys, and potentially chain to code execution.
Fix
Update to 1.27.1, rotate the internal token and any credentials the service account can read, keep Gitea off the public internet where possible, and review logs for Org-mode markup requests.

Paperclip AI flaws let a malicious agent import run commands on the host

Researchers disclosed flaws in Paperclip, an AI agent tool, that let attackers run commands on a user's machine through malicious agent imports. The more serious path, CVE-2026-41679 and scored 10.0, needs no account or user interaction against network-reachable deployments running in authenticated mode with the default registration configuration. A second path, scored 9.6, requires a victim to open an attacker-controlled page while Paperclip runs in its default local trusted mode. A third issue exposed sensitive data and control-plane details through API routes that skipped access checks. The fixes, which add import authorization and hostname validation, ship in the version tagged 2026.416.0.

Check
Update Paperclip to the 2026.416.0 release, and review whether any AI agent tools you run accept agent definitions or imports from untrusted sources without authorization.
Affected
Users of Paperclip AI running network-reachable authenticated deployments or the default local trusted mode (CVE-2026-41679); malicious agent imports or a visited page can lead to host command execution.
Fix
Apply the fixed release, require authorization for agent imports, avoid exposing agent tools to untrusted networks, and treat imported agent definitions as untrusted code that can execute on the host.

Critical cPanel flaw lets a hosting customer gain database administrator access

cPanel patched a critical flaw that lets an ordinary hosting customer escalate to full database administrator access, running SQL as the database root user. Tracked as CVE-2026-58048 with a score of 9.4, the bug is significant on shared hosting, where many customers use one database server: administrator access there can expose or alter other tenants' data, and depending on the operating system and database configuration, cPanel warns it may extend to operating-system-level compromise. cPanel is one of the most widely deployed web hosting control panels, so the flaw affects a large number of shared and reseller hosting environments. Fixes shipped across several release tiers.

Check
Update cPanel to a patched build for your release tier, prioritizing shared and reseller servers, and if you host with a provider, confirm they have applied the fix.
Affected
Providers and customers on unpatched cPanel servers (CVE-2026-58048); a hosting customer can gain database root access, reaching other tenants' data and potentially the underlying operating system on shared infrastructure.
Fix
Apply cPanel's patched builds, apply the vendor's interim mitigation where immediate updating is not possible, review database accounts and logs for unauthorized administrator use, and segment tenants where feasible.

Google removes AI agent workflows after a GitHub issue could hijack a privileged agent

Pillar Security showed that Google's Agent Development Kit repository could be turned against itself through a poisoned pull request or issue. The public repository ran a low-privileged triage agent that responded to outside contributions, and a higher-privileged agent reserved for maintainers. Because the triage agent posted through a bot account that counted as a repository collaborator, a prompt injection could make it post a command that satisfied the privileged workflow's trust check, invoking the maintainer-level agent. That crossed into a job holding a long-lived access token, a Google API key, and a cloud service-account credential, enabling code execution on the runner and secret theft. Google deleted the affected workflows.

Check
Review any AI agent workflows that act on untrusted pull requests or issues, and check whether a low-privileged agent can trigger a higher-privileged one through a shared bot identity.
Affected
Teams running tiered AI agent workflows in code repositories; untrusted issue or pull-request content can prompt-inject a public agent into invoking a privileged one, exposing continuous integration secrets and code execution.
Fix
Give agents scoped, non-collaborator identities, keep untrusted content from reaching privileged workflows, require human approval for sensitive agent actions, and minimize the tokens and credentials an agent job can access.

TP-Link patches 15 Omada provisioning flaws that chain into network takeover

TP-Link patched 15 vulnerabilities in the zero-touch provisioning system of its Omada business networking line, which lets IT teams and managed service providers configure switches, access points, gateways, and routers remotely. Forescout's Vedere Labs, which presented the findings at Black Hat, reported hardcoded cryptographic keys and certificates, insecure credential transmission, weak certificate validation enabling interception, a race condition in cloud device adoption, and default credentials. Chained with two previously disclosed command-injection flaws, they let an attacker break the provisioning chain of trust and infiltrate networks. Eleven received CVEs, and some issues also affect TP-Link cameras and smart-home devices. Forescout found over 1,800 exposed controllers.

Check
Apply TP-Link's Omada firmware and controller updates, take controller management interfaces off the public internet, and change any default device credentials still in use.
Affected
Organizations, and the managed service providers serving them, running TP-Link Omada devices; the provisioning flaws enable interception, device hijacking, and, chained with prior command-injection bugs, remote code execution and network infiltration.
Fix
Update affected Omada controllers and devices, restrict controller exposure, replace default credentials and certificates, monitor for rogue device adoption, and extend checks to affected TP-Link cameras and smart-home products.

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.

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.