Arista patched an actively exploited critical SQL injection flaw (CVE-2026-114625, CVSS 9.9) in on-prem VeloCloud Orchestrator that lets any authenticated user gain operator privileges and masquerade as the local 'superuser operator'. Hosted VCO is already patched; on-prem admins need to upgrade.
2026-10-23: CISA added CVE-2026-114625 to its Known Exploited Vulnerabilities catalog, telling agencies to apply Arista's mitigations or stop using the product if mitigations are unavailable. (source)
2026-10-22: Arista disclosed CVE-2026-114625, an actively exploited SQL injection in on-prem VeloCloud Orchestrator, with fixes in 5.2.3.18, 6.1.3.10 and 6.4.2.12. Hosted VCO is already patched. Arista advised restricting the VCO web interface to admin networks, blocking 74.82.197.86 and 38.54.50.151, and preserving logs before remediating if compromise is suspected. (source)
China-nexus actor ARMORY CASTLE (ex-UNC5221) exploited CVE-2026-102764, a critical unauthenticated file-operations flaw in BeyondTrust Remote Support, as a zero-day from late August 2026. BeyondTrust issued BT26-05-RS; SaaS was auto-patched by Oct 9; CISA added the CVE to KEV on Oct 16. Self-hosted appliances need the patch plus forensics — patching alone does not clear existing footholds (SAWFLY / BARECLAW).
Fixed in
BT26-05-RS patch for self-hosted RS 24.3.1-26.2.3 (older versions must upgrade first); SaaS auto-patched Oct 9
The Polkadot Community Foundation warned that Fearless Wallet browser-extension versions 3.0.1, 3.0.3, 3.0.4 and 3.0.5 contained code, added Feb 19 2025 inside a large 'TON ecosystem' change, that sent private keys/recovery data to an attacker server when the wallet was unlocked. The code was active at different times until Oct 10 2026. Eight users have reported losses totalling 17,286 DOT. Anyone who used the extension since Feb 2025 must create a new keypair in another wallet and move funds.
Latest updates (3)
2026-10-21: Polkadot Community Foundation publishes security notice (14:00 UTC); 8 users report 17,286 DOT lost. (source)
2026-10-10: Last known period the exfiltration code was active (it could be re-enabled). (source)
2025-02-19: Malicious code merged into the extension's public source as part of a 'TON ecosystem' PR. (source)
Fortinet FortiMail CVE-2026-104286 (CVSS 9.8) is an unauthenticated arbitrary file write via path traversal / null-byte issues in Identity-Based Encryption web flows. CISA confirmed active exploitation and ordered federal mitigation; Fortinet published FG-IR-26-175 with patches and interim mitigations (disable IBE / restrict admin/webmail).
GitLab released a critical patch on Oct 21 2026 for CVE-2026-110264: an integer overflow in the bundled Onigmo / regex compiler that can allow an unauthenticated attacker to execute code on self-managed GitLab. CVSS 10.0; every CE/EE version from 7.0 (2014) is in range. Instances that only applied the Oct 12 regex fix remain vulnerable and must upgrade again.
2026-10-22: Shadowserver tracks 2,700+ internet-exposed GitLab CE instances (honeypot and patch status unknown); researcher joaxcar reported the bug via HackerOne. (source)
2026-10-22: GitLab updated its advisory with two threat detections ("Onigmo native worker crash" and "Org mode render error burst") to help self-managed customers spot exploitation attempts; GitLab.com and Dedicated remain patched. (source)
2026-10-21: GitLab released 19.5.1 and backports for CVE-2026-110264; GitLab.com already patched.
HPE Networking patched 72 vulnerabilities in its wireless operating systems AOS-8 and AOS-10 (ArubaOS) on Oct 22 2026 (advisory HPESBNW05162). Eight are rated CVSS 10.0: authentication bypasses, command injection, SQL injection and buffer overflows that let an unauthenticated remote attacker run code on Mobility Conductors, Controllers, Gateways and Access Points, several through the web management interface and the PAPI protocol. HPE urges customers to patch quickly and to restrict management interfaces. It knows of no public exploit code or exploitation.
2026-10-23: BleepingComputer reports the eight maximum-severity flaws and HPE's advice to restrict CLI and web management interfaces to a dedicated VLAN or firewall them. (source)
2026-10-22: HPE publishes HPESBNW05162 with fixes for 72 AOS-8 and AOS-10 vulnerabilities, eight of them CVSS 10.0, mostly found by its own security research. It knows of no public exploit code. (source)
2026-10-15: HPE Networking publishes an advance notification of the security advisories due on Oct 22. (source)
A flaw in Keycloak's reset-credentials flow (keycloak-services) lets an unauthenticated attacker force a password reset for any user without clicking the emailed verification link, then set new credentials and take over the account. Red Hat rates it CVSS 9.1. Fixes shipped in August (26.4.15, 26.6.6, 26.7.2); on Oct 21 a full proof-of-concept with check and takeover modes was published on Exploit-DB, so unpatched Keycloak instances should be upgraded now.
2026-10-21: Exploit-DB publishes EDB-52699 "Keycloak 26.7.2 - Unauthenticated Account Takeover" by Abel Maldonado (Orevim): a PoC with a safe --check mode and a --set-password takeover mode, tested on Keycloak 26.6.2. (source)
2026-08-18: CVE-2026-18963 published with GitHub advisory GHSA-4gv3-mc9p-5wqc (critical); fixed in keycloak-services 26.4.15, 26.6.6 and 26.7.2, with Red Hat errata for Red Hat Build of Keycloak. (source)
On Oct 21, Trend Micro's Zero Day Initiative sent several unpatched Linux kernel vulnerability reports to security@kernel.org but Cc'd the public linux-kernel and subsystem lists, so full technical details (code paths, KASAN traces) are now public before fixes ship. The worst are two ksmbd (in-kernel SMB server) remote code execution bugs that ZDI scores CVSS 9.0: an SMB Direct integer underflow (needs an RDMA device and a writable share) and a protocol-dispatch race (needs a guest share). Also leaked: an skb_zerocopy local privilege escalation (ZDI-CAN-33367, CVSS 7.8), a vmwgfx out-of-bounds write LPE, and an nvmet info leak. ZDI-CAN-33367 now has a working public exploit: CloudLinux confirmed it gives any local user root on AlmaLinux 8, 9 and 10, Debian 12 and 13, and Ubuntu 24.04 and 26.04 where unprivileged user namespaces are allowed, and setting user.max_user_namespaces to 0 closes that path. No CVEs yet and no fixed mainline or stable release; the skb_zerocopy fix is posted for review but not merged, KernelCare has a livepatch only for CloudLinux/AlmaLinux 10, the ksmbd race fix sits in the ksmbd maintainer tree, and an SMB Direct fix is in a branch aimed at Linux 7.5. No exploitation in the wild reported. Only machines running ksmbd are exposed to the RCEs.
Fixed in
No fixed mainline or stable kernel yet, skb_zerocopy LPE (ZDI-CAN-33367): upstream fix posted for review, not merged; KernelCare livepatch released for CloudLinux 10 and AlmaLinux 10 only (CloudLinux 9 in review, 8 in progress), ksmbd race (ZDI-CAN-33774): fix commit 68f410faedaf in the ksmbd maintainer tree (linkinjeon/smb.git), not yet in a release, SMB Direct underflow (ZDI-CAN-33549): likely fixed in Stefan Metzmacher's for-7.5/smbdirect branch (unconfirmed)
Latest updates (3)
2026-10-23: KernelCare livepatch for ZDI-CAN-33367 released for CloudLinux 10 and AlmaLinux 10, verified to stop the public exploit; CloudLinux 9 livepatch in review, 8 in progress. (source)
2026-10-22: Greg Kroah-Hartman replies to the reports: "For some reason you sent this to public lists, and did not include a patch" and "Please fix your submission process..." (source)
2026-10-22: Eric Dumazet says a patch for the skb_zerocopy bug, reported by someone else a week earlier, will be available soon. (source)
An unauthenticated OS command injection in proxy.php of Collabora Online - Built-in CODE Server (richdocumentscode), an optional Nextcloud app, lets attackers run commands on the Nextcloud server whenever the app's local CODE document server isn't running, for example during a restart, an upgrade or after a crash. It was exploited in the wild in September and October 2026 to plant web shells, with the first attack reported on GitHub on Sep 10. Collabora fixed it in richdocumentscode 26.4.303 on Sep 11 and published CVE-2026-110447 (CVSS 4.0 9.2) on Oct 14; it is a different bug from the 2025 proxy RCE CVE-2025-66208. Turning the app off is not enough: update it or remove it. Standalone Collabora Online servers, Docker or distro packages, hosted Collabora, and Nextcloud Office (richdocuments) without the built-in app are not affected. Admins who ran a vulnerable version should also hunt for unexpected PHP files.
Fixed in
richdocumentscode 26.4.303 or later (latest release 26.4.502), or uninstall the app
On Oct 14 2026 Vercel shipped Next.js 16.4.1 and 15.5.28 with two critical unauthenticated remote code execution fixes held back from the September release: CVE-2026-96889 / GHSA-2464-fhr4-w9xw, a use-after-free in librsvg (via sharp) reachable through the Image Optimization API when SVGs are processed on glibc-based Linux, and GHSA-673q-mjm6-r5xr, RCE in App Router apps with Cache Components when a `use cache` function returns multiple typed arrays. A high-severity Server Actions DoS (GHSA-p3m5-59mp-jv5r) is fixed too. GitHub added the SVG advisory to its global database on Oct 22. No known exploitation.
Fixed in
next 15.5.28, next 16.4.1, sharp 0.35.5 (librsvg 2.63.2)
2026-10-22: GitHub publishes GHSA-2464-fhr4-w9xw to the global Advisory Database (critical), so Dependabot and npm audit start flagging affected next versions. (source)
2026-10-14: Vercel releases Next.js 16.4.1 and 15.5.28 as an out-of-band security update: two critical unauthenticated RCEs (SVG Image Optimization, `use cache` typed arrays) and a high-severity Server Actions DoS. No workaround for the `use cache` bug; upgrade even if you don't use those features. (source)
2026-10-14: Netlify: the SVG flaw is also reachable through `next/og` ImageResponse; on Netlify the next/image path runs on its Image CDN, and impact there is a crashed function, not code execution. (source)
Node2Shell (CVE-2026-111497, also written Node 2 Shell) is a Brotli decoder out-of-bounds write in Node.js that can let an attacker run code when an app decompresses attacker-controlled Brotli data: Express 5 / body-parser 2.x request bodies sent with Content-Encoding: br, Brotli responses read by fetch(), or node:zlib on untrusted input. OpenAI Codex Security (Khai Tran and Sylvie Mayer) reported it; Node.js fixed it on Oct 21 2026 in 26.12.1, 24.22.1 and 22.23.4, alongside nine other CVEs (TLS hostname/IP bypasses, DNS NUL truncation) and a CA store refresh for the eMudhra incident. On Oct 22 Imperva Red Team, which coined the name Node2Shell, ran code on the official Node.js 24.22.0 image. NVD lists CVSS 4.0 9.2 (critical); Node.js rates it High. End-of-life lines (Node.js 20, 23, 25 and older) get no fix: upgrade to 26.12.1, 24.22.1 or 22.23.4. Bun is fixed in 1.4.4.
2026-10-22: End-of-life Node.js 20, 23 and 25 get no fix. Anyone on them has to move to 26.12.1, 24.22.1 or 22.23.4. Bun shipped the fix in 1.4.4. (source)
2026-10-22: NVD record for CVE-2026-111497 updated: the Google CNA scores it CVSS 9.2 (critical) and places the root bug in Google Brotli 1.0.3 through 1.2.0 (c/dec/decode.c), so other software bundling Brotli needs updating too. (source)
2026-10-22: Imperva Red Team (Ron Masas) names the bug Node2Shell and runs code on the official Node.js 24.22.0 image (Linux arm64) through fetch() and Express 5 / body-parser 2.x. It took several attempts; 24.22.1 rejected the same input. (source)
A command-injection flaw in the OpenCode AI coding agent let a malicious or later-hijacked remote MCP server run PowerShell commands on a developer's Windows or WSL machine when they started the MCP OAuth sign-in. The server-supplied authorization endpoint was passed unescaped to an old version of the open package. Anomaly fixed it in 1.18.33 on Sep 28 without a CVE or advisory, so scanners won't flag 1.0.137 through 1.18.32. macOS and Linux are not affected. Pillar Security found it and rates it 9.8; no in-the-wild exploitation reported.
Fixed in
OpenCode 1.18.33
Latest updates (3)
2026-10-22: The Hacker News reports the flaw; upgrade to 1.18.33, run `opencode mcp list`, and remove unvetted remote MCP servers. (source)
2026-10-19: Pillar Security discloses the flaw publicly. Anomaly declined to request a CVE, saying user-configured MCP servers are outside its trust boundary. (source)
2026-09-28: OpenCode 1.18.33 ships the fix as a routine browser-launch refactor; release notes don't mention security. (source)
Two critical remote-code-execution flaws in PHP core (CVE-2026-109618 and CVE-2026-109619, aka “PHP2Shell”) were disclosed early after an embargo leak. Both score CVSS 9.2 and can let an unauthenticated attacker run code on servers serving PHP web requests, especially Apache mod_php. Patches shipped Oct 21 2026 (appliance vendors such as QNAP are still preparing fixes); exploitation attempts were observed before and after the patch, and watchTowr / AWS report active scanning.
2026-10-23: The PHP Foundation advises keeping session.upload_progress.enabled=0 until the next PHP release to block a further, unlikely RCE vector (CVE-2026-115560). It already recommended this setting for CVE-2026-109619; only apps with a non-default serialize_handler that switch it to "php" at runtime can be affected. (source)
2026-10-23: Germany's BSI says it has found no cases of exploitation so far but cannot rule out successful attacks; most federal administration websites taken offline as a precaution are available again. (source)
2026-10-23: SOCRadar and Hunt.io find an attacker server with a PHP2Shell "one-click" chain for PHP 8.4.26 on Apache mod_php; the operator probed 123 servers over 10 rounds and none was exploited. Sophos retracts an earlier report of a successful compromise; no vendor has confirmed one so far. (source)
Four Plex Media Server flaws (CVE-2026-96652/96654/96655/96656), together called Plex2Shell, chain to unauthenticated admin-token theft and code execution. Researcher Zach Main published details Oct 16 and a PoC shortly after; exploitation of internet-facing servers (cryptominers + residential proxies) began by Oct 17. Fixed in 1.43.3.10861 (released earlier in August); CISA added the chain to KEV with a federal deadline of Oct 23.
Paulos Yibelo / pwn.ai found a Critical Linux networking flaw (CVE-2026-99999, CVSS 9.3) during Vercel’s $1M Sandbox challenge. Guest-controlled checksum metadata can rewrite an IPv4 header after validation, enabling host-memory disclosure and, in lab conditions, guest-to-host code execution on KVM/Firecracker. Upstream fix merged Oct 2026; host kernels need patch + reboot. Affects multi-tenant VPS / sandbox providers more than end-user desktops.
Fixed in
Upstream commit 6785011f8b16 and matching stable backports; vendor kernels as listed by distros
Ruby released 4.0.9, 3.4.12 and 3.3.13 on Oct 23 2026 to fix bugs in its Onigmo regular-expression engine (a double free and integer overflows) that GitLab turned into remote code execution on its servers, tracked by GitLab as CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264. Any Ruby app that compiles a regex from an attacker-controlled string (Regexp.new, Regexp.union, Regexp.compile or /#{input}/) is exposed; Regexp.timeout and pattern-length limits do not protect. Apps that only use their own hard-coded regexes are not affected. Ruby 3.2 and older are end-of-life and get no fix.
2026-10-23: Ruby releases 4.0.9, 3.4.12 and 3.3.13 with the upstream fixes: a double free when parsing fails after an alternation (#13332), an integer overflow in the compiled pattern size (#19020) and an overflow of internal IDs in patterns with many repeats (#16801). Ruby requested no CVEs of its own and says to track GitLab's IDs in scanners. Credit: Johan Carlsson (joaxcar) via GitLab's bug bounty; GitLab reported and coordinated. (source)
2026-10-23: Ruby 3.3 is in security maintenance and gets the Regexp fixes as an exception. 3.3.13 also updates the default resolv gem to 0.3.2, fixing CVE-2026-80212 and CVE-2026-80213. (source)
2026-10-21: GitLab 19.5.1 and backports fix CVE-2026-110264 (CVSS 10.0, unauthenticated RCE from an integer overflow when compiling a crafted regex), affecting every CE/EE version from 7.0. (source)
V12 disclosed 25 flaws in the x402 agent-payment SDKs, three rated critical: the default client had no spending limit (a hostile API could ask for an agent's whole token balance), the TypeScript Solana facilitator accepted token approvals as payments, and the SIWx login helper signed messages for other websites. All three were fixed in the August 18 releases, but no advisory was published, so npm audit and PyPI don't warn. Update @x402/fetch, @x402/axios, @x402/extensions and @x402/svm to 2.23.0 or later.
2026-10-23: The Hacker News found the foundation published no security advisory for the three flaws, so npm audit and PyPI report nothing for the last vulnerable releases. Patched clients now cap each payment at $1 and allow only recognized USD stablecoins unless the app sets its own spend controls. (source)
2026-10-22: V12 published 25 x402 findings with three critical ones detailed: no default spend limit, Solana ApproveChecked accepted as TransferChecked in the TypeScript facilitator (a complete payment bypass in local tests), and SIWx signing relayed login messages for other domains. The x402 Foundation had fixed all three in the August 18 releases. (source)
A bug in RingRTC, the open-source library behind Signal's voice and video calls, lets the other party on a call flood the call's state-machine event queue so a local hang-up gets stuck behind the backlog, and audio (possibly video) keeps flowing to them after the victim thinks the call ended. Affects every Signal client (Android, iOS, Desktop) embedding RingRTC before 2.72.0. Fixed in RingRTC 2.72.0 (released Sep 4 2026, disclosed Oct 20); a conceptual PoC is public, no known exploitation.
2026-10-22: No known exploitation; CISA has not added it to KEV and NVD lists it as awaiting analysis. (source)
2026-10-22: SecurityWeek: the hang-up was queued behind peer events with no rate limit or priority; the fix makes call termination bypass the queue. Users should update Signal and check the call indicator after hanging up. (source)
2026-10-22: Closed on pwn.watch: the fix shipped Sep 4 (RingRTC 2.72.0), there is still no known exploitation and no new developments, so this is now a patch-and-move-on item. Make sure Signal is updated on every device. (source)
