A malicious file identified by the SHA-256 hash 5bb52bd682510c1fdc91025512a92c0e2323c885664e65ad32f0fbb426940469 was observed by OffSeq Mirage honeypot sensors on 2026-10-26. The file was detected four times during attacker activity involving the T1105 technique (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The malicious activity was traced to attacker infrastructure located in PS. Organizations are advised to match this hash against their environments and security feeds to detect potential compromise.
A malicious file identified by the SHA-256 hash a863e21577e54cd763729803a621804da4b5030afa35bcf879ea3b3413488a66 was observed by OffSeq Mirage honeypot sensors during attacker activity on 2026-10-26. This file is associated with CVE-2026-109618 and linked to the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The file likely represents a malicious payload such as a dropper, web shell, miner, or post-exploitation tool used during the attack. The activity was traced back to attacker infrastructure in PS. Organizations are advised to match this hash against files in their environments and threat intelligence feeds.
The PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) are critical flaws in the PHP engine allowing unauthenticated remote code execution. Multiple industrial vendors including Siemens, Schneider Electric, ABB, and others have confirmed that some of their products are affected. Patches for PHP were released on October 21, 2026, shortly after exploitation attempts began. Several vendors have released or are preparing patches for affected products, while some continue to assess impact or provide mitigations. The vulnerabilities have been actively targeted in the wild, with millions of exploitation attempts reported and confirmed attacks on honeypots.
CVE-2026-99099 addresses a vulnerability in the Linux kernel related to AMD processors where the processor may fail to invalidate a TLB entry when executing an INVLPGB/TLBSYNC instruction pair. This issue is known as AMD TLBI Erratum #1718. The Linux kernel has implemented a software workaround to detect this erratum and mitigate it when a microcode fix is not available.
A buffer overflow vulnerability in the Linux kernel's dm-integrity inline mode with large tag sizes has been fixed. The issue occurs because the checksum computation uses an on-stack buffer smaller than the tag size, causing an overflow when the tag size exceeds the buffer size. This overflow can cause kernel panics with stack protection enabled. The vulnerability requires root privileges to trigger and is not considered a security bug. Fixes have been applied in recent kernel commits.
A vulnerability in the Linux kernel's tee subsystem allows zero-sized allocations in tee_dyn_shm_alloc_helper(), leading to a kernel allocation failure and potential boot panic on systems with panic_on_warn enabled. This occurs because the function does not check for zero size before calling alloc_pages_exact(), which results in an invalid page order. The issue is triggered via TEE_IOC_SHM_ALLOC with a zero size parameter and has been fixed in specific commits.
A vulnerability in the Linux kernel's io_uring subsystem allowed disabled rings to bypass task restrictions on register operations until enabled. This could let a task with restricted register opcodes create a disabled ring, perform any register opcode on it, and then enable the ring without proper permission. The issue has been fixed by ensuring that rings inheriting restrictions from tasks are checked even while disabled, requiring explicit permission to enable them.
A vulnerability in the Linux kernel's drm/vc4 driver was fixed by properly draining the hangcheck timer and related work on V3D unbind. The flaw allowed timer callbacks to access freed memory due to the timer not being stopped before the device was unbound and freed.
A vulnerability in the Linux kernel Bluetooth driver btintel_pcie was fixed to correct a bounds check error in the TX descriptor handling. The function btintel_pcie_prepare_tx used an index that could exceed the valid range of the transmit queue arrays, potentially leading to out-of-bounds access. This issue was addressed by rejecting an index equal to the transmit queue count, which is one past the end of the arrays.
A Linux kernel vulnerability was fixed that prevented scheduling deferred kernel page table freeing during system boot. The issue caused kernel panics when using a boot-time function tracer with a filter, due to workqueue usage before initialization. The fix delays scheduling the freeing work until the system is fully booted.
CVE-2026-99092 is a vulnerability in the Linux kernel affecting the riscv architecture's handling of bpf-jit execmem addresses. The issue arises from incorrect assumptions about memory writability in the vmalloc area when CONFIG_STRICT_MODULE_RWX is disabled, causing BPF JIT compilation to fail. This bug affects kernel version 6.10 and similar configurations where strict module RWX enforcement is not enabled. The flaw has been fixed in specific commits addressing the patch_map() function to correctly handle executable memory mappings for BPF JIT code.
A vulnerability in the Linux kernel Bluetooth management (MGMT) subsystem caused pending commands flushed on power off to report an incorrect status. Specifically, commands pending when the Bluetooth adapter powers off were incorrectly answered with a success status (0x00) instead of the appropriate error status (e.g., Not Powered or Invalid Index). This could cause user-space components like bluetoothd to crash due to unexpected responses. The issue has been fixed in Linux kernel versions 6.6.160, 6.2, 6.11, 6.12, and related releases.
CVE-2026-99090 is a vulnerability in the Linux kernel's AMDGPU driver where vblank counter reads are not properly serialized against GPU resets. This can cause unsafe hardware access during GPU recovery, triggering kernel warnings and tainting the kernel. The issue is fixed by acquiring a semaphore before hardware access or returning a cached software count if reset is in progress.
A vulnerability in the Linux kernel's ASoC Samsung i2s driver causes an imbalance in runtime power management due to the op_clk clock not being enabled during device probe. This leads to a warning during boot related to clock disablement. The issue is fixed by enabling op_clk in the probe function and disabling it in the remove function.
A vulnerability in the Linux kernel's Open vSwitch component related to IPv6 address rewrite actions on IPv6 fragments has been fixed. The issue occurs because the transport header is not properly validated before being accessed, leading to uninitialized memory reads that trigger warnings under debug configurations. The fix involves early return in the checksum update function to avoid reading uninitialized transport header offsets for IPv6 fragments.
CVE-2026-90885 is an XML External Entity (XXE) vulnerability in the Apache Camel Saxon component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.2. The vulnerability arises because the default Saxon Configuration used by XQueryBuilder accepts DOCTYPE declarations and resolves external entities when the message body is already a javax.xml.transform.Source, allowing external entity expansion. This can lead to unauthorized file reads and network requests initiated by the vulnerable process. The issue is fixed in Apache Camel versions 4.18.5 and 4.22.2.
CVE-2026-77062 is a vulnerability in the boneIO Black web interface where the lack of clickjacking protections allows remote attackers to embed the control panel in an iframe and trick authenticated users on the internal network into performing unauthorized actions. These actions include activating relays, opening gates, or controlling blinds, which may have physical safety implications. The issue is exacerbated by CVE-2026-77053, which disables authentication by default, allowing any internal network user to trigger these actions via a malicious website. This vulnerability was fixed in boneIO version 1.6.0.
CVE-2026-94386 is a vulnerability in Apache Camel's OAuth component affecting versions from 4.19.0 up to but not including 4.22.2. The issue arises from a static token cache keyed only by token endpoint and client ID, causing tokens to be shared across profiles with different scopes or client secrets. This can lead to outbound requests carrying tokens with broader or unintended scopes, potentially granting excessive access to services. The vulnerability is fixed in version 4.22.2 and later.
CVE-2026-77061 is a vulnerability in boneIO versions 1.2.0 up to but not including 1.6.0 where several API endpoints are excluded from authentication. This allows an unauthenticated attacker on the local network to access sensitive information such as system logs, firmware version, serial number, MQTT username, configuration file listings, and API documentation. The issue was fixed in version 1.6.0 by requiring authentication for all API routes, disabling interactive API documentation, and withholding the serial number from anonymous users.
boneIO black_debian_images versions from 1.2.0 up to but not including 1.6.0 improperly set world-readable permissions on the Mosquitto MQTT broker password file located at /etc/mosquitto/passwd. This allows any local user to read password hashes for all MQTT accounts, enabling offline dictionary attacks. The issue is fixed in version 1.6.0.