Operation ShadowCloud is a sophisticated cyber intrusion campaign targeting government entities in Asia and Africa. It uses novel backdoors named GitDoor and GraphDoor deployed via the legitimate MeshAgent utility. These backdoors hide command-and-control communications by leveraging cloud platforms such as Microsoft SharePoint, GitHub, and Ably messaging services to evade network detection. The modular toolset supports on-demand plugin downloads and in-memory shellcode injection, enabling keylogging, screen capture, credential theft, and proxy deployment. The campaign employs DLL sideloading with legitimate executables to deliver encrypted payloads. Multiple GitHub repositories created since late 2024 are used for data exfiltration and command distribution. The operation uses advanced obfuscation techniques including control flow flattening and multi-stage payloads.
CVE-2026-90423 is a use-after-free (UAF) vulnerability in the RDMA/rxe component related to the On-Demand Paging (ODP) initialization error-handling path. The issue affects Microsoft product version 4.0. No CVSS score or detailed impact information is provided.
Astro is a web framework for content-driven websites. From 5.14.3 until 7.4.7, Astro's /_image endpoint compared the requested local-image path with the build output directory without preserving case on case-sensitive filesystems. A sibling directory whose path differed from the output directory only by letter case could therefore pass the containment check, allowing an unauthenticated requester to read image files accepted by the image service from outside the output directory. Exploitation required on-demand rendering with the @astrojs/node adapter, a case-sensitive filesystem, and a preexisting case-variant sibling directory; ordinary traversal to unrelated paths was already rejected. This issue is fixed in Astro version 7.4.7.
A vulnerability in Zephyr's arm64 MMU backend causes improper TLB invalidation, allowing user threads to retain access to stale memory mappings after page eviction. This flaw breaks memory isolation enforced by CONFIG_USERSPACE, enabling information disclosure and memory corruption, potentially leading to full system compromise. The issue affects arm64 builds with CONFIG_USERSPACE and CONFIG_DEMAND_PAGING enabled and demand-paged pages mapped into user memory domains. A fix changes the TLB invalidation to cover all ASIDs and both global and non-global entries, preventing stale translations from persisting.
CVE-2026-83394 is a vulnerability in Oracle Demand Planning versions 12.1 and 12.2 that allows a low privileged attacker with network access via HTTP to gain unauthorized access to critical data. Exploitation requires user interaction from someone other than the attacker. The vulnerability impacts confidentiality but does not affect integrity or availability. Oracle has included this vulnerability in its October 2026 Critical Patch Update advisory.
CVE-2026-101547 is a vulnerability in Oracle Demand Planning versions 12.1 and 12.2 that allows an unauthenticated attacker with network access via HTTP to perform unauthorized read and write operations on accessible data. Exploitation requires user interaction from someone other than the attacker and can impact additional Oracle products. The vulnerability has a CVSS 3.1 base score of 6.1, indicating medium severity with confidentiality and integrity impacts but no availability impact.
The report analyzes trends in the US cybersecurity job market for 2026, highlighting a 26% decline in overall cybersecurity job postings compared to 2025. Despite the overall decline, demand for AI-related cybersecurity roles, such as AI Security Engineers and Cyber Data Scientists, has surged significantly. The report emphasizes shifts in required skills rather than job titles and notes increased references to AI knowledge across various cybersecurity functions. Leadership roles like CISOs have seen a decline in postings, though some recovery is noted. The report does not indicate any specific security threat or vulnerability.
The Document Gallery WordPress plugin through 5.1.1 does not perform any capability or ownership check when generating a gallery on demand, allowing unauthenticated users to enumerate and disclose the titles, descriptions and direct file URLs of media attached to unpublished, private or trashed content.
This content describes a virtual conference event focused on Zero Trust security strategies and identity verification. The event aims to provide actionable insights on implementing Zero Trust architectures and leveraging AI for identity-based threat defense. It is not a security vulnerability or threat but rather an industry event announcement.
CVE-2026-15894 is a high-severity memory safety vulnerability in the Zephyr Bluetooth Mesh On-Demand Private Proxy solicitation handler. It involves copying a Solicitation PDU into a fixed 17-byte stack buffer without proper length bounds, allowing an attacker to overwrite the stack with attacker-controlled data. This flaw can be triggered remotely by sending crafted BLE advertisements without requiring pairing or authentication. The vulnerability can lead to remote code execution or denial of service. Fixed versions 4.3.2 and 4.4.2 address this issue by enforcing length checks before processing.
CVE-2026-98361 is a vulnerability in the Linux kernel's RDMA rxe driver where a missing write permission check in on-demand paging (ODP) write paths allows unprivileged users to overwrite read-only page cache memory. This flaw enables modification of files such as /etc/passwd or setuid binaries by registering an ODP memory region over a read-only mapping, similar in nature to Dirty COW. The issue was introduced by a commit that removed the HMM_PFN_WRITE check, causing endless pagefault loops and improper write access. The vulnerability is fixed by restoring the HMM_PFN_WRITE check in the rxe driver, preventing unauthorized writes to non-writable memory regions.
Polish dental software vendor FELG Dent suffered a data breach involving patient records and received a ransom demand. An attacker exploited insecure API endpoints to access sensitive patient and staff data, including personal identifiers and medical information. FELG estimates about 2 million patient records were affected. The attacker claims to hold about 10% of the database and threatens to sell it on a dark web forum after failed ransom negotiations. FELG has notified Polish authorities and is assisting affected dental practices with breach notifications under GDPR.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.2.4 and 12.0.2, a single message with a deeply nested object in its pattern can terminate a NestJS microservice using the TCP or RabbitMQ transport. ServerTCP#handleMessage and ServerRMQ#handleMessage pass a client-controlled non-string pattern to JSON.stringify to derive the handler lookup key; sufficiently deep nesting throws RangeError: Maximum call stack size exceeded, and the unhandled promise rejection terminates Node.js under its default behavior. An attacker who can reach the TCP port or publish to the consumed RabbitMQ queue or exchange can crash the service on demand; other transports are not affected because their patterns arrive as strings. This issue is fixed in versions 11.2.4 and 12.0.2.
AzuraCast versions before 0.23.8 contain a server-side request forgery (SSRF) vulnerability in the station webhook URL validation. The validation incorrectly rejects only literal link-local IP addresses but allows loopback and private network addresses, enabling a user with station-scoped WebHooks permission to configure webhooks targeting internal or private network resources. This can cause the server to send HTTP POST requests with station data to unintended internal endpoints. The vulnerability can be triggered on demand via a specific test endpoint. No patch was available at the time of the advisory.
AzuraCast versions before 0.23.8 have a vulnerability in the public On-Demand download endpoint that does not properly enforce playlist-level access controls. This flaw allows unauthenticated users to download media files that are meant to be excluded from On-Demand-enabled playlists, bypassing intended access restrictions and exposing private or restricted audio content.
In late August, an organization was compromised by INC ransomware affecting at least 175 endpoints. The attack unfolded over several weeks with a 17-day gap, indicating involvement of an initial access broker and a separate ransomware affiliate. Early activity included scheduled tasks with randomized names and lateral movement via RDP using compromised credentials. After the pause, attackers deployed AnyDesk for remote access, used Bring Your Own Vulnerable Driver (BYOVD) techniques to disable security controls, and executed ransomware using Impacket tools. Two ransom notes were found: the standard ransom demand and a secondary data leak threat note listing stolen files and threatening to contact media, employees, and partners within 48 hours to pressure the victim.
A vulnerability in the Linux kernel ARM breakpoint handling was resolved by removing the stub hw_breakpoint_cfi_handler(), ensuring that ARM_ENTRY_CFI_BREAKPOINT type breakpoints are only stolen when Control Flow Integrity (CFI) is actively used. This prevents unintended interception of breakpoints when CFI is not in use or when breakpoints are issued in userspace.
SLDP (Simple Layer-2 Discovery Protocol) is a lightweight, stateless Layer-2 bootstrapping protocol designed to automate discovery between IPv4-only and IPv6-only devices on a common broadcast domain. It operates directly over Ethernet frames without requiring IP stack initialization and is intended as a commissioning tool rather than a runtime protocol. SLDP uses a dedicated EtherType and a two-step handshake to establish MAC-to-IP mappings, facilitating integration in mixed IPv4/IPv6 environments such as industrial IoT and legacy networks. It is not a replacement for ARP, NDP, or LLDP and runs only on demand during device commissioning. The protocol includes a security blueprint (CLL Trust Oracle) to protect against address spoofing during discovery. No known exploits or vulnerabilities have been reported, and no patch or remediation is applicable as this is a newly proposed protocol.