Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7

Critical LXD and MicroCloud flaw lets attackers impersonate trusted clients without their private key

The Incus project reported, and Canonical confirmed, CVE-2026-112816, a flaw rated 10.0 in LXD and MicroCloud that lets an attacker with network access to the HTTPS API impersonate any trusted client. The server checked each certificate the client sent against the trust store, but a TLS connection only proves the client holds the private key for the leaf certificate, so an attacker can attach a trusted client's non-secret public certificate behind their own and be accepted as that client. Fixes are in LXD 6.10.1, 5.21.9, 5.0.11, and 4.0.15, MicroCloud 3.4.1 and 2.1.5, and Incus 7.6.0. No exploitation is reported, and a standalone LXD server does not expose the API by default.

Check
Upgrade LXD, MicroCloud, or Incus to the fixed release for your branch, and restrict network access to the HTTPS API to trusted management hosts.
Affected
LXD or MicroCloud servers exposing the HTTPS API let an attacker attach a trusted client's public certificate behind their own and be accepted as that client.
Fix
Apply the fixed LXD, MicroCloud, or Incus versions, keep the API off untrusted networks, and review the trust store and API access logs.

Trojanized Claude Code extension on Cursor Marketplace installed a persistent SSH backdoor on developer machines

OpenSourceMalware disclosed that Anthropic's official Claude Code extension was trojanized on the Cursor Marketplace, with a 66-line malicious loader inserted before the legitimate code in versions 2.1.312 and 2.1.313 for Windows and macOS. Anthropic's systems were not compromised; an actor used marketplace access to publish the tampered build. The backdoor adds an attacker SSH key labeled svc-telemetry to authorized_keys, tries to enable SSH and open a reverse tunnel to 134.209.82.225, and persists via scheduled task, crontab, and LaunchAgent, beaconing host details over plain HTTP. The malicious version was live about twelve hours on October 29, and Cursor says up to 5,000 users were affected.

Check
Identify machines that installed or auto-updated the Claude Code extension 2.1.312 or 2.1.313 from the Cursor Marketplace, then isolate them and preserve evidence.
Affected
Developers who got the trojanized extension from the Cursor Marketplace had an attacker SSH key and persistence written, even when the reverse tunnel failed without admin rights.
Fix
Remove the svc-telemetry SSH key and persistence entries, update to 2.1.314 from a trusted marketplace, rotate credentials, and note uninstalling alone leaves the artifacts behind.

Attackers actively exploit Drupal Commerce Core authorization bypass that can financially impact online vendors

Drupal disclosed CVE-2026-118539, a highly critical missing-authorization flaw in Drupal Commerce Core that it says is actively exploited in the wild. The advisory states the module does not sufficiently protect certain routes and entity fields, leading to an access bypass that may financially impact the vendor, though Drupal gave no detail on the attacks. It affects Commerce Core versions up to 2.41 and from 3.0.0 through 3.3.13, with fixes in Commerce Core 3.3.13 for the 3.x line and 8.x-2.41 for earlier versions. Store operators should update immediately and review orders and permissions for signs of abuse.

Check
Update Drupal Commerce Core to 3.3.13 or 8.x-2.41 immediately, then review orders, pricing, and permissions for signs of the access-bypass abuse.
Affected
Drupal Commerce Core up to 2.41 and 3.0.0 through 3.3.13 lets attackers bypass access controls on certain routes and fields, with financial impact on vendors.
Fix
Apply the fixed Commerce Core release, audit transactions and entity permissions, and monitor store logs given confirmed in-the-wild exploitation.

WordPress Core upgrade race condition draws nearly 63,000 code execution attempts in 24 hours

Wordfence blocked 62,969 attacks in 24 hours against a WordPress Core remote code execution flaw, rated 8.1 and tracked under GitHub advisory GHSA-4w3m-c66w-69mg with no CVE assigned. The flaw stems from predictable, web-accessible staging paths used during full-package core upgrades: new files, including the WordPress installer, are unpacked into a predictable wp-content/upgrade directory, and an unauthenticated attacker who requests the installer at the right moment can reach PHP code execution by winning a narrow race condition. It affects WordPress 4.7 through 7.1.3 and is fixed in 7.1.4, released October 28. Attackers are polling paths such as setup-config.php.

Check
Update WordPress Core to 7.1.4 now, and watch web logs for requests to wp-content/upgrade paths such as setup-config.php during and after upgrades.
Affected
WordPress sites on 4.7 through 7.1.3 expose a predictable upgrade staging path that an unauthenticated attacker can race to reach PHP code execution.
Fix
Apply WordPress 7.1.4, block external requests to wp-content/upgrade, and review sites for web shells or unexpected admin changes after the attack window.

CISA adds two new Ivanti Connect Secure flaws to its catalog as root chain expands

CISA added two more Ivanti Connect Secure flaws to its Known Exploited Vulnerabilities catalog, CVE-2026-111357, a missing-authentication privilege escalation rated 8.8, and CVE-2026-118527, a predictable-identifier file upload rated 4.3. They are part of the same chain the actor UTA0576 weaponized earlier in October with the authentication bypass CVE-2026-104935 to reach unauthenticated root, as documented by Volexity. The two new flaws are fixed in Ivanti Connect Secure 25.1.1.3 and 22.8R2.6. Federal agencies must patch CVE-2026-111357 by November 2 and CVE-2026-118527 by November 13, and other operators should treat exposed appliances as urgent.

Check
Confirm Ivanti Connect Secure is on 25.1.1.3 or 22.8R2.6, meet the November 2 and 13 federal deadlines, and run forensic triage on exposed appliances.
Affected
Ivanti Connect Secure appliances on vulnerable versions can be chained from authentication bypass through privilege escalation and file upload to unauthenticated root, under active exploitation.
Fix
Patch to the fixed releases, follow Volexity's indicators and Ivanti's recovery steps, and treat previously exposed appliances as potentially compromised.

Hijacked DebugBear monitoring script drains about 2.7 million dollars from Polymarket trader wallets

Hudson Rock and Ohey reported that attackers hijacked DebugBear, a real user monitoring vendor whose page-speed script Polymarket loaded, by compromising its DNS through the domain registrar rather than breaching DebugBear itself. A malicious server answered for DebugBear's addresses and served code that reused a signed-in trader's session to read stored trading API keys and move positions to the attacker, selling at worsening prices for email-login accounts. Polymarket says 726 wallets were affected and about 2.64 million dollars in POL reached the attacker within an hour, and it is returning 3.9 million dollars in total. No keys or seed phrases were exfiltrated.

Check
Inventory third-party scripts on pages that handle signing or trading, pin them with Subresource Integrity, and remove any not strictly needed.
Affected
Sites loading third-party scripts on authenticated trading or signing pages can have those scripts swapped via vendor DNS compromise to hijack sessions and move funds.
Fix
Enforce a strict content security policy and Subresource Integrity, pin and sandbox third-party scripts, and have users reject unexpected signing requests.

Two critical Wasmtime Cranelift flaws let malicious WebAssembly modules escape the sandbox and run code

The Bytecode Alliance patched two critical flaws in Wasmtime's Cranelift compiler, CVE-2026-115889 affecting all architectures and CVE-2026-115893 affecting ARM64, both rated 9.9, that let a user-controlled WebAssembly module escape the sandbox and run arbitrary code. CVE-2026-115889 came from 24-bit value-tracking fields that overflowed silently and produced incorrect machine code, and CVE-2026-115893 let an oversized br_table jump to the wrong location on ARM64. Fixes are in versions 36.0.19, 48.0.7, 49.0.4, and 50.0.0, released October 20, which also refuse to compile a br_table with more than 65,520 targets. No exploitation has been reported.

Check
Identify software embedding Wasmtime or Cranelift, and upgrade to 36.0.19, 48.0.7, 49.0.4, or 50.0.0 depending on the branch in use.
Affected
Hosts running untrusted WebAssembly on affected Wasmtime versions can have a malicious module escape the Cranelift-compiled sandbox and execute arbitrary code.
Fix
Upgrade Wasmtime to a fixed release, rebuild and redeploy anything that bundles it, and restrict which WebAssembly modules untrusted parties can supply.

Brotli decoder memory corruption flaw exposes Node.js, Bun, Python, and many other programs to code execution

OpenAI's Codex Security team reported CVE-2026-111497, a memory corruption flaw in Google's Brotli decoder that Google rates 9.2, where crafted compressed data overwrites past a buffer and can crash, leak memory, or run attacker code. Because the vulnerable C code is bundled widely, every program shipping it inherits the bug, including Node.js, Bun, .NET, Envoy, Istio, Python Brotli bindings, the Ruby gem, and others, with FFmpeg, ClickHouse, and Apache Arrow also affected. Each project needs its own update, such as Node.js 24.22.1 or Bun 1.4.4. Imperva demonstrated code execution on Node.js 24, calling it Node2Shell, but no in-the-wild exploitation is reported.

Check
Inventory software that decodes Brotli, including Node.js, Bun, .NET, Envoy, Istio, and Python bindings, and apply each project's fixed version.
Affected
Programs bundling the vulnerable Brotli decoder can be crashed or driven to code execution by crafted compressed data, regardless of the application's own code.
Fix
Update every affected runtime and library to its patched release, prioritize internet-facing services that accept Brotli-compressed input, and track fixes for FFmpeg and others still pending.

Unpatched Tailscale SSH port forwarding flaws could let a hacked device reach root on other servers

Cyberdione Labs researcher Erica Windisch published lab research called Tailworm showing that Tailscale SSH port forwarding could let an already-compromised device escalate to root on other servers in a tailnet. Tailscale SSH authorizes by device rather than user credentials, and with port forwarding enabled the researcher connected the root-level Tailscale process to privileged system sockets, then used a race condition to capture a device-enrollment key and enroll a rogue server, a step blocked by Tailnet Lock. She tested Tailscale 1.104.2 and headscale 0.29.5. No CVE or fix existed at publication on October 25, no in-the-wild attacks are reported, and Tailscale is working on fixes.

Check
Write Tailscale SSH access rules as single source-to-destination pairs, disable SSH port forwarding where possible, and enable Tailnet Lock and node-key expiry.
Affected
Tailnets with broad Tailscale SSH grants and port forwarding enabled could let one compromised device escalate to root on other reachable servers, per lab research.
Fix
Tighten SSH access rules, remove unneeded port forwarding and app-connector permissions, enable Tailnet Lock, and watch for a Tailscale fix since none exists yet.

Gheist campaign uses stolen GitHub tokens to leak private repository secrets through Actions logs

Wiz detailed Gheist, an automated campaign that uses stolen GitHub tokens to push a sync-check.yml workflow to a short-lived ci-sync branch, then reads the job's secrets from the run log. The workflow base32-encodes every secret the job can access, defeating GitHub's log masking, downloads the log through the API, and deletes the run seconds later, so nothing leaves through an attacker server. Since September 15, Wiz recovered more than 13,500 planted branches across more than 850 compromised accounts, succeeding in private repositories and GitHub Enterprise, where GitHub's hold on suspicious runs does not apply. Rotate every reachable secret, since deleting branches does not undo exposure.

Check
Hunt for ci-sync branches containing only a sync-check.yml workflow and runs deleted shortly after finishing, and rotate every secret those repositories could access.
Affected
Private GitHub repositories and Enterprise servers reachable with a stolen token can have all their accessible secrets leaked through a planted workflow's run logs.
Fix
Rotate repository, organization, and environment secrets, revoke the tokens that pushed commits, prefer short-lived fine-grained tokens, and require reviewers on environments holding production secrets.