Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: unpatched (18 articles)Clear

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.

PHP schedules emergency release for two critical remote code execution flaws after early details leak

A leaked post disclosed two critical PHP remote code execution flaws, dubbed PHP2Shell, prompting PHP to schedule an out-of-cycle security release at 14:00 UTC on October 21 for supported branches 8.2 through 8.5. PHP rated both flaws 9.2 and has not described the mechanism, affected versions, or feature requirements, which will come with the release; the leaked identifiers CVE-2026-109618 and CVE-2026-109619 are not confirmed by PHP. watchTowr verified the leak is real and that the flaws allow code execution. No exploitation was reported as of October 21, and end-of-life branches 8.1 and older will receive no fix.

Check
Prepare to apply PHP's out-of-cycle update for branches 8.2 through 8.5 as soon as it ships, and plan migration off end-of-life 8.1 and older.
Affected
Supported PHP branches 8.2 through 8.5 reportedly contain two critical remote code execution flaws, with end-of-life branches 8.1 and older receiving no fix at all.
Fix
Install the PHP security release immediately on all supported branches, upgrade off end-of-life versions, and watch for exploitation once the technical details become public.

Unpatched critical LMCache flaw lets unauthenticated attackers run code on exposed LLM cache servers

JFrog disclosed CVE-2026-105192, a critical flaw rated 9.8 in LMCache, open-source software that speeds up LLM servers such as vLLM. In multiprocess mode the cache runs as a standalone server reached over ZeroMQ with no authentication, and one message type is deserialized with pickle before its type is checked, letting a crafted message run code. The server is exposed only when an operator binds it to a routable address rather than the default localhost, and the code runs with LMCache's privileges, which are root in the project's official container images. No fix exists yet, and JFrog advises keeping the port on localhost or a trusted cluster network.

Check
Inventory LMCache deployments, confirm the ZeroMQ cache server is bound only to localhost or a trusted cluster network, and avoid exposing it on routable addresses until a fix ships.
Affected
LMCache 0.3.9 through 0.5.5 in multiprocess mode exposes an unauthenticated ZeroMQ socket that deserializes pickle data, letting a remote attacker run code as root on bound servers.
Fix
Keep the LMCache port on localhost or a trusted network, restrict network access to LLM cache hosts, and watch for an upstream patch since none is available yet.

ConnectWise warns of an unpatched ScreenConnect flaw and urges interim mitigation

ConnectWise warned of a new vulnerability in ScreenConnect, its widely used remote-access platform, affecting both cloud and on-premises deployments, and issued temporary mitigations while it prepares a patch. The flaw involves file-transfer behavior in remote-access sessions and has not yet received a CVE identifier. As an interim measure, administrators are told to disable file-transfer permissions in the ScreenConnect console. ScreenConnect is a favorite tool of managed-service providers and IT teams, which also makes it a repeated target: three earlier ScreenConnect flaws are in the exploited-vulnerabilities catalog, two abused in ransomware, and nearly 6,000 instances are exposed online. There is a concurrent campaign spreading malware through rogue ScreenConnect clients.

Check
Apply ConnectWise's interim mitigation now by disabling file-transfer permissions in the ScreenConnect console, restrict access to the platform, and apply the official patch as soon as it ships this week.
Affected
Organizations and managed-service providers running ScreenConnect, cloud and on-premises; the unpatched file-transfer flaw could be abused for attacks, on a platform that grants powerful remote access and is frequently targeted by ransomware.
Fix
Disable file-transfer permissions until patched, limit and monitor who can reach the ScreenConnect console, watch for unauthorized clients and sessions, patch promptly on release, and treat this remote-access tooling as high-value infrastructure.

Unpatched Kaltura video player flaws allow unauthenticated file read and code execution

CERT/CC disclosed two unpatched flaws in Kaltura's HTML5 video player library that let a remote, unauthenticated attacker read files from a server and run code, with only network access to the endpoint required. Both stem from the same unsafe deserialization in the mwEmbedLoader.php endpoint, which takes a user-controlled ServiceUrl parameter and passes fetched data to PHP's unserialize without validating it. Supplying a file path lets an attacker read any file the web server can access, including credentials and API keys, while the deserialization also enables code execution. CERT/CC could not reach the vendor, and because the endpoint is exposed on Kaltura's shared multi-tenant infrastructure, the flaws can affect many tenants at once.

Check
Since there is no vendor patch, restrict or disable external access to the mwEmbedLoader.php endpoint and enforce a strict allow-list for the ServiceUrl parameter permitting only known backend API URLs.
Affected
Organizations running the Kaltura HTML5 player library exposing mwEmbedLoader.php (CVE-2026-19913, CVE-2026-19912); an unauthenticated attacker can read sensitive files and execute code, with shared-CDN exposure widening the impact.
Fix
Block or lock down the vulnerable endpoint, allow-list ServiceUrl values, monitor for suspicious file-read attempts, rotate any secrets that may have been exposed, and watch for a vendor fix.

Unpatched Calix router flaw lets attackers expose devices behind home networks

An unpatched flaw in Calix residential routers used by several US broadband providers lets a remote, unauthenticated attacker create port-forwarding rules that expose devices on the local network to the internet. Tracked as CVE-2026-75501, the missing-authentication issue affects the Calix GS7 XGS model on a specific firmware version, and Calix supplies gear to large providers including Cox and Brightspeed. The researcher who found it reported it to the vendor in June, got no response, and disclosed through CERT/CC after further attempts failed. Because it lets an attacker punch holes through the router's network address translation, internal devices that were never meant to be reachable can be exposed. No fix is available.

Check
If you operate or manage affected Calix broadband routers, ask the provider or vendor about a fix and mitigations, and check devices for unexpected port-forwarding rules exposing internal systems.
Affected
Networks behind affected Calix GS7 XGS routers on the vulnerable firmware (CVE-2026-75501); a remote, unauthenticated attacker can add port-forwarding rules that expose internal devices to the internet, and no patch exists.
Fix
Press the broadband provider and Calix for a firmware fix, restrict remote management where possible, monitor for unauthorized port-forwarding entries, and place sensitive internal devices behind an additional firewall until resolved.

Unpatched Shark vacuum flaw lets one stolen certificate control others region-wide

A researcher disclosed an unpatched flaw in internet-connected Shark robot vacuums that lets an attacker take control of other owners' units across the same cloud region. The certificate a vacuum uses to authenticate to its maker's Amazon cloud broker was never restricted to that one device, so a certificate pulled from a vacuum's flash memory can send root commands to any Shark vacuum the broker serves. That means watching the camera, driving the robot, reading the stored map of a home, and taking the Wi-Fi password in plaintext. No memory corruption or password guessing is needed. The researcher says the maker has had the report since March with no fix.

Check
If Shark robot vacuums are on your network, isolate them and other smart-home devices on a separate segment away from sensitive systems, keep their firmware current, and watch for the vendor's fix.
Affected
Owners of internet-connected Shark robot vacuums; an attacker with a certificate from one unit can run root commands on others region-wide, exposing camera feeds, home maps, and Wi-Fi passwords.
Fix
Isolate smart-home devices on their own network segment, limit what they can reach, and watch for the vendor to rescope its cloud certificate policy or reissue certificates, the real fix here.

Unpatched Cursor flaw runs a repo's fake git.exe the moment you open it

Security firm Mindgard disclosed an unpatched flaw in Cursor, the widely used AI code editor, that runs code automatically when a developer opens a malicious repository on Windows. When loading a project, Cursor looks for a Git binary in several places, including the workspace itself, so a file named git.exe planted in the repository root gets executed with no click, prompt, or warning, and it re-runs on a cadence while the project stays open. In a proof of concept, a renamed Windows Calculator launched on its own. Mindgard reported it in December and went public after seven months with no fix, so there is no patch and no CVE, only workarounds.

Check
Determine who uses Cursor on Windows, and avoid opening untrusted or freshly cloned repositories directly on a host, since a planted git.exe in the repository root runs automatically with the developer's access.
Affected
Developers using Cursor on Windows; opening a repository with a malicious git.exe in its root runs that binary automatically as the user, exposing source, SSH keys, and cloud tokens, with no patch.
Fix
Until Cursor fixes this, open untrusted repositories only in a disposable virtual machine or Windows Sandbox, add AppLocker path-deny rules for executables under workspace folders, and watch for unexpected child processes.

Unpatched Windows BitLocker bypass and SYSTEM elevation PoCs dropped on GitHub by a disgruntled researcher - YellowKey and GreenPlasma hit Windows 11 and Server 2022/2025

A researcher who calls themselves Chaotic Eclipse - and who has weaponized every prior Windows flaw they have leaked this year - dropped working proof-of-concept code for two unpatched zero-days on May 12. YellowKey lets anyone with physical access to a Windows 11 or Server 2022/2025 machine plug in a USB stick, hold CTRL during a reboot into the Windows Recovery Environment, and get a shell with full access to the BitLocker-protected drive. GreenPlasma is a privilege escalation against the CTFMON service that hands an unprivileged user a path to SYSTEM. Independent researchers including Will Dormann and Kevin Beaumont have confirmed that YellowKey works as advertised.

Check
Inventory which Windows 11, Server 2022, and Server 2025 endpoints have BitLocker in TPM-only mode (the default on most consumer hardware), and identify machines that ever leave secured premises.
Affected
Windows 11 and Windows Server 2022/2025 with BitLocker in TPM-only mode. Windows 10 is unaffected. GreenPlasma privilege escalation hits Windows 11 and Server 2022/2025.
Fix
No patch yet. Switch BitLocker from TPM-only to TPM+PIN, set a BIOS or UEFI admin password, and disable USB boot in firmware. Watch for a Microsoft out-of-band release before next Patch Tuesday.

Brand-new Linux 'Dirty Frag' bug lets any local user become root on every major distribution - PoC exploit is public, no patches yet

Researcher Hyunwoo Kim disclosed Dirty Frag yesterday after an unrelated third party broke the embargo five days early. The flaw chains two Linux kernel page-cache write bugs (xfrm-ESP and RxRPC) to give any local user root access on every major distribution - Ubuntu, RHEL, CentOS Stream, AlmaLinux, openSUSE Tumbleweed, Fedora. Like Dirty Pipe and last week's Copy Fail, it's a deterministic logic bug with no race condition required and no kernel panic on failure. PoC is public on GitHub. The ESP variant patch was merged into the netdev tree on May 7 but distribution kernels remain unpatched. No CVE assigned yet because the embargo broke early.

Check
Inventory Linux servers, container hosts, CI runners, and Kubernetes nodes that allow shell access or run untrusted code. Check whether esp4, esp6, and rxrpc kernel modules are loaded with 'lsmod | grep -E "esp4|esp6|rxrpc"'.
Affected
Every Linux distribution with kernel 4.10+ (ESP variant) and 5.x+ (RxRPC variant). All major distros confirmed: Ubuntu, RHEL, CentOS Stream, AlmaLinux, openSUSE Tumbleweed, Fedora. Acute risk: shared-kernel multi-tenant environments (Kubernetes nodes, container hosts), CI/CD runners executing untrusted PR code. Firecracker microVMs and gVisor are not affected.
Fix
Blacklist vulnerable modules: 'sh -c "printf \'install esp4 /bin/false\\ninstall esp6 /bin/false\\ninstall rxrpc /bin/false\\n\' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"'. This breaks IPsec VPNs and AFS filesystems but stops the exploit. Apply distribution kernel patches as soon as they ship - AlmaLinux has early test patches. Treat container boundaries as broken until patched.