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

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.

macOS ClickFix campaign fingerprints visitors to hide its malware from analysts

Microsoft Threat Intelligence detailed a macOS ClickFix operation spanning more than 250 domains that now fingerprints visitors before deciding whether to show a malware lure. The server-side gate hides the malicious page from crawlers and sandboxes while presenting selected Mac users with a fake software download, an anti-analysis layer rather than a change to the attack itself. The lure still requires the victim to copy and run an obfuscated command in Terminal, which fetches scripts and installs an infostealer, in this case Atomic Stealer, that targets credentials, browser data, authentication stores, and cryptocurrency wallets. Many domains follow a dictionary-word naming pattern using the word file.

Check
Warn Mac users never to paste and run Terminal commands from a web verification or fix prompt, and use the file-plus-dictionary-word domain pattern as a threat-hunting pivot.
Affected
macOS users who follow fake software-fix prompts; the fingerprinting gate hides the lure from analysis while serving selected victims an infostealer that harvests credentials, browser data, and crypto wallets.
Fix
Update to macOS 26.4 for its new Terminal and XProtect protections, block known campaign domains, monitor endpoints for scripts run from Terminal, and reinforce that legitimate fixes never require pasted commands.

Leaked n8n API tokens in public code exposed live automation instances

GitGuardian found 321 live n8n automation instances reachable using API tokens that developers had accidentally committed to public GitHub repositories, and showed four ways an attacker could abuse them. n8n workflows often hold credentials for the services they connect, so a valid API token can expose not just the automation platform but the downstream accounts it touches, from cloud services to messaging and databases. Because n8n is widely self-hosted and frequently wired into sensitive systems, an exposed token can become a path to broader compromise. The finding is a reminder that secrets committed to source control remain one of the most reliable ways in.

Check
Scan your repositories and history for committed n8n API tokens and other secrets, rotate anything exposed, and confirm n8n instances are not reachable from the internet without protection.
Affected
Teams self-hosting n8n whose API tokens reached public code; an attacker can drive the automation platform and reach the downstream credentials stored in its workflows, from cloud services to databases.
Fix
Rotate exposed tokens, add automated secret scanning to block commits, scope n8n credentials tightly, keep instances behind authentication and off the public internet, and audit workflows for stored downstream credentials.

Self-spreading npm worm ChainDrop poisons over 1,300 package versions in hours

A self-propagating worm named ChainDrop tore through the npm registry on August 4, poisoning packages that huge parts of the software world depend on. It began by hijacking the GitHub account behind keyv, a caching library pulled in about 150 million times a week, then spread to sibling and downstream packages, reaching over 1,300 poisoned versions with billions of monthly downloads within hours. A preinstall script harvests credentials from developer and continuous integration environments, including AI agent tokens, cloud keys, and self-hosted CI secrets, then uses stolen npm publishing access to poison more packages. A descendant of the earlier Shai-Hulud worm, it even forged valid-looking build provenance.

Check
Compare lockfiles and resolved versions against the published affected-package list, and treat any machine that installed a poisoned version as compromised, but remove the malware's token watcher before rotating anything.
Affected
Developers and CI systems that installed a poisoned version during the attack window; the worm steals repository, registry, cloud, AI agent, and private-key credentials, then self-spreads through npm publishing access.
Fix
Rotate all reachable credentials after removing the token watcher, install with scripts disabled, pin and delay adoption of new versions, and check for injected hooks in developer tooling and continuous integration configuration.

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.

77 malicious Open VSX extensions posed as dev tools to harvest developer data

Manifold Security found 77 malicious extensions on Open VSX, the open marketplace that editors like VSCodium, Cursor, and Windsurf pull extensions from, impersonating legitimate developer tools. Detected between July 26 and August 1, all 77 were linked through a shared exfiltration domain and common code. Fifty-eight sent only basic system information, while the other 19 performed deeper reconnaissance, exfiltrating developer, Git repository, and continuous integration metadata. Manifold found no access to source code, credentials, tokens, or SSH material and did not determine the campaign's goal. The extensions were pulled from Open VSX by August 3, but must still be removed manually from affected machines.

Check
Check developer machines and workspace configuration files for the extension identifiers in Manifold's report, remove any that appear, and block the campaign's exfiltration domain, mangorbit dot com.
Affected
Developers who installed the evil-twin extensions from Open VSX through editors like VSCodium, Cursor, or Windsurf; the extensions leaked system, Git repository, and continuous integration metadata about their environments.
Fix
Vet extensions and publishers before installing, prefer verified sources, inventory installed extensions across developer machines, block the known exfiltration domain, and monitor for extensions contacting unexpected external hosts.

XCSSET returns to infect Macs when developers build poisoned Xcode projects

Palo Alto Networks Unit 42 detailed a rebuilt version of XCSSET, macOS malware that spreads through Xcode developer projects. The actors compromise Git repositories and inject a downloader into ordinary files inside a project, so that when a developer builds the cloned project, a hidden loader runs under their own account with no permission prompt. It then infects every other Xcode project on the machine and propagates through shared code. Version 40 hides its logic in memory, generates polymorphic payloads, and adds a Chrome hijacker that drives the browser through its debugging protocol plus a component that trojanizes Telegram. Seventeen modules handle credential, keystroke, clipboard, and browser theft.

Check
Inspect Xcode projects, especially shared or cloned ones, for unexpected build scripts or run phases before building them, and watch developer machines for Chrome launched with debugging enabled.
Affected
macOS developers who build Xcode projects cloned from Git repositories; a hidden loader runs at build time under the developer's account, spreads to other local projects, and steals credentials and browser data.
Fix
Review third-party Xcode projects before building, build untrusted ones in isolated environments, keep macOS and tools patched, and monitor for browsers launched with remote debugging and unexpected outbound connections.