On 22 October 2026 Microsoft's Security Update Guide published CVE-2026-83938, 'Azure Kubernetes Configuration Service Elevation of Privilege Vulnerability': missing authentication for a critical function (CWE-306) in Azure Kubernetes Configuration Service allows an unauthorised attacker to elevate privileges over a network. Microsoft rates it Critical with a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Microsoft's FAQ says the vulnerability has already been fully mitigated by Microsoft, there is no action for users of the service to take, and the CVE is published to provide further transparency. Microsoft lists it as not publicly disclosed and not exploited. It was one of six Microsoft cloud-service CVEs published that day; the others are on their own desk cards. Primary: Microsoft Security Response Center; CVE record.
Microsoft Security Response Center — CVE-2026-83938, Azure Kubernetes Configuration Service Elevation of Privilege Vulnerability (22 Oct 2026)
On 22 October 2026 Microsoft's Security Update Guide published CVE-2026-108456, 'Azure AI Foundry Elevation of Privilege Vulnerability': server-side request forgery (CWE-918) in Azure AI Foundry allows an authorised attacker to elevate privileges over a network. Microsoft rates it Critical with a CVSS 3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N). Microsoft's FAQ says the vulnerability has already been fully mitigated by Microsoft, there is no action for users of the service to take, and the CVE is published to provide further transparency. Microsoft lists it as not publicly disclosed and not exploited. It was one of six Microsoft cloud-service CVEs published that day; the others are on their own desk cards. Primary: Microsoft Security Response Center; CVE record.
Microsoft Security Response Center — CVE-2026-108456, Azure AI Foundry Elevation of Privilege Vulnerability (22 Oct 2026)
Kaspersky's Global Research and Analysis Team (GReAT) said on 22 October 2026 that in early 2026 it identified a complex APT attack on diplomatic agencies in Tajikistan, Uzbekistan and Turkmenistan that used a UEFI bootkit it named BlackX, which it found to be similar to the BlackLotus bootkit. Kaspersky says the attackers deployed BlackX after compromising victim networks and obtaining administrator privileges, dropping an installer (inst.exe) and an RC4-encrypted file (PVMDIJGKAX2) that write files to the system and UEFI partitions to exploit the Baton Drop vulnerability (CVE-2022-21894) and install custom Machine Owner Keys (MOK), allowing arbitrary EFI files to load. Because BlackLotus source code has never been published, Kaspersky says the attackers either reverse-engineered BlackLotus or bought its source code. The UEFI payload injects a kernel driver, signed with a since-revoked certificate of 'Wenjiang District Mingyu Network Technology Service Studio', that disables security-product callbacks, tampers with ETW providers and protects the bootkit files; it drops user-mode espionage payloads: a RAT that uses Google Drive, OneDrive or Yandex.Disk for command and control, and an OLLVM-obfuscated DLL Kaspersky calls OxiDLLRunner, side-loaded by a legitimate googleupdate.exe, that runs a Rust payload talking to www[.]archivetj[.]com. Kaspersky attributes the attack to APT41 with medium confidence, citing the 'xdd' identifier shared with a FishMonger kernel implant described by ESET in June 2026, DLL side-loading and OLLVM obfuscation. Kaspersky says the targeted machines were fully patched: the Baton Drop fix revokes the 'Windows Production PCA 2011' certificate only when an administrator triggers it manually, Microsoft's planned automatic 'Enforcement Phase' has not been implemented, and the certificate's expiry on 19 October 2026 does not stop vulnerable binaries loading unless it is blocklisted. Microsoft's own guidance says the mitigations for the related BlackLotus Secure Boot bypass (CVE-2023-24932) are included in Windows security updates since 9 July 2024 but are not enabled by default, and that this malware requires physical or administrative access to the device. Primary: Kaspersky Securelist. Updated 23 Oct 2026: The Hacker News reported the research. (source: The Hacker News)
Kaspersky Securelist — New BlackX UEFI bootkit exploiting Baton Drop (22 Oct 2026)
Eye Security's research team said on 22 October 2026 that between November 2025 and March 2026 it actively disabled the vulnerable update mechanism in Time4Popcorn, a fork of the Popcorn Time BitTorrent streaming client, by executing code on systems running it. The flaw is CVE-2026-30612, which the CVE record describes as allowing a remote attacker to execute arbitrary code through updater.exe on Windows and PT.updd on macOS in Time4Popcorn for Windows up to 6.2.1.18, for macOS up to 6.2.1.17 and for Android up to 3.5.0.173; CISA's ADP enrichment scores it CVSS 3.1 9.8. Eye Security says it found an Updater.exe at a client trying to reach the lapsed domain popcorntimeupd.xyz. After registering it, Eye found the updater would download and run any executable named in a JSON reply with NT AUTHORITY\SYSTEM privileges, with no code signing and over unencrypted HTTP; on macOS a pushed update ran as root. It estimates it encountered about 2.5 to 3.0 million Windows hosts and 250,000 to 350,000 macOS hosts, connecting mostly from home ISPs but also from government, military and corporate networks around the world. Eye says its update only stopped and disabled the updater service, with no telemetry or file deletion, and that it had to adjust the code to get past endpoint products that flagged it. It says more than a million systems were updated by December 2025, it sent over 2 million update downloads in total, and update requests had fallen 98% by 1 March 2026. In late March it handed the 15 domains it controlled to The Shadowserver Foundation; some other update domains are still owned by third parties. Eye did not touch Android, where updates need user interaction, and says the application itself remains unsafe: it is built on a 2014 Chrome engine with the sandbox disabled, loads content over plain HTTP and loaded JavaScript from abandoned domains, and Eye has a proof of concept that runs calc.exe through JavaScript. Primary: Eye Security. Updated 23 Oct 2026: BleepingComputer reported the research. (source: BleepingComputer)
Eye Security — Operation IXIM: Preventing a botnet of millions of Popcorn Time users (22 Oct 2026)
HPE's security bulletin HPESBNW05162 rev.1, released 22 October 2026, lists 72 CVEs in the HPE Networking Wireless Operating Systems AOS-8 and AOS-10 for Mobility Conductors, Controllers, Gateways and Access Points. HPE rates eight of them 10.0 under CVSS 3.1: CVE-2026-79844 and CVE-2026-79850 (authentication bypass leading to remote code execution in AOS-10 and AOS-8), CVE-2026-79845 (authentication bypass in the PAPI protocol of AOS-10 allowing unauthorised access and modification of sensitive data), CVE-2026-79846 (unauthenticated command injection in AOS-8), CVE-2026-79848 and CVE-2026-79849 (unauthenticated SQL injection allowing remote code execution in AOS-8), and CVE-2026-79847 and CVE-2026-79851 (unauthenticated buffer overflows leading to remote code execution in AOS-10). A further 25 are rated between 9.0 and 9.8, among them unauthenticated command and SQL injection in the PAPI protocol and an authentication bypass in the AOS-8 SSH daemon. HPE lists affected versions as AOS-10.8.x.x: 10.8.1.1 and below, AOS-10.7.x.x: 10.7.2.6 and below, AOS-10.4.x.x: 10.4.1.13 and below, AOS-8.13.x.x: 8.13.3.0 and below and AOS-8.10.x.x: 8.10.0.23 and below. It recommends upgrading to AOS-10.8.x.x: 10.8.1.2 and above, AOS-10.7.x.x: 10.7.2.7 and above, AOS-10.4.x.x: 10.4.1.14 and above, AOS-8.13.x.x: 8.13.3.1 and above or AOS-8.10.x.x: 8.10.0.24 and above. HPE says versions that have reached End of Maintenance are presumed to be affected and are not covered by the advisory. HPE says the vulnerabilities were generally discovered by its internal security research and that it 'is not aware of any public discussion or exploit code that targets the listed vulnerabilities as of the release date of this advisory'. It adds: 'Customers are strongly urged to patch their instances due to the complexity, breadth, and impact of these vulnerabilities.' Until patches are applied, HPE recommends restricting the CLI and web-based management interfaces to a dedicated layer 2 segment/VLAN and/or controlling them with firewall policies at layer 3 and above. HPE published CVE records citing the bulletin on 22 October (UTC), and CISA's ADP enrichment on the seven 10.0-rated HPE records lists exploitation as none. When checked on 23 October, the CVE list entry for CVE-2026-79845 was an unrelated record assigned by VulDB, not an HPE record. Primary: HPE security bulletin; vendor: HPE CVE records. Updated 23 Oct 2026: BleepingComputer reported the bulletin, noting that ArubaOS powers Aruba Networking enterprise wireless infrastructure. (source: BleepingComputer)
HPE — HPESBNW05162 rev.1 - Multiple Vulnerabilities in HPE Networking Wireless Operating Systems (AOS-10 & AOS-8) (22 Oct 2026)
Security firm V12 said on 22 October 2026 that it found 25 vulnerabilities in the x402 codebase, the open standard that lets software such as AI agents pay for an API call inside an ordinary HTTP exchange (a server answers 402 Payment Required, the client signs a payment and retries). V12 described three it rated critical. First, the documented default client setup enforced no per-payment limit or total budget, so, according to V12, a hostile API could turn a routine request into a request for the wallet's full balance of a compatible token, and with an automatic signer and no application-supplied policy the client could sign it. Second, the TypeScript Solana facilitators did not check the instruction type, so a token approval, which moves no tokens, was accepted as a payment in V12's local test; V12 called it "a complete payment bypass" and says the test did not submit a live transaction. Third, the Sign-In-With-X client signed login messages without checking that the website named in them was the one it had contacted, which V12 says could let a malicious server log in to another site as the agent's wallet. V12 says it reported the 3 critical and 13 high-severity findings to the x402 team on 12 August 2026 and that the 3 critical flaws were fixed by 20 August. The x402 Foundation's TypeScript changelogs for 2.23.0 list the matching changes: client spendControls that by default allow only recognised pegged assets with a $1 USD cap, a required origin check before signing Sign-In-With-X messages, and a validation guard for TransferChecked in the Solana package. Primary: V12; vendor: x402 Foundation changelog. Updated 23 Oct 2026: according to The Hacker News, neither V12 nor the x402 Foundation has publicly reported attacks using the flaws, the foundation has published no security advisory for them, and npm audit and PyPI listed no advisories for the last releases before the fixes as of 23 October. (source: The Hacker News)
V12 — 25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings (22 Oct 2026)
On 22 October 2026 Microsoft's Security Update Guide published CVE-2026-97785, 'AAD App Proxy Elevation of Privilege Vulnerability': improper authentication (CWE-287) in AAD App Proxy allows an unauthorised attacker to elevate privileges over a network. Microsoft rates it Critical with a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N), and the CVE record names the affected product Microsoft Entra application proxy. Microsoft's FAQ says the vulnerability has already been fully mitigated by Microsoft, there is no action for users of the service to take, and the CVE is published to provide further transparency. Microsoft lists it as not publicly disclosed and not exploited. Primary: Microsoft Security Response Center; CVE record. Updated 24 Oct 2026: this card previously covered six Microsoft cloud-service CVEs published the same day; the other five now have their own desk cards (Azure Kubernetes Configuration Service CVE-2026-83938, VM Inspector for Azure Virtual Machines CVE-2026-110063, Azure Pipelines CVE-2026-105014, Azure AI Foundry CVE-2026-108456 and Exchange Online CVE-2026-96185). (source: Microsoft Security Response Center)
Microsoft Security Response Center — CVE-2026-97785, AAD App Proxy Elevation of Privilege Vulnerability (22 Oct 2026)
ESET researchers Anton Cherepanov and Peter Strýček published research on 22 October 2026 on MythicRatatoskr, a previously unknown Go-based backdoor that reaches a command-and-control server hosted inside Yggdrasil, a decentralised, experimental IPv6 mesh network. According to ESET, UAC-0099 gained initial access to a grain logistics company in Ukraine on 16 July 2025 through a spearphishing email with a malicious attachment that led to its MATCHBOIL downloader and MATCHWOK backdoor; the next day MythicRatatoskr was deployed, and ESET believes it was later used to deliver a SOCKS5 server. ESET says data-wiping activity followed on 17 September 2025, carried out by deploying the SDelete utility through Active Directory Group Policy, which it calls standard Sandworm tactics. ESET attributes the initial stage to UAC-0099 and the wiping to Sandworm with high confidence and assesses with high confidence that UAC-0099 handed off access to Sandworm, but says it cannot yet tell which group operated MythicRatatoskr. ESET says it has not seen the backdoor anywhere else, found indications that a Linux variant may exist, and notes Yggdrasil is not designed to provide anonymity; it says blocking the public peer addresses is a viable mitigation. ESET presented the findings at LABScon on 18 September 2026 and Virus Bulletin on 16 October 2026. Source: ESET WeLiveSecurity (22 Oct 2026). Updated 23 Oct 2026: according to Reuters (as published by iTnews), ESET said it had not previously observed state-linked attacks using the network and could not confirm whether the attack disrupted grain operations, and a Microsoft spokesperson said SDelete is a legitimate administrative utility that can be misused by attackers who already have access. (source: iTnews)
ESET WeLiveSecurity — MythicRatatoskr: An Yggdrasil-enabled backdoor deployed in a UAC-0099-Sandworm collaboration (22 Oct 2026)
Capcom Co., Ltd. said in a press release on 22 October 2026 that certain customer information tied to CAPCOM ID, the unified account used for its web services and needed to play some Capcom games online, was subject to unauthorised access by a third party. Capcom says the affected information (as of 22 October) is 11,774,247 records worldwide of email addresses plus system identifiers (account creation date and time, last login date and time, number of logins and the client IP address used at the last login); 43 of those records also included date of birth, gender, country/region and nickname, and login passwords on 196 accounts were changed without authorisation and have since been reset. Capcom says it has not confirmed any compromise of passwords originally set by customers and that credit card information was not included. According to Capcom's timeline, it detected suspicious activity on 19 October and confirmed unauthorised access the same day, set up an incident response headquarters on 20 October and confirmed customer information was affected, and reported the incident to the Osaka Prefectural Police and Japan's Personal Information Protection Commission on 21 October. Capcom says it has identified and addressed the attack method, without saying what it was; services that use CAPCOM ID, including games, remain available; it will notify affected customers and has set up dedicated support channels by region, including Asia (excluding Japan) and Oceania. Capcom warns that the information could be misused for fraudulent emails or messages impersonating Capcom. BleepingComputer reported the disclosure on 22 October. Source: Capcom press release (22 Oct 2026); wire: BleepingComputer (22 Oct).
Capcom — Notice and Apology Regarding Customer Information Affected Through Unauthorized Access (press release, 22 Oct 2026)
Trend Micro's Zero Day Initiative (ZDI) lists two Linux vulnerabilities, ZDI-CAN-33549 and ZDI-CAN-33774, each rated CVSS 9.0 and reported to the vendor on 21 October 2026. According to The Hacker News (22 Oct), both are remote code execution flaws in KSMBD, the Linux kernel's built-in SMB server, and were sent to public mailing lists without patches. The Hacker News says ZDI-CAN-33774 needs no authentication and exposes any server running KSMBD on port 445: a race in how KSMBD assigns its handler table lets a burst of short SMB1 packets followed by an SMB2 packet make workers read past the end of a buffer, with a path to writing past it once an attacker has access to a share. It says ZDI-CAN-33549 is an integer underflow in KSMBD's SMB Direct path that needs an RDMA-capable interface (hardware or the rxe software driver), a writable KSMBD share and a client negotiating SMB Direct. According to The Hacker News, as of Thursday 22 October neither flaw had a named fix in the mainline kernel or linux-next, and neither has a CVE, since the kernel assigns CVEs only after a stable-tree fix. Phoronix (22 Oct) says a patch for ZDI-CAN-33549 sits in a Git branch intended for Linux 7.5, and that the reports appear to have been sent to the public list by mistake. The Hacker News says Red Hat Enterprise Linux does not include KSMBD by default, according to Red Hat's documentation. No exploitation has been reported. Sources: ZDI upcoming advisories; The Hacker News (22 Oct); Phoronix (22 Oct).
Zero Day Initiative — Upcoming advisories (ZDI-CAN-33549 and ZDI-CAN-33774, Linux, CVSS 9.0, reported 21 Oct 2026)
CISA said on 22 October 2026 that it, the Canadian Centre for Cyber Security (Cyber Centre) and partners are releasing joint guidance, Managing AI Token Consumption for Operational Resilience, to help organisations understand and manage token usage. CISA says unmanaged token consumption may contribute to rising and unpredictable costs, reduced service availability, degraded performance, token exhaustion, and denial-of-tokens or denial-of-wallet attacks. The Cyber Centre's version (ITSM.00.125) describes a denial-of-tokens attack as threat actors deliberately generating excessive AI usage to exhaust token allocations, consume budgets or trigger rate limits, and a denial-of-wallet attack as exploiting usage-based pricing to cause financial harm, for example with complex prompts or AI loops. The authoring agencies recommend a tiered model that ranks token allocation by business impact, with cyber defence, incident response and threat intelligence in the mission-critical tier, and risk assessments before letting AI agents operate autonomously. They also recommend monitoring unusual increases in token consumption as a potential indicator of data exfiltration, feeding AI token telemetry into a SIEM alongside identity, cloud and API logs, progressive usage alerts (the guide's example: 70%, 80% and 90% of quota), multi-provider architectures, and planning for reduced AI availability in critical infrastructure, including keeping non-AI and manual capabilities. Sources: CISA (22 Oct 2026); Canadian Centre for Cyber Security ITSM.00.125 (October 2026).
CISA — Managing AI Token Consumption for Operational Resilience (22 Oct 2026)
Arista Security Advisory 0199 (22 October 2026) documents CVE-2026-114625, an SQL injection flaw (CWE-89) in on-premises VeloCloud Orchestrator (VCO), the management portal for VeloCloud SD-WAN. Arista says any authenticated user can gain operator privileges and masquerade as a local 'superuser operator' user, reaching functionality meant for internal use only, and that successful exploitation may compromise the confidentiality, integrity and availability of the orchestrator and the data it manages. An attack needs network access to the VCO web interface and a valid authenticated session; the minimum role is Enterprise Read Only, the lowest built-in tenant role, and Arista says no configuration prevents the exposure. Arista says the issue was detected by Arista and is known to be actively exploited, and that Hosted (including Dedicated) VCO was impacted and has already been patched. Arista rates it CVSS 3.1 9.9 and CVSS 4.0 9.4. Affected on-prem releases: 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10 and 6.4.x before 6.4.2.12; end-of-support versions were not assessed. Arista lists two IP addresses seen conducting the attacks (74.82.197.86 and 38.54.50.151) and advises blocking them and checking logs for them. VeloCloud Gateway, VeloCloud Edge and Arista EOS-based products are listed as not affected. This is a separate flaw from the actively exploited VCO bug CVE-2026-93952 that Arista disclosed in September (see this desk's card). BleepingComputer reported the advisory on 22 October. Source: Arista Security Advisory 0199 (22 Oct 2026); wire: BleepingComputer (22 Oct). UPDATE (24 Oct 2026): CISA added CVE-2026-114625 to its Known Exploited Vulnerabilities catalog on 23 October 2026 (catalog version 2026.10.23), with a remediation due date of 26 October 2026 for US federal civilian agencies and forensic triage required. (source: CISA KEV)
