Fortinet's FG-IR-26-180, published on 13 October 2026, fixes CVE-2026-106173 in FortiSIEM. Fortinet titles it an arbitrary file write in the gRPC phQueryMaster service and describes a path traversal (CWE-22) that may let an unauthenticated attacker execute unauthorised code or commands with specially crafted packets. It rates the flaw Critical, 9.4 (CVSS 3.1). Only FortiSIEM 7.5.0 is listed as affected; 7.6 is not affected and FortiSIEM Cloud is not affected. The fix is 7.5.1. Fortinet gives a workaround: restricting access to TCP port 27918 prevents the issue. The flaw was found internally by Fortinet's product security team, and the advisory marks it as not known to be exploited. FortiSIEM collects logs and credentials for the systems it monitors and is widely run by managed security providers, and older FortiSIEM bugs have been exploited soon after disclosure, so a SIEM that accepts traffic from untrusted networks is worth treating as urgent. Released in the same Fortinet monthly batch as the critical FortiSandbox flaw CVE-2026-107656 (its own card). UPDATE (20 Oct, Horizon3.ai): Horizon3.ai published a technical analysis and released working exploit code on GitHub. It found the phQueryMaster gRPC service on TCP 27918 listens on all interfaces and does not ask clients for a certificate, so anyone who can reach the port can call it without logging in. Its SendQueryResult handler builds a file path from an attacker-supplied query-id without validation, so '../' sequences pick the directory, and a NUL byte in the query-id cuts off the file name the server would otherwise append, letting an attacker overwrite an existing file in place while keeping its owner and permissions. Horizon3.ai's exploit overwrites /opt/charting/redishb.sh, a Redis health-check script cron runs every 60 seconds, which turns the file write into code execution; a second variant creates a new file with an exact name. Horizon3.ai says no FortiSIEM application log clearly shows the attack. Fortinet's advisory still marks the flaw as not known to be exploited (checked 21 Oct). Wire: The Hacker News (20 Oct).
Fortinet PSIRT FG-IR-26-180 — FortiSIEM arbitrary file write in gRPC phQueryMaster (13 Oct 2026)
Fortinet published FG-IR-26-185 on 13 October 2026 for CVE-2026-107656, a critical authentication bypass using an alternate path or channel (CWE-288) in the FortiSandbox web management GUI. A remote, unauthenticated attacker can send crafted HTTP requests to get past authentication, and Fortinet lists the impact as executing unauthorised code or commands. It rates the flaw 9.6 (CVSS 3.1). FortiSandbox 5.0.0 to 5.0.6 and 4.4.0 to 4.4.9 are affected, as are FortiSandbox PaaS 5.0.0 to 5.0.6 and every PaaS 4.4 release; the 5.2 branch is not affected. Fortinet's product security team found it internally, and Jason McFadyen of TrendAI Research also reported it. The advisory marks it as not known to be exploited. It was part of Fortinet's 13 October monthly PSIRT release, which also fixed a separate critical FortiSIEM flaw (CVE-2026-106173, its own card) and lower-rated FortiSandbox, FortiOS, FortiManager, FortiAnalyzer and FortiMail issues. FortiSandbox sits in the mail and web inspection path and holds samples of suspicious files, so an exposed admin interface is a high-value target. Wire: Cyber Security News (13 Oct).
Fortinet PSIRT FG-IR-26-185 — FortiSandbox improper access control and session management in the web management interface (13 Oct 2026)
Microsoft's October 2026 security updates, released on 13 October 2026, fix one actively exploited zero-day and two publicly disclosed flaws. CVE-2026-96951 is a Windows Shell security feature bypass (command injection) that lets an unauthenticated attacker get around Mark of the Web protections over a network once a user opens a crafted file or link; Microsoft rates it Important, CVSS 8.8, and marks it 'Exploitation Detected'. It has not said who reported it or how it was used. CVE-2026-108398 is a .NET Framework untrusted search path flaw (CVSS 8.8) that lets a local, authenticated attacker register a crafted .NET assembly for loading by a protected process and bypass Windows Defender Application Control (WDAC); it was publicly disclosed and found by James Forshaw of Google Project Zero, but is not marked exploited. CVE-2026-92707 is a publicly disclosed MessagePack-CSharp denial of service (CVSS 5.3). BleepingComputer counts a record 1,411 flaws fixed on Patch Tuesday itself, 70 of them Critical (57 remote code execution), not counting 348 cloud and other fixes released earlier in the month. Critical remote code execution bugs rated CVSS 9.8 by Microsoft include Windows DHCP Server (CVE-2026-96934), Windows Message Queuing (CVE-2026-100202), Microsoft QUIC (CVE-2026-100219, CVE-2026-105016), Windows Text Shaping (CVE-2026-97814) and several Outlook bugs, all rated 'Exploitation Less Likely'. October is also the last update for Windows 11 24H2 Home and Pro and Windows 10 Enterprise LTSB 2016. UPDATE 15 October: the WA Government's Cyber Security Unit (WASOC) issued advisory 20261015001 for CVE-2026-96951, saying Microsoft is aware of exploitation and CISA has added it to its Known Exploited Vulnerabilities catalogue. WASOC has had no reports of exploitation on WA Government networks and recommends applying Microsoft's fix within expected timeframes. UPDATE 16 October: Microsoft added a known issue to the KB5127648 release notes for Windows 11 24H2, 25H2 and 26H2: after the update, some devices cannot turn Smart App Control back on in the Windows Security app if it was off, and the option may be greyed out. Devices that already have Smart App Control on are not affected and stay protected. Microsoft gives a registry workaround and two Feature Preview Group Policies for managed devices, and says a fix will come in an upcoming release. Separately, on 13 October MSRC published a blog proposing 'risk cohorts': provisional groups of CVEs that need the same check of a customer's environment (for example, 64 RDP client, gateway and server CVEs share the question of which roles are deployed and exposed; an Office cohort of 119 CVEs includes 23 rated Critical and 17 needing no user interaction). MSRC says these are not a new classification or prioritisation framework, do not change its update guidance, and do not appear in the Security Update Guide for now. UPDATE 16–17 October: Microsoft's NTLMv1 guidance (KB5066470) and message-centre post MC1508562 say the October 2026 update changes a default by design: on Windows 11 24H2, 25H2 and 26H2 and Windows Server 2025 devices without Credential Guard, if the BlockNtlmv1SSO registry value has never been set, Windows now uses Enforce mode instead of Audit mode and blocks NTLMv1-derived single sign-on credentials. Microsoft says this is a planned change, not a known issue, but it can break Wi-Fi, Ethernet and VPN connections that use MS-CHAPv2 (for example PEAP-MSCHAPv2) on domain-joined devices; The Register (16 Oct) reported it, and at least one university says Windows clients lost access to its MS-CHAPv2 wireless network. The temporary workaround is to set HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BlockNtlmv1SSO (REG_DWORD) to 0, which allows the requests and logs warning Event ID 4024; blocked attempts log Event ID 4025. Microsoft says Audit mode should only be a scoped, temporary exception. UPDATE 16–19 October: Microsoft's Windows release health dashboard (issue opened 16 Oct, status Mitigated) and the Exchange Team blog (16 Oct) say the October 2026 Windows Server updates can make on-premises Exchange Server 2016, 2019 and Subscription Edition unstable: users may be unable to sign in to Outlook on the web (OWA), mail sent from Outlook can stay in the Outbox, mail queues grow, mailbox replication can fail and some DAG members cannot reach quorum. OWA may show 'MapiExceptionMdbOffline ... (hr=0x80004005, ec=1142)' with Event ID 1006. The cause is a new default limit on Endpoint Mapper memory (512 simultaneous Endpoint Lookup calls), which busy Exchange servers can exceed. The affected updates are KB5126646 (Server 2025), KB5126655 (Server 2022), KB5126651 (Server 2019) and KB5126868 (Server 2016). Microsoft says this is not caused by the October Exchange security updates, impact depends on server load and some servers may never see it, and customers should not uninstall the Windows updates. Its temporary workaround is to set HKLM\SOFTWARE\Microsoft\Rpc\EpmapSavedContextCap (REG_DWORD) to 65536, reboot, and raise it if the problem returns; a further mitigation is available through Microsoft Support for business, and a fix is under investigation. BleepingComputer reported it on 19 October.
Microsoft Security Response Center — October 2026 Security Updates release notes (13 Oct 2026)
Microsoft Windows Command Injection Vulnerability. Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network. Apply vendor mitigations. Check the NVD record and the vendor advisory for affected versions and the patch.
Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability. Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands. Apply vendor mitigations. Check the NVD record and the vendor advisory for affected versions and the patch.
SAP's 13 October 2026 Security Patch Day lists 16 new security notes and 4 GitHub security advisories, led by CVE-2026-89111 (GHSA-4mv3-jxxm-9cx2), rated Critical 10.0. SAP says the Cloud SDK for Python, its official toolkit for Python apps and AI agents on SAP Business Technology Platform (BTP), has an OAuth2 server-side request forgery flaw affecting multi-tenant BTP applications: an attacker who controls the tenant_subdomain parameter can redirect OAuth2 token requests to a server they control and capture the application's client credentials. Versions before 0.45.2 are affected. The same patch day also rates as Critical CVE-2026-89110 (9.9, broken access control in NetWeaver Visual Composer VC70RUNTIME 7.50), CVE-2026-89107 (9.9, code injection in S/4HANA Manage Substitution/Validation Rules, S4CORE 105 to 109) and CVE-2026-89108 (9.1, missing authorisation in Manufacturing Integration and Intelligence Configuration Service). SAP has not marked any of these as exploited.
SAP Security Patch Day — October 2026 (13 Oct 2026)
Ivanti disclosed CVE-2026-104935 in Ivanti Connect Secure (ICS) on 13 October 2026 and said it is aware of limited exploitation in the wild, urging customers on affected versions to act immediately, upgrade to the fixed release and run the Integrity Checker Tool regularly. The CVE record describes an authentication bypass by spoofing that lets a remote unauthenticated attacker execute arbitrary commands; ICS 22.7R2.14 and earlier are not affected. Volexity, which found and reported the issue, says a previously unknown actor it tracks as UTA0576 exploited a fully patched 22.8R2.4 appliance from 3 October 2026. The chain abused a request-routing bypass in the public welcome.cgi page (an X-DSCGI-PATH header pointing at an internal script), a race in the wu.cgi upload handler to run a briefly written Perl script, and a separate privilege escalation in the dsinvoked broker's trust of DSCache data to reach root. Ivanti tracks the bypass and RCE together as CVE-2026-104935; BleepingComputer reports the privilege escalation is still being fixed. The actor deployed no web shell, re-exploited the device for each command, tampered with debug and audit logs and evaded the Integrity Checker. Post-exploitation targeted Active Directory: LDAP service credentials stored on the appliance, LAPS passwords, BitLocker recovery keys, Kerberoasting and password spraying. Defused reports first exploitation signs from 1 October, and Shadowserver tracks more than 5,500 internet-exposed ICS instances. CISA added CVE-2026-104935 to its Known Exploited Vulnerabilities catalog on 13 October, with a 16 October patch deadline for US federal agencies, and issued an alert saying it is aware of actors using the flaw for credential theft and data exfiltration. CISA warns the Integrity Checker may miss exploitation because commands run in memory, so confirming compromise needs network and memory forensics, and it says Connect Secure 22.8 reaches end of life on 31 January 2027. Rapid7 reports Ivanti had found part of the issue internally and fixed it in 25.1.3.0 in July, and exploitation came while backports to other branches were still under way; iTnews lists 25.1.1.2 among the fixed builds. Volexity assesses with medium confidence that UTA0576 used large language models to build its tooling. On 14 October The Hacker News reported that Previdian honeypot sensors had logged 105 exploitation attempts from 50 unique IPs (mainly Singapore and the US) as of that date, using the X-DSCGI-PATH header to reach an internal CGI handler and upload Perl scripts packaged as ZIP files that return execution-test markers; payloads seen so far were mostly weaponisation probes rather than full malware drops. Sample source IPs published by Previdian include 216.73.160[.]59, 216.73.160[.]61, 216.73.160[.]210 and 45.8.19[.]111. UPDATE (23 Oct 2026): the privilege escalation now has its own CVE record, CVE-2026-111357 (published 15 October, updated 16 October): Ivanti Connect Secure 22.8R2.4 mishandles how the dsinvoked broker trusts DSCache configuration data, leading to root, 'as exploited in the wild in October 2026'. The record scores it CVSS 3.1 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) and lists no fixed version as of its 16 October update. Volexity's 13 October post says Ivanti is working on a fix that will be included in a future release 'in the coming weeks'. CVE-2026-111357 was not in CISA's KEV catalog as of the 23 October catalog release (version 2026.10.23). (source: CVE-2026-111357 record (cve.org); Volexity)
Ivanti — October 2026 Security Update (13 Oct 2026; links the Connect Secure CVE-2026-104935 advisory)
Bloom Security disclosed 'SlugFest' on 13 October 2026, a takeover path in npm Trusted Publishing, the OpenID Connect (OIDC) feature that lets a GitHub Actions workflow swap a short-lived identity token for an npm publishing credential instead of storing a long-lived token. Until a binding completed its first successful publish, npm recorded the trusted repository only by its human-readable owner/repo name (the 'slug'), not by GitHub's permanent repository and owner IDs. If the maintainer then renamed, transferred or deleted that repository, or the owner account was renamed or deleted, anyone could create a repository at the freed name, add a workflow file with the expected filename, and receive a valid publish credential for a package they did not own. No stolen token or account access is needed, and a release pushed this way carries a valid Sigstore provenance attestation, naming the attacker's repository. Bloom's scan found more than 1,500 vulnerable packages with over 10 million total downloads and more than a million a month. It is not publishing the list. It ran the attack end to end only against packages and repositories it controlled, and says it is unknown whether anyone abused the flaw in the wild. Bloom says npm's GitLab trusted publishing integration had the same weakness. Bloom reported the issue through GitHub's HackerOne programme on 6 June; GitHub validated it on 9 June, and Bloom says follow-ups after 8 July went unanswered until it found the fix when it checked again before publishing. GitHub's changelog of 2 October 2026 says unvalidated npm trusted publishing configurations now expire 48 hours after creation and can no longer authorise publishing, and that npm now rejects trusted publishing tokens from GitHub Actions issue_comment events, alongside the existing pull_request_target block. GitHub told Help Net Security it shipped fixes after validating the bug bounty report; its statement does not say whether older bindings were re-bound to permanent IDs. Bloom's broader point is that AI coding agents now pull in about 70 packages a month on a typical endpoint (close to 350 on developer machines), usually without review, so a hijacked package can spread without fooling a human. Primary: Bloom Security; vendor: GitHub changelog; wire: Help Net Security and Cyber Security News (13 Oct).
Bloom Security — SlugFest: millions of AI agents download exposed npm packages (13 Oct 2026)
Advantech published a security advisory on 12 October 2026 for the ADAM-3600 EdgeLink, a remote terminal unit (RTU) used for industrial data acquisition and remote monitoring. It fixes 30 vulnerabilities, CVE-2026-43829 to CVE-2026-43858, found by Simone Bossi and Raffaele Bova of Nozomi Networks and coordinated with the Cyber Security Agency of Singapore (CSA), which issued alert AL-2026-149 on 20 October; Canada's Cyber Centre flagged the advisory the same day (AV26-1065). Every firmware version before EdgeLink 2.8.5.0 is affected. The most serious are rated critical under CVSS 4.0: CVE-2026-43836 (9.3) lets an attacker forge a packet to run arbitrary commands with maximum privileges, and CVE-2026-43844 (9.3) bypasses authentication in the device's proprietary protocol; CVE-2026-43845 (9.2) bypasses authentication through the password-reset mechanism; and stack buffer overflows in the log-message function (CVE-2026-43831, unauthenticated), the login function (CVE-2026-43838) and, when the SafeEnhancement feature is enabled, password and cookie parsing (CVE-2026-43829 and CVE-2026-43832, unauthenticated) can give code execution (all 9.2). Other fixes cover command injection while a firmware file is verified (CVE-2026-43830) and upload of a forged firmware image that could permanently compromise the device (CVE-2026-43835), unlimited brute-forcing of the administrator password over the proprietary protocol even with SafeEnhancement on (CVE-2026-43847), authenticated root-level command injection, arbitrary file read and file write, recovery of administrator credentials from an encrypted EdgeLink project file (CVE-2026-43854), and several unauthenticated crashes of the logging and licence-manager services. Advantech says EdgeLink 2.8.5.0 fixes all 30 and adds asymmetric digital signatures for firmware upgrades. Neither Advantech nor CSA reports exploitation. Primary: Advantech advisory (12 Oct); government: CSA AL-2026-149 (20 Oct).
Advantech — Security advisory: Vulnerabilities identified in ADAM-3600 (v1.0, 12 Oct 2026; PDF)
Tencent Zhuque Lab published a full write-up and working demos on 12 October 2026 for CVE-2026-74580, which it calls Vghost. The bug is in the Linux kernel's vhost subsystem, which accelerates network and other I/O for virtual machines and containers through device nodes such as /dev/vhost-net and /dev/vhost-vsock. vhost caches the memory mapping behind each virtual ring and treats a cache hit as proof the region was already checked, but the cache was not cleared when the VHOST_SET_VRING_ADDR or VHOST_SET_VRING_NUM commands changed a live ring's addresses or size. With a device IOTLB attached, the old mapping keeps being used and the kernel copies data outside the mapped region. On a host this gives a local user deterministic arbitrary kernel read and write, a KASLR bypass and root, with no heap grooming or race. Where a guest's virtio device sits behind a virtual IOMMU with iommu_platform on, an untrusted guest can trigger the same bug to make the host kernel write out of bounds into the host's QEMU process, which can be used to hijack or crash it. Tencent reproduced local-user-to-root on Ubuntu 26.04, RHEL 9.8, Amazon Linux 2023, Azure Linux 3.0 and Oracle Linux 10.2; on Ubuntu the node is limited to the kvm group, but on the other four it was world-accessible (mode 0666). The flaw dates from a 2017 change (Linux 4.11) combined with a 2020 change (5.9). The kernel.org CNA scores it 8.8 with scope changed; Red Hat scores 7.3 (scope unchanged), Amazon 7.8 and Oracle 7.3. Tencent says its Corvus AI multi-agent system found the bug; the fix (commit de845981da67) was released on 3 August and credits it with an Assisted-by line. No exploitation is reported. Primary: Tencent Zhuque Lab write-up and the upstream kernel commit; The Hacker News background.
Tencent Zhuque Lab — Vghost: Beyond the Privilege Boundary (CVE-2026-74580, 12 Oct 2026)
Wordfence said on 12 October 2026 that its Argus AI system found CVE-2026-39919, a critical heap buffer overflow in the Ghostscript PostScript and PDF interpreter, during a WordPress 7.1 assessment on 23 August. A PDF containing a JPEG 2000 image with low-bit-depth samples and mismatched component resolutions makes Ghostscript write 1,024 bytes into a 256-byte buffer. Wordfence rates it 9.8 and turned it into unauthenticated remote code execution on a purpose-built WordPress test server, where WordPress calls ImageMagick through PHP Imagick to make a PDF thumbnail and ImageMagick launches Ghostscript. Ghostscript 9.21 to 10.07.1 contain the vulnerable code. In its 15 September tests, the Ghostscript packages in Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04, Fedora 44, AlmaLinux 10, Alpine and the official WordPress Docker image were all still affected. Its two exploits did not work against those stock packages in 10,240 attempts, but did work after changes to fonts, language settings and one system library, so exploitation depends on the environment. Stock WordPress does not allow anonymous Media Library uploads; an attacker needs some way to upload a PDF that the site then renders. Artifex fixed the flaw in Ghostscript 10.08.0 on 8 September and backported fixes to older lines. Wordfence has seen no exploitation in the wild. Any application that renders untrusted PDFs through Ghostscript is in scope, not only WordPress.
Wordfence — Argus discovers critical vulnerability in Ghostscript, the program that turns uploaded PDFs into thumbnails (12 Oct 2026)
Docker said on 12 October 2026 that from 26 August 2024, converting a Docker Hub personal account into an organization also re-assigned that account's personal access tokens (PATs) to the account named as the new owner, without rotating the secret and without asking or telling that owner. An attacker could create an account and a PAT, convert it, name a target user as owner, and keep using the token with the target's registry scope, so they could pull, push or delete images in the target's repositories and in organizations the target could reach. Docker rated it critical because it allowed publishing images under a legitimate name. It did not give web access or let anyone change passwords, email or two-factor settings. Researchers Peter Molnar and Krisztian Hozak reported it on 30 September 2026 and Docker deployed a fix in under four hours. Docker says it reviewed every conversion back to August 2024, found no evidence of exploitation after examining 304,000 pushes made with transferred tokens, emailed affected users and organization owners on 2 October, and deactivated transferred PATs on 8 October unless owners asked to keep them. Conversion no longer transfers PATs and now needs the named owner's consent.
Docker — Docker Hub security advisory: personal access tokens transferred during account-to-organization conversions (12 Oct 2026)
