A high-volume phishing campaign was observed on November 13, 2026, targeting organizations globally across multiple sectors. The attackers impersonated Microsoft 365 service-health notifications, falsely claiming that emails were held due to a service disruption and would be deleted unless recipients acted within 24 hours. The campaign used specific malicious sender domains and recipient-specific tracking links. Although assessed as credential phishing, no direct credential capture, malware delivery, or post-compromise activity was observed. Microsoft Defender and Defender for Office 365 provide blocking and quarantine protections against this campaign.
Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily. Other DDL attack routes exist, such as "ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN". The system had inadequate tracking of typed values, and values were not self-identifying. Stale values could appear in data dictionary entries, PL/pgSQL variables, and many other parts of the system. PostgreSQL Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
CopperDragon is a malware framework linked to China-nexus threat actors targeting high-profile organizations globally, including in Latin America, Asia, and Europe. It supports multiple intrusion campaigns grouped into three clusters—SilentDelivery, OceanGate, and DarkWire—each using distinct backdoors and sophisticated techniques such as kernel rootkits, trojanized SSH tools, and credential harvesting across Linux and Windows systems. The campaigns focus on government, critical infrastructure, and telecommunications sectors.
CVE-2026-114235 is a forced browsing vulnerability in Apache OFBiz 24.09 versions prior to 24.09.08. It allows an authenticated user with view-only access to the Order Manager component to modify shipment tracking numbers by directly accessing the updateTrackingNumber endpoint. This issue is fixed in version 24.09.08.
CVE-2026-69050 is a critical out-of-bounds write vulnerability in the Samsung Semiconductor Exynos 1480 device driver caused by improper resource state tracking. This flaw allows an attacker to write outside the intended memory bounds, potentially leading to complete system compromise. The vulnerability has a CVSS score of 9.8, indicating high impact on confidentiality, integrity, and availability. A fix was released in November 2026.
Seven months after initial disclosure, the Coruna iOS exploit framework continues to evolve, now deploying two distinct chains based on device operating system version. Targets running iOS 17.2.1 or earlier receive the legacy Coruna framework, while later builds receive DarkSword-derived chains. Analysis identified 608 domains delivering Coruna-family code, with 93 sites mapping to 21 distinct tracking collectors. Distribution spans dating portals, AI-companion platforms, cryptocurrency promotions, media streaming services, and compromised legitimate sites. The attack requires no user interaction beyond loading a webpage, operating through hidden iframes that deploy browser exploits leading to native code execution. Recovered modules include kernel memory manipulation, code-signing enforcement changes, process memory access, encrypted command-and-control communication, and cleanup routines. One delivery vector involves compromised npm packages, enabling legitimate websites to serve exploits through their o...
A vulnerability in the Linux kernel's ksmbd component involves uninitialized FileSystemControlFlags in the FS_CONTROL_INFORMATION structure. This can cause information leakage in compound SMB2 requests due to leftover data in the response buffer. The issue arises because the buffer is zeroed on allocation but not fully cleared on certain error responses, allowing stale data to be sent to clients. ksmbd does not implement quota tracking and reports no control flags, which is related to the flaw.
CVE-2026-99082 is a vulnerability in the Linux kernel's KVM x86 virtualization component related to the handling of per-vCPU MMIO cache and memslot generations. The flaw involves improper use of memslots when the vCPU runs in System Management Mode (SMM), which can lead to stale cache entries and incorrect memory accesses. This can cause KVM to bypass write-tracking for certain memory pages, potentially allowing continued use of outdated shadow translations. The issue has been fixed by ensuring the active memslots are used for caching and validation, distinguishing between normal and SMM address spaces.
CVE-2026-98850 is a vulnerability in the Linux kernel's net/packet subsystem where the TX_RING byte count can overflow during packet transmission. This occurs because the signed integer tracking the total byte count can wrap into the negative range after many successful transmissions, causing a kernel BUG and potentially a system panic on configured systems. The flaw affects certain Linux kernel versions and is triggered by concurrent userspace recycling of completed frames. The issue has been fixed by preventing the byte count from exceeding INT_MAX, avoiding the overflow and subsequent kernel panic.
Since April 2026, the PoeLLM malware campaign has targeted exposed AI/LLM and open-source services such as LiteLLM, Ollama, Gotenberg, and Gitea. It uses a novel command-and-control method where infected systems extract C2 server addresses from keywords embedded in a poem on GitHub. The malware deploys cryptocurrency miners (XMRig and Iron) connecting victims to Kryptex mining infrastructure. Compromised hosts are also used as scanners and exploit servers to grow the botnet, which has affected over 3,400 servers with up to 800 active daily. The campaign is linked to an Italian-speaking threat actor and mainly impacts victims in the United States and Western Europe. Vulnerable routers are exploited to serve as C2 infrastructure.
Apache YuniKorn 1.9.0 and earlier allows bypassing the check for the user annotation by setting a secondary label on the pod. If the pod has the label 'app=yunikorn' the checks limiting the user annotation content are not run. The label is used to identify the YuniKorn application itself in the deployments.
The bypass allows any user to specify an arbitrary user info annotation. The arbitrary user information could allow access to a queue that the user normally would not have access to. Quota usage for the queue might be impacted if the application runs in the incorrect queue. User based quota enforcement is also based on the user annotation. User quota tracking could be side stepped even if the application runs in the correct queue.
Users are recommended to upgrade to version 1.10.0, which fixes this issue.
CVE-2026-73570 is an unauthenticated OS command injection vulnerability in the SNMP notification path of Zimbra Collaboration Suite mail servers. It was actively exploited between July and August 2026. Attackers used this flaw to deploy JSP webshells and reverse shells without authentication, escalate privileges via PAM configuration abuse, and maintain persistence through systemd services. Post-exploitation activities included lateral movement across clusters using Zimbra SSH keys, theft of authentication secrets and mailbox data, and attempts to exfiltrate data using cloud storage tools. Multiple organizations across various regions and industries were targeted through automated and manual attacks on internet-facing Zimbra mail servers.
A vulnerability in the Linux kernel's network bridge code involving CFM and MRP frame handlers has been resolved. The issue arises because CFM and MRP register a global frame type node that is linked into multiple bridge lists, causing list corruption when unregistered on one bridge. This affects uncommon protocol handlers that can only be installed once per bridge. The fix involves tracking per-bridge enable state with option bits and removing the shared list structure, improving both correctness and performance.
A vulnerability in the Linux kernel's x86/amd_node component related to PCI device reference counting in the amd_smn_init() function has been resolved. The issue involved improper handling of reference counts for temporary pointers during PCI device searches, which could lead to incorrect reference counting. The fix ensures proper incrementing and decrementing of reference counts to maintain accurate device usage tracking.
The s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 260814 via the 'first_name' parameter parameter. This is due to insufficient sanitization of the first_name parameter via esc_refs(), which strips only regex backreferences and not PHP tags, before substitution into the eval'd Signup Tracking Codes template, combined with disclosure of the site-global proxy verification key that allows PayPal postback verification to be bypassed. This makes it possible for unauthenticated attackers to execute code on the server. Successful exploitation requires that the site administrator has configured a Signup Tracking Codes template containing the %%first_name%% placeholder (a documented, GUI-supported feature) and that the attacker has obtained the site-global proxy verification key, which is exposed in plaintext in the JSON response of any PayPal Checkout AJAX request on the target site.
In the Linux kernel, the following vulnerability has been resolved: arm64: entry: Avoid unnecessary local_irq_disable() on kernel exit Currently, when exiting to kernel mode, we attempt involuntary preemption. The preemption logic expects IRQs to be disabled, which is why we call local_irq_disable() before attempting preemption. However, depending on the context, local_irq_disable() may be unnecessary: - __el1_irq(), the non-NMI EL1 IRQ path, already has IRQs disabled, so local_irq_disable() is redundant. - irqentry_exit_to_kernel_mode_preempt() immediately returns when exiting from an NMI-like context, so calling local_irq_disable() beforehand is unnecessary work. Furthermore, it confuses the pNMI state tracking when we are in a context with interrupts disabled and the GIC_PRIO_PSR_I_SET bit is set in the PMR, leading to a warning when CONFIG_ARM64_DEBUG_PRIORITY_MASKING=y: WARNING: ./arch/arm64/include/asm/irqflags.h:63 at arm64_exit_to_kernel_mode+0xb8/0xc0, CPU#40: retsnoop/31805 CPU: 40 UID: 0 PID: 31805 Comm: retsnoop Not tainted 7.2.0-rc6-next-20260805 #7 PREEMPTLAZY pstate: 234013c9 (nzCv DAIF +PAN -UAO +TCO +DIT +SSBS BTYPE=--) pc : arm64_exit_to_kernel_mode (arch/arm64/kernel/entry-common.c:63) lr : el1_abort (arch/arm64/kernel/entry-common.c:323) pmr: 000000f0 Call trace: arm64_exit_to_kernel_mode (arch/arm64/kernel/entry-common.c:63) (P) el1_abort (arch/arm64/kernel/entry-common.c:323) el1h_64_sync_handler (arch/arm64/kernel/entry-common.c:449) el1h_64_sync (arch/arm64/kernel/entry.S:589) [...] Split arm64_exit_to_kernel_mode() into preempt, non-preempt, and dispatch parts so that we can avoid this extra work where it is not needed and avoid breaking the pNMI tracking logic.