CISA confirms Brotli exploited and sets November 10 deadline
The Brotli flaw gets confirmation of exploitation, an ESXi zero-day hits the legal sector, and GhostAction has already compromised 1,792 GitHub accounts.

The 30-second summary
- CISA confirms active exploitation of the Brotli flaw (Node2Shell) in Node.js, with a federal fix deadline of November 10.
- ESXi zero-day used by a China-linked group against US law firms left operations unlogged.
- Palo Alto confirms PHP2Shell in active exploitation against management interfaces; Imperva recorded 482,342 requests in 24 hours.
- GhostAction compromised 1,792 accounts on GitHub across 22,964 targeted repositories; stolen tokens continue to be reused.
- testmetest campaign hid files too large for GitHub search to detect and publishes malicious npm packages.
CISA confirms active exploitation of Brotli with November 10 deadline
After demonstrations of remote code execution, CISA confirmed active exploitation of the Brotli flaw and listed it in the KEV (CISA's list of flaws already used in attacks), with a deadline of November 10. The code is in Node.js, Bun, Python, Envoy, and PowerShell.
Services that decompress data from external sources can be taken over by attackers without a password, with memory read and remote code execution, already demonstrated by Imperva on an official Node.js image. Lines 20.x, 23.x, and 25.x have no fix and require migration.
For the technical team
Out-of-bounds write in the Google Brotli decoder (CVSS v4 9.2) corrupts memory when processing a malicious compressed stream, without authentication. Imperva demonstrated RCE on an official Node.js image. CISA listed it in the KEV on October 27, 2026; the Microsoft bulletin gathers nine other related CVEs.
- CVE
- CVE-2026-111497, CVE-2026-105482, CVE-2026-105483, CVE-2026-106069, CVE-2026-105481, CVE-2026-106072, CVE-2026-106074, CVE-2026-106070, CVE-2026-106071, CVE-2026-106073
- Affected
- Brotli 1.0.3 to 1.2.0; Node.js 22.x, 24.x, and 26.x before the fixes, with 20.x, 23.x, and 25.x without a fix; Bun before 1.4.4; PyPI Brotli and brotlicffi; Envoy and Istio with Brotli decompression configured; .NET, Visual Studio, and PowerShell before the October 25, 2026 updates
- Exploitation
- confirmed active
- Fix
- Node.js 22.23.4, 24.22.1, or 26.12.1; Bun 1.4.4; Brotli 1.2.1; Microsoft updates from October 25; restart services, rebuild container images, and disable Brotli inspection on Palo Alto firewalls until the fix scheduled for October 30
Takeaway: A flaw in an embedded library appears in many products at the same time; the dependency inventory defines the speed of the fix.
Sources: Microsoft, The Hacker News, @HacktronAI, @BleepinComputer
On the radarFollow this incident live →ESXi zero-day used against the legal sector enters the KEV
China-linked hackers exploited a VMware ESXi flaw as a zero-day against US organizations, including law firms, according to CrowdStrike. CISA listed the flaw in the KEV, with a fix deadline of November 11.
The flaw leaves administrative actions out of server logs, which delays detection and investigation of intrusions. According to CrowdStrike, the group enters through edge devices exposed to the internet and moves to vCenter. Companies with VMware virtualization should prioritize the fix.
For the technical team
Insufficient logging vulnerability in ESXi: an actor with administrative privilege executes operations without a log record. CrowdStrike attributes the zero-day use to the China-nexus group Warp Panda, with entry through exposed edge devices and a pivot to vCenter. CISA requires forensic triage along with mitigation.
- CVE
- CVE-2026-41709
- Affected
- Broadcom VMware ESX; specific versions not stated in the sources
- Exploitation
- confirmed active
- Fix
- Builds ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025, or ESXi80U3j-25429389 or newer; vendor mitigations and the forensic triage required by CISA
Takeaway: Administrative actions outside logs delay any investigation; validate whether your telemetry covers the hypervisor.
Sources: CISA KEV, The Hacker News, SecurityWeek
On the radarFollow this incident live →Palo Alto confirms PHP2Shell exploited on management interfaces
Palo Alto Networks confirmed active exploitation of the PHP2Shell flaws against management interfaces exposed to the internet. The flaws allow remote code execution without authentication and affect PAN-OS on Siemens RUGGEDCOM. Imperva recorded 482,342 scanning requests in 24 hours.
PHP runs today on about 70% of web software, according to TechCrunch, and exploitation gives control of the server without a password. Cited research reports 25 servers with root access in four countries, including an environment tied to the US government.
For the technical team
CVE-2026-109618 and CVE-2026-109619 allow unauthenticated RCE in PHP configurations that serve web requests: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. CVE-2026-46300, from the Linux kernel, appears together in the KEV in the same chain. A public PoC exists after a solved bitcoin challenge.
- CVE
- CVE-2026-109618, CVE-2026-109619
- Affected
- PHP 5.4 to 8.5.11 on branches that serve web requests; EOL lines 8.1 and earlier without a patch from the PHP project; PAN-OS on Siemens RUGGEDCOM APE1808; IBM SevOne NMS 8.0.0 to 9.0.0
- Exploitation
- confirmed active
- Fix
- PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or a vendor build with a backport; update PAN-OS, apply the IBM service packs for SevOne, and remove the management interface from the internet
Sources: JPCERT/CC, TechCrunch Security, @hakluke
On the radarFollow this incident live →CISA confirms PolyShell in Adobe Commerce with November 10 deadline
CISA added the PolyShell flaw in Adobe Commerce to the KEV on October 27, citing active exploitation, with a federal deadline of November 10. Attacks exploit CVE-2026-48356 and breached hundreds of stores, according to The Hacker News. Adobe already fixed it in July.
Adobe Commerce and Magento stores without the July patches accept file upload without authentication, which leads to code execution and control of the store. After fixing, it is necessary to look for attacker code and injected content blocks, the DailyDarkWeb recommends.
For the technical team
CVE-2026-48356 (CVSS 9.6) is unrestricted upload of a file with a dangerous type in Adobe Commerce and Magento, without authentication, with arbitrary code execution in the context of the current user. CISA listed it in the KEV on October 27, 2026; use in ransomware listed as unknown.
- CVE
- CVE-2026-48356
- Affected
- Adobe Commerce and Magento without the July 2026 updates (APSB26-73)
- Exploitation
- confirmed active
- Fix
- Apply APSB26-73 (July 2026) and, after the patch, search for webshells and injected CMS blocks
Sources: CISA KEV, The Hacker News, @DailyDarkWeb
On the radarFollow this incident live →GhostAction reaches 22,964 repositories and tokens continue to be reused
The GhostAction campaign is larger than previously known: 22,964 targeted repositories, more than 72,000 malicious commits, and 1,792 compromised accounts with five families of malicious code. Attackers compromise maintainers on GitHub and inject automation routines to steal secrets, according to The Hacker News.
Every credential configured in the repository and any password stored in Git history was offered to the attacker, according to StepSecurity, which recommends treating the finding as a confirmed intrusion. Stolen tokens continue to be reused. The second stage reaches the developer's machine through VS Code.
For the technical team
Branch ci-sync-<6 chars> added .github/workflows/sync-check.yml to exfiltrate secrets through Actions logs. The second stage uses tasks.json and public/fonts/fa-solid-400.woff2 to mine credentials from Git history and install a remote command every five minutes. Public IoCs include IP 193.32.204.199 and the marker AKIA_CTX_START.
- Affected
- GitHub repositories accessible through compromised maintainer accounts; uber/athenadriver and pyxel hit
- Exploitation
- confirmed active
- Fix
- Revoke all tokens and secrets, including those present in Git history; remove the listed malicious files; search for IoCs and examine developer machines
Takeaway: A secret stored in Git history remains valid to the attacker after removal; revoking is the only fix.
Sources: GitGuardian, StepSecurity, @TheHackersNews, The Hacker News
On the radarFollow this incident live →WordPress 7.1.4 fixes 22 flaws, with RCE during the update
WordPress released version 7.1.4 with fixes for 22 vulnerabilities. The most severe is a race condition in the core update, which could allow remote code execution during the update. WordPress does not indicate active exploitation.
Sites on earlier versions are exposed to code execution on the server. Many flaws are injected script (stored XSS, which steals sessions) and require the Contributor, Author, or Editor role, common on sites with multiple writers. Versions 4.6 and earlier receive no fixes.
For the technical team
A race condition in the core upgrade could lead to RCE during the update window. Fixed multiple stored XSS in block markup, Interactivity API, Customizer, and comment pagination, plus stored DoS in the Interactivity API, disclosure of unpublished Customizer changes, and replacement of the embedded eMudhra root certificates.
- Affected
- WordPress before 7.1.4; fixes also for branches 7.0 to 4.7; 4.6 and earlier unsupported
- Exploitation
- not observed
- Fix
- Update to 7.1.4 through Dashboard > Updates; sites with background automatic updates should update on their own
Sources: @DarkWebInformer
On the radarFollow this incident live →testmetest hid a 13 MB payload from GitHub search
JFrog Security Research detailed how the npm testmetest campaign works: hidden configurations run malicious code when the project opens in Claude Code, Gemini CLI, Cursor, or VS Code. Files from 12.9 to 13.7 MB escaped GitHub code search.
In total, 42 repositories from 11 legitimate owners were weaponized. The attacker code publishes new malicious npm packages with stolen tokens or GitHub OIDC trusted publishing, which publishes without a token. JFrog recommends auditing repositories through Git tree enumeration.
For the technical team
Polymorphic wrappers from 12.9 to 13.7 MB exceeded the indexing of GitHub code search and the contents API. The payload is a publisher that uses stolen npm tokens or OIDC trusted publishing. Recent packages hide the payload in a native addon (.napi_cache, XOR 0x96) that refuses to run in CI, containers, or debuggers.
- Affected
- 42 GitHub repositories from 11 owners; developers who open infected projects in Claude Code, Gemini CLI, Cursor, or VS Code
- Exploitation
- confirmed active
- Fix
- Rotate GitHub and npm credentials and tokens, revoke unused OIDC trusted publishing, and audit repositories through Git tree enumeration
Takeaway: A trusted publishing credential becomes a propagation vector; the audit must cover the entire Git tree.
Sources: @DailyDarkWeb, @IntCyberDigest
On the radarFollow this incident live →ZDI publishes zero-day in Telegram animated stickers with no fix
The Zero Day Initiative disclosed CVE-2026-111105 (CVSS 7.0), a flaw in the Telegram animated sticker library rlottie that allows code execution inside the app. The final advisory requires user interaction; researcher Saifeldeen Aziz claims a 0-click chain, without a click, with execution on iOS.
Telegram told ZDI that sticker validation on the server mitigates the flaw, and there is no patched version or recorded attacks. The flaw affects clients used by journalists, executives, and government teams, and a malicious sticker would compromise the device and the conversations.
For the technical team
Write before the start of the buffer due to incorrect validation of attacker-controlled animation data in rlottie. ZDI published the zero-day on October 15 after Telegram refused a client fix, claiming server-side sticker validation. Saifeldeen Aziz presented a 0-click chain with code execution on iOS at OffensiveCon Japan; conference claims, not yet verified. A third-party report indicates replacement of rlottie with tlottie, in Rust, in the clients.
- CVE
- CVE-2026-111105
- Affected
- rlottie library in Telegram clients for iOS, Android, and Desktop; affected versions not disclosed
- Exploitation
- not observed
- Fix
- Not stated in the sources; keep clients up to date, disable automatic media download, and avoid unknown stickers and links
Sources: @DarkWebInformer, @DailyDarkWeb, @IntCyberDigest
On the radarFollow this incident live →KeyDrift stole encryption keys on Cisco SD-WAN networks
Cisco Talos revealed KeyDrift, malware installed in Cisco Catalyst SD-WAN environments compromised through CVE-2026-20127, a maximum severity flaw, CVSS 10.0, fixed in February. The malware copies and stores the keys that encrypt traffic between sites and maintains attacker access.
With the keys captured, attackers can decrypt traffic between sites. Talos assesses with high confidence an infrastructure overlap with the Silent Train network, used by Volt Typhoon. Observed targets include satellite services, defense, aerospace, and policy research. The attacks are historical.
For the technical team
Two components: LittleFilch extracts encryption key material from the data plane, starting from decrypted controller traffic; PolyFlame maintains a backdoor and command relay in legitimate processes. Talos attributes it to actor UAT-11473 and assesses with high confidence an overlap with the Silent Train network, of Volt Typhoon. The analysis covers historical intrusions, with no new wave confirmed; Lumen documented exploitation of the same flaw.
- CVE
- CVE-2026-20127
- Affected
- Cisco Catalyst SD-WAN environments without the February fix; targeted sectors include satellite services, defense and aerospace, and policy research
- Exploitation
- confirmed active
- Fix
- Apply the fix for CVE-2026-20127, available since February, and investigate signs of persistence after applying it
Takeaway: The fix closes the entry vector; old intrusions remain active, so look for persistence after updating.
Sources: The Hacker News, @DailyDarkWeb, @TheHackersNews
On the radarFollow this incident live →Wrapping up
The day was about confirmations: flaws with fixes available for months now entered the CISA exploitation list, from Adobe Commerce to Cisco SD-WAN. The difference between incident and routine was knowing where the code ran and acting within hours. Finding early, fixing, and checking afterward remains the cycle that protects.
Do you know today where each vulnerable dependency runs in your company?
Most of these flaws already had a fix available before becoming an attack.
Talk to us