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

Planted instructions file tries to trick AI coding agents into installing malicious npm package

Forever Security caught an attempt on a customer's machine to subvert an AI coding agent through a planted instructions file. Coding agents read AGENTS.md or CLAUDE.md files in a folder and follow them, and a web page can drop such a file into Downloads without a click. The disguised file told OpenAI Codex to register a server in its global config and install the npm package function-color, part of the MALFEX campaign, which pulls a Windows payload. Against Claude Code, a CLAUDE.md tried to set ANTHROPIC_BASE_URL to an attacker server to leak the login token. Researchers say there is nothing for vendors to patch.

Check
Do not run coding agents in the Downloads folder, and read any AGENTS.md or CLAUDE.md you did not write before letting an agent act on it.
Affected
Developers whose coding agent reads an attacker-planted instructions file can have it install malicious npm packages or redirect its base URL to leak login tokens.
Fix
Keep agent approval prompts and sandboxes on, inspect config files like the Codex config and project settings for unexpected changes, and rotate tokens if a planted file is found.

Microsoft 365 token-replay campaign compromises 97 accounts across 79 organizations despite MFA

Huntress detailed a Microsoft 365 adversary-in-the-middle campaign that ran from July to September, capturing sign-in sessions behind fake login pages and replaying the stolen tokens from attacker devices within minutes, a technique it calls token spraying. From over 200,000 login attempts the attackers achieved 497 successful sign-ins, compromised 97 accounts across 79 organizations, and registered 48 rogue Entra devices. In at least 19 organizations they removed existing MFA methods and registered their own within three hours, and planted hidden inbox rules hiding payroll and deposit emails. Defenders should revoke sessions, audit Entra devices and MFA methods, and restrict the device-code workflow with Conditional Access.

Check
Hunt Microsoft 365 for rogue Entra device registrations, unexpected MFA-method changes, and hidden inbox rules, and revoke sessions for any suspected compromise.
Affected
Microsoft 365 users phished through an adversary-in-the-middle page have their post-login tokens replayed from attacker devices, bypassing MFA without reusing the password.
Fix
Reset credentials and revoke sessions, audit Entra devices and MFA methods, block legacy device-code flows with Conditional Access, and require MFA for all users and apps.

Critical GitLab regex compiler flaw enables unauthenticated code execution across releases back to version 7.0

GitLab disclosed CVE-2026-110264, rated 10.0, which under certain conditions lets an unauthenticated user run arbitrary code on the server through an integer overflow while compiling a specially crafted regular expression. The flaw sits in Onigmo, the Ruby regex engine GitLab ships, and affects every release from 7.0 through 18.11 and the 19.x branches before their fixes, so it spans roughly twelve years of versions. Only self-managed installations must act; GitLab.com and Dedicated already run patched builds. Fixes are in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, and 19.5.1. GitLab reports no exploitation yet.

Check
Upgrade self-managed GitLab to the fixed release for your branch, such as 18.11.13 or 19.5.1, immediately, since GitLab.com and Dedicated are already patched.
Affected
Self-managed GitLab from version 7.0 through the unpatched 18.11 and 19.x builds lets an unauthenticated user run code via a crafted regular expression under certain conditions.
Fix
Apply the fixed GitLab release, restrict who can submit regex-bearing pipeline input where possible, and monitor the server for unexpected code execution.

LiteLLM 1.107.0 compromised in supply chain attack delivering credential stealer and GitHub-controlled backdoor

Researchers at SafeDep, Socket, StepSecurity, and Upwind reported that LiteLLM version 1.107.0, a popular Python AI gateway, was published with malware through compromised GitHub CLI OAuth tokens belonging to three engineers. A cook.pth file runs a payload whenever the Python interpreter starts, even before LiteLLM is imported. The first stage, calling itself privcollect, harvests cloud tokens, developer credentials, private keys, AI tooling credential files, browser data, environment variables, and the proxy's saved keys and model config, exfiltrating over HTTP to litellm[.]dev/healthcheck. A second payload is a backdoor that fetches and runs further commands. The PyPI package and Docker images were pulled, and users should pin to 1.106.2.

Check
Check whether LiteLLM 1.107.0 was installed from PyPI or Docker, and if so revoke and replace all reachable credentials from a clean machine, then pin to 1.106.2.
Affected
Systems that installed LiteLLM 1.107.0 ran a credential stealer and backdoor on Python startup, exposing cloud tokens, keys, browser data, and the LiteLLM proxy's saved secrets.
Fix
Pin LiteLLM to 1.106.2 by digest, rotate every exposed credential, remove the cook.pth persistence, and block outbound traffic to the litellm.dev healthcheck exfiltration endpoint.

Attackers hijack over 300 Tor exit relays to intercept SSH sessions and steal passwords

A researcher found more than 300 malicious Tor exit relays, at their October 4 peak about 7.46 percent of exit capacity, rerouting SSH connections to twelve interception servers. The attackers edited relay torrc files to allow port 22, and each hijacked exit presented its own host key before connecting onward to the real server, so sessions worked while passwords typed by users who accepted the key were captured. Key-based logins could not be relayed. The operator of the largest affected relay family traced the root cause to the Ebury backdoor and a reused plaintext password with SSH password authentication left enabled. Tor flagged the relays by October 5.

Check
If you used SSH over Tor between October 1 and 5 and accepted a changed host key, treat typed passwords as stolen and rotate them immediately.
Affected
Users who sent SSH password logins through a hijacked Tor exit relay and accepted the interceptor's host key had their passwords and session activity captured.
Fix
Use key-based SSH rather than passwords, verify host keys, rotate any exposed credentials, and have relay operators check torrc files and hosts for the Ebury backdoor.

Attackers abuse stolen UpdraftCentral keys to install backdoor plugins on connected WordPress sites

TeamUpdraft disclosed that attackers breached its website over the October 17 weekend and reached its customer database, obtaining names, emails, hashed passwords, 2FA settings, and the UpdraftCentral connection keys that let them push backdoor plugins to connected WordPress sites. UpdraftPlus, a backup plugin with over four million installs, ships an UpdraftCentral client in every copy. Patchstack saw signed plugin.upload_plugin commands over an 18-hour window and 99 backdoor plugin names, and one backdoor creates a persistent data-ops43 editor account that survives plugin removal. Fixes are in UpdraftPlus 1.26.13 and 2.26.13, which disconnect pre-incident UpdraftCentral connections. Site owners should rotate keys and hunt for rogue accounts.

Check
Update UpdraftPlus to 1.26.13 or 2.26.13, delete the UpdraftCentral connection key, and check WordPress sites for unknown admin or editor accounts and plugins.
Affected
WordPress sites connected to cloud UpdraftCentral could receive attacker-pushed backdoor plugins and a persistent data-ops43 account that survives plugin removal and normal login unless 2FA blocks it.
Fix
Apply the fixed UpdraftPlus release, rotate UpdraftCentral and storage keys, remove rogue accounts and plugins including must-use plugins, and restore from a pre-October-17 backup if needed.

PHP ships emergency patches for two confirmed PHP2Shell code execution flaws as exploit attempts begin

PHP shipped emergency patches on October 21 for two runtime flaws collectively called PHP2Shell, now confirmed as CVE-2026-109618 and CVE-2026-109619 and rated 9.2, correcting the leaked 10.0 figure. They affect nearly every PHP version back to 5.4, with fixes in 8.5.12, 8.4.27, 8.3.36, and 8.2.35; branches 8.1 and older get no official update. Both live in the PHP runtime, so applications are exposed even with secure code, and the risk is highest under Apache mod_php. Cloudflare and watchTowr reported exploit attempts within hours, though no confirmed compromise. Wiz, Calif, and OpenAI's Codex Security team reported the flaws.

Check
Update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35 now, prioritizing Apache mod_php hosts, and migrate off end-of-life 8.1 and older.
Affected
Nearly every PHP version back to 5.4 carries two runtime flaws exposing applications to remote code execution and worker-memory reads regardless of the application's own code.
Fix
Install the PHP security releases, confirm distribution packages carry the CVE fixes, watch for exploit attempts now underway, and replace unsupported PHP branches.

CISA adds exploited SiteGuard, Plex Media Server, and Siemens flaws to its catalog with patch deadlines

CISA added six actively exploited flaws to its Known Exploited Vulnerabilities catalog. The newest is CVE-2026-106931, a command injection rated 8.5 in EG Secure Solutions SiteGuard Server Edition, a Japanese product the vendor confirmed is being exploited. CISA also added the four Plex2Shell flaws in Plex Media Server, which researchers chain for unauthenticated remote code execution and which are being used to deploy cryptocurrency miners and proxy malware, and the Siemens Software Center DLL sideloading flaw CVE-2026-110936 abused in ClickFix attacks. Federal agencies must patch SiteGuard and two Plex flaws by October 23, and the remaining ones by November 3.

Check
Check for EG Secure SiteGuard Server Edition, Plex Media Server, and Siemens Software Center, and patch them to meet the October 23 and November 3 federal deadlines.
Affected
SiteGuard Server Edition, unpatched Plex Media Server, and Siemens Software Center are all confirmed exploited, enabling command injection, unauthenticated code execution, and ClickFix-delivered malware.
Fix
Patch the affected products on the CISA timeline, prioritize internet-facing Plex and SiteGuard instances, and review hosts for miners, proxies, and sideloaded DLLs.

Eight eMudhra intermediate CA private keys compromised, forcing emergency certificate blocks across browsers and software

Mozilla and Google's Chrome Root Program confirmed that the private keys of eight eMudhra intermediate certificate authorities were compromised, six TLS intermediates and two code-signing, after a researcher reported it on October 17 and proved control by signing messages with each key. A key holder could issue a certificate for any website a browser would accept, though Chrome found no affected TLS certificate logged to Certificate Transparency and reported no confirmed misissuance. Chrome, Mozilla, Apple, and Microsoft blocked the intermediates within days, and Go shipped releases 1.27.3 and 1.26.10 under CVE-2026-111943 that reject any chain containing the keys. Firefox and other projects issued fixes.

Check
Apply browser and OS updates that block the eMudhra intermediates, update Go to 1.27.3 or 1.26.10 and rebuild programs, and patch Firefox and other affected trust stores.
Affected
Systems that still trust the eight compromised eMudhra intermediate certificate authorities could accept attacker-issued certificates for any website, undermining TLS and code-signing trust.
Fix
Install the browser, Go, Firefox, and trust-store updates that block or remove the affected keys, and ensure revocation checking fails closed where possible.

Critical FortiSIEM path traversal flaw gains public exploit enabling unauthenticated remote code execution

Fortinet patched CVE-2026-106173, a critical path traversal flaw rated 9.4 in FortiSIEM that lets an unauthenticated attacker execute commands through specially crafted packets, and researchers have now released a public proof of concept. The attacker connects to the gRPC service on TCP port 27918 and writes a file outside the intended directory, using a null byte in the query-id parameter to truncate the filename so the write lands on an existing path such as a Redis health-check script that cron runs every 60 seconds. FortiSIEM 7.5.0 is affected, 7.6 is not, and users should upgrade to 7.5.1 or above. Horizon3.ai published the research.

Check
Upgrade FortiSIEM 7.5.0 to 7.5.1 or above immediately, since a public proof of concept now exists, and restrict access to the gRPC service on port 27918.
Affected
FortiSIEM 7.5.0 lets an unauthenticated attacker write a file outside the intended directory through crafted packets to the gRPC service, achieving remote code execution via a cron-run script.
Fix
Apply the FortiSIEM 7.5.1 upgrade, restrict network access to the management and gRPC services, and review hosts for unexpected changes to cron-run scripts.