Denial Of Service
Monthly
Privilege escalation via use-after-free in the Windows Telephony Service (TAPI) allows a locally authenticated, low-privileged attacker to gain SYSTEM-level access across a broad range of Windows desktop and server releases. The vulnerability affects Windows 10, Windows 11 (all current feature releases), and Windows Server 2012 through 2025, representing near-universal coverage of supported and legacy Microsoft platforms. No public exploit identified at time of analysis; vendor-released patches are available via Microsoft Update.
Use-after-free in Windows Winlogon enables a locally authenticated attacker to escalate privileges to SYSTEM level across a broad range of Windows desktop and server editions spanning Windows 10 through Windows 11 26H1 and Windows Server 2012 through 2025. The CVSS 7.0 score (AV:L/AC:H/PR:L) reflects that exploitation requires an existing low-privileged foothold and high attack complexity, placing this squarely in the post-compromise privilege escalation category rather than an initial access vector. No public exploit identified at time of analysis; Microsoft has released patches covering all affected build branches.
Privilege escalation in Windows Installer (msiexec) on Windows 11 and Windows Server 2025 allows a locally authenticated low-privileged user to gain SYSTEM-level privileges by exploiting a use-after-free memory corruption condition. Affected builds span Windows 11 versions 24H2, 25H2, and 26H1, as well as Windows Server 2025 including Server Core deployments. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available from Microsoft.
Privilege escalation via use-after-free in the Windows Bind Filter Driver affects Windows 11 (versions 23H2 through 26H1) and Windows Server 2025, allowing a locally authenticated attacker to gain SYSTEM-level privileges. The memory corruption flaw (CWE-416) is triggered through the kernel-mode filter driver component, yielding full confidentiality, integrity, and availability impact per CVSS. SSVC signals no confirmed exploitation and non-automatable attack path; a vendor patch is available and should be prioritized given the total technical impact rating.
Privilege escalation via use-after-free in the Windows Kernel allows a locally authenticated low-privilege attacker to gain SYSTEM-level access on Windows 11 and Windows Server 2025. The vulnerability carries a CVSS 7.0 score with high attack complexity (AC:H), indicating exploitation likely requires precise timing or heap-grooming to succeed. No public exploit identified at time of analysis, and Microsoft has released patches addressing all affected build versions.
Privilege escalation in the Windows Bind Filter Driver (bindflt.sys) permits a low-privileged local attacker to gain SYSTEM-level access on Windows 11 and Windows Server 2025 by exploiting a race condition that triggers a use-after-free in kernel memory. Affected builds span Windows 11 24H2, 25H2, and 26H1, as well as Windows Server 2025 including Server Core installations; Microsoft has released patched builds via the MSRC update guide. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Local code execution in the Windows DHCP Client exposes Windows 11 and Windows Server 2025 systems to privilege escalation by authorized local users via a use-after-free memory corruption condition. The flaw (CWE-416) requires high attack complexity - consistent with race-condition-dependent UAF exploitation - and an existing local foothold (PR:L, AV:L), limiting its practical reach compared to its full C:H/I:H/A:H impact triad. No public exploit has been identified at time of analysis, and Microsoft has released a vendor-confirmed patch.
Local privilege escalation in Windows Application Information Services (appinfo) allows an authenticated local user to gain SYSTEM-level privileges through a use-after-free memory corruption flaw (CWE-416). Affected systems span Windows 11 versions 24H2, 25H2, and 26H1, plus Windows Server 2025 and its Server Core variant - all current, widely-deployed Microsoft platforms. No public exploit identified at time of analysis, but the low attack complexity (AC:L) and full CIA impact (C:H/I:H/A:H) make this a high-priority patch for any environment where untrusted or low-privileged users have local access.
Privilege escalation in the Windows Work Folder Service allows an authenticated local attacker to gain SYSTEM-level privileges via a use-after-free memory corruption flaw rooted in a race condition (CWE-362). The vulnerability affects a wide range of Windows client and server releases from Windows Server 2012 R2 through Windows 11 26H1 and Windows Server 2025. No public exploit has been identified at time of analysis, and SSVC assessment confirms no observed exploitation; however, technical impact is rated 'total,' indicating full system compromise is achievable if exploited.
Privilege escalation in the Windows Ancillary Function Driver for WinSock (afd.sys) allows an authenticated local attacker with low privileges to elevate to SYSTEM-level access by exploiting a use-after-free memory corruption condition in the kernel-mode driver. The flaw spans a wide swath of Microsoft's supported and legacy Windows ecosystem, from Windows 10 1607 and Server 2012 through Windows 11 26H1 and Server 2025, making the patching surface unusually broad. No public exploit code or active exploitation has been confirmed at time of analysis; however, the combination of kernel-level impact, full C/I/A compromise upon success, and low privilege prerequisite makes this a meaningful post-compromise escalation risk.
Local privilege escalation in the Windows Graphics Kernel exposes a broad range of Windows 10, Windows 11, and Windows Server editions to a use-after-free memory corruption flaw (CWE-416). An attacker holding a low-privileged local account who can satisfy a race condition in the kernel graphics subsystem can gain SYSTEM-level control of the affected host. Microsoft has released patches across all identified product lines; no public exploit has been identified at time of analysis.
Null pointer dereference in the Windows TCP/IP kernel driver exposes virtually every supported Windows Server and desktop release to remote denial-of-service attacks without any authentication or user interaction. The flaw, rooted in CWE-476, causes a kernel panic (Blue Screen of Death) when a specially crafted network packet triggers a NULL pointer dereference in tcpip.sys, crashing the affected host. Nineteen distinct product/version combinations from Windows Server 2012 through Windows Server 2025 and Windows 11 25H2 are confirmed affected; no public exploit has been identified at time of analysis, and Microsoft has released corrective patches.
Privilege escalation in the Windows Virtual Hard Disk (VHD) Miniport Driver affects Windows 10, 11, and Server 2016 through 2025, enabling a low-privileged local attacker to achieve full kernel-level control via a use-after-free memory corruption in a kernel-mode driver. The CVSS AC:H rating indicates the exploit path likely requires precise timing - consistent with a race condition in driver memory management - which reduces but does not eliminate real-world risk. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch from Microsoft is available.
Unauthenticated network-based denial of service in the Windows Kernel results from unconstrained resource allocation (CWE-770), where the kernel fails to impose limits or throttling on network-triggered resource consumption. Affecting Windows 10, Windows 11, and Windows Server editions spanning 2012 through 2025, a remote attacker with no credentials or user interaction can exhaust system resources and render the host unavailable. No public exploit code or active exploitation has been identified at the time of analysis, though the low-complexity, unauthenticated attack surface warrants prompt patching across all affected enterprise environments.
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exhaust system resources and cause an application denial-of-service. Three distinct SDK components are affected: the Rust SDK (c2pa), the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), and the command-line tool (c2patool), all across their respective versions prior to the patched releases. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable without authentication or user interaction.
Null pointer dereference in Adobe's Content Credentials SDKs (Rust SDK ≤c2pa-v0.90.5, JS SDK ≤@contentauth/c2pa-web@0.12.1, CLI tool ≤c2patool-v0.27.5) enables unauthenticated remote attackers to crash any application built on these libraries by supplying a crafted C2PA media payload. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms straightforward remote exploitation with zero prerequisites or user involvement. No active exploitation has been confirmed in CISA KEV and no public exploit code has been identified at time of analysis; vendor-released patches are available for all three SDK components.
Denial of service via crafted HTTP requests to the Remote Access SSL VPN service affects Cisco Secure Firewall ASA and FTD Software across a broad range of versions, enabling unauthenticated remote attackers to force an unexpected device reload and take down the firewall entirely. The Changed scope (S:C) in the CVSS vector reflects that the impact extends beyond the VPN process itself to the entire device, disrupting all traffic passing through it. This vulnerability is confirmed actively exploited (CISA KEV), with SSVC marking it as automatable, making it a high-priority remediation target for any organization with internet-exposed ASA or FTD VPN endpoints.
Kernel-mode stack overflow in Intel PROSet/Wireless WiFi Software for Windows allows adjacent unauthenticated attackers to crash affected systems, resulting in a full system denial of service. The flaw resides in Ring 0 (kernel privilege level) WiFi driver code, meaning a successful exploit triggers a kernel panic or Blue Screen of Death rather than a user-space crash. No public exploit or CISA KEV listing has been identified at time of analysis, and no exact patched version is confirmed in the available reference data - the Intel advisory INTEL-SA-01468 should be consulted directly.
Kernel-mode denial of service in Intel PROSet/Wireless WiFi Software for Windows allows an adjacent unauthenticated attacker to crash the target system by triggering an improper buffer restriction in the Ring 0 (kernel-level) WiFi driver component. The vulnerability carries a CVSS 4.0 score of 8.3, requires no authentication or user interaction, and is confined to adjacent-network attackers. Intel has acknowledged the issue via security advisory INTEL-SA-01468; no public exploit code exists and no CISA KEV listing has been identified at time of analysis.
Denial of service in Intel PROSet/Wireless WiFi Software for Windows stems from a null pointer dereference (CWE-476) in the Ring 2 device driver layer, allowing an adjacent unauthenticated attacker to crash the affected system with no user interaction required. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VA:H) confirms low-complexity exploitation from the same network segment, resulting in high availability impact to the vulnerable system and residual low availability impact to subsequent systems. No public exploit code or CISA KEV entry has been identified at time of analysis, though the absence of authentication and interaction requirements makes this trivially triggerable by any adjacent network adversary.
Denial of service in Intel PROSet/Wireless WiFi Software for Windows stems from improper buffer restrictions (CWE-119) in the Ring 2 device driver layer, exploitable by an adjacent network attacker without authentication or user interaction. An attacker within Wi-Fi range or on the same network segment can trigger a driver-level crash by sending crafted wireless input, resulting in high availability impact on the target system and low availability impact on subsequent systems, with no confidentiality or integrity consequences. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog at time of analysis.
Null pointer dereference in Intel PROSet/Wireless WiFi Software for Windows at the Ring 2 device driver layer enables denial of service by an unauthenticated adjacent-network attacker. Disclosed by Intel in advisory INTEL-SA-01422, the flaw affects all currently indexed versions of the software and can be triggered at low complexity with no user interaction or special attack prerequisites. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Out-of-bounds read in the kernel-mode (Ring 0) component of Intel PROSet/Wireless WiFi Software for Windows enables a denial-of-service condition against affected Windows hosts. An unauthenticated attacker with adjacent network access and the ability to satisfy specific attack requirements can trigger a kernel-level crash, resulting in high availability impact to both the vulnerable system and any subsequent system processes. No public exploit code has been identified at time of analysis, and this CVE has not been listed in the CISA Known Exploited Vulnerabilities catalog.
Denial of service in Intel PROSet/Wireless WiFi Software affects the Ring 2 device driver layer, where an improper conditions check (CWE-754) can be triggered by an adjacent, unauthenticated attacker with no user interaction required. The vulnerability collapses wireless availability on the affected host and, per the CVSS 4.0 vector, cascades to subsequent system availability as well, meaning dependent network-connected services may also be disrupted. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial of service in Intel PROSet/Wireless WiFi Software device drivers (Ring 2) allows an unauthenticated adjacent-network attacker to crash or disable the wireless subsystem on affected systems. The flaw stems from an improper conditions check (CWE-754) within the WiFi driver stack, meaning edge-case or malformed network input is not handled safely, leading to complete availability loss of the vulnerable system. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the low-complexity, zero-privilege attack vector makes this straightforward to trigger from WiFi range.
Out-of-bounds write in Intel PROSet/Wireless WiFi Software for Windows device drivers (Ring 2) allows adjacent network attackers to trigger a denial of service condition without authentication or user interaction. Unauthenticated attackers on the same network segment can exploit this CWE-787 buffer overflow flaw with low complexity, causing high availability impact to the affected Windows system and low residual availability impact on subsequent systems. No public exploit code and no CISA KEV listing exist at time of analysis.
Improper access control in Intel PROSet/Wireless WiFi Software device drivers (Ring 2) allows a local unprivileged process to cause a denial of service affecting both the wireless subsystem and, to a lesser extent, downstream system integrity. Affected systems running Intel wireless drivers are exposed to any unprivileged local code - no authentication, no elevated privileges, and no user interaction are required. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in the CISA KEV catalog.
Denial-of-service in Intel PROSet/Wireless WiFi Software for Windows (Ring 2 device driver layer) allows an unauthenticated adjacent-network attacker to crash or disable the wireless driver with no user interaction. The flaw stems from an improper conditions check (CWE-754) in the driver, yielding complete loss of wireless availability on the affected system and minor downstream availability impact on subsequently connected systems. No public exploit or CISA KEV listing exists at time of analysis, and Intel has published an advisory at INTEL-SA-01422.
Intel PROSet/Wireless WiFi Software for Windows contains a null pointer dereference in Ring 0 (kernel space) that an adjacent, unauthenticated attacker can exploit to crash the target system, resulting in a denial of service. The flaw resides in the WiFi kernel driver, meaning a successful trigger causes a kernel panic (BSOD on Windows) with high availability impact on both the vulnerable component and the broader system. No public exploit code has been identified at time of analysis, and no KEV listing exists, but the adjacent-network attack vector and zero-privilege requirement make this relevant for any environment where untrusted parties share a wireless segment with Intel WiFi-equipped Windows endpoints.
Denial of service via improper input validation in Intel Active Management Technology (AMT) and Intel Standard Manageability firmware allows unauthenticated network-adjacent attackers to disrupt the out-of-band management interface. The CVSS 4.0 AT:P designation confirms that specific prerequisites - namely AMT being provisioned and network-accessible - must independently exist before exploitation is possible. No public exploit has been identified at time of analysis, and Intel has disclosed the issue under advisory INTEL-SA-01427.
Remote code execution in Zoom Clients' annotator function allows a malicious meeting participant to compromise another participant's device by exploiting a use-after-free memory corruption flaw during a live meeting session. The CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H vector confirms network-accessible cross-participant exploitation with full CIA impact and scope change, requiring no in-meeting privileges but demanding high attack complexity consistent with UAF heap manipulation. No public exploit code has been identified at time of analysis, and no CISA KEV listing was found.
Out-of-bounds read and memory exhaustion flaws in Velociraptor's NTFS parsing library allow denial of service when processing maliciously crafted NTFS images. Specifically affects deployments using the dead disk forensics workflow where Velociraptor ingests untrusted NTFS image files rather than live filesystems. An attacker who can supply a corrupted NTFS volume to a Velociraptor analyst can crash the tool, disrupting forensic investigations. No public exploit identified at time of analysis; patch available in version 0.77.2 and later.
Passkey authentication in Craft CMS before 5.10.5 is vulnerable to WebAuthn assertion replay, enabling an attacker who obtains a captured login request body to create additional authenticated sessions for a victim account without possessing the passkey device. The root cause is a dual failure at the `users/login-with-passkey` endpoint: the server accepts client-supplied `PublicKeyCredentialRequestOptions` - bypassing server-generated challenge binding - and never persists the updated credential counter after assertion validation, leaving it permanently stale. No public exploit code has been identified at time of analysis, though the GHSA advisory documents a complete step-by-step attack scenario; organizations with passkey authentication enabled in Craft CMS 5.x should treat the vendor-released patch (5.10.5) as urgent.
Prototype pollution in n8n's Edit Fields (Set) node allows any authenticated user with workflow execution permissions to corrupt a shared global in the main Node.js process, triggering an instance-wide denial of service that locks out all users until a manual process restart. Affected are all n8n releases before 1.123.67, 2.31.5, and 2.32.1 across the 1.x and 2.x branches. The attack requires only a low-privilege authenticated account and no special configuration, making this a high operational priority for any multi-user or shared n8n deployment; no public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Heap-based out-of-bounds read and write in FreeRDP before 3.30.0 can be triggered by a malicious peer during CredSSP/NLA Kerberos authentication, allowing information disclosure, heap memory corruption, or denial of service. The flaw exists in kerberos_DecryptMessage() where the peer-supplied 16-bit EC field of a GSS Wrap token is used directly in pointer arithmetic without bounds validation, enabling any RDP peer - rogue server or malicious client - to shift decrypt pointers up to 65535 bytes past the end of a ~60-byte token buffer. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Resource exhaustion in iperf3 server mode allows unauthenticated remote attackers to trigger a Denial of Service by submitting crafted control-channel JSON with oversized numeric values for the `parallel` and `len` parameters. The server performs no bounds validation on these fields, causing it to spawn excessive threads or streams and allocate disproportionately large buffers until system resources are exhausted. No public exploit code has been identified at time of analysis, and this vulnerability is not currently listed in the CISA KEV catalog.
Unauthenticated remote memory exhaustion in Undertow's WebSocket subsystem enables denial of service against any deployed application exposing a Jakarta @ServerEndpoint with an @OnMessage handler. An attacker needs only a standard WebSocket handshake - no credentials, no special tooling - to trigger unbounded Out of Memory conditions on the server. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the zero-prerequisite attack vector (CVSS AV:N/AC:L/PR:N/UI:N) makes exploitation trivially automatable against any reachable Undertow instance.
Denial of service in Red Hat JBoss Enterprise Application Platform's jboss-remoting component allows any remote unauthenticated attacker who can reach application or management ports to exhaust server memory through a crafted protocol handshake. By completing an Upgrade: jboss-remoting handshake on ports 8080, 9990, or 4447, an attacker triggers an integer overflow (CWE-190) that causes uncontrolled heap allocation, inducing OOM errors that degrade or halt request processing server-wide. No public exploit has been identified at time of analysis and the CVE is not listed in the CISA KEV catalog.
Denial of service in Red Hat EAP's Undertow HTTP/1.1 chunked-transfer decoder allows unauthenticated remote attackers to exhaust JVM heap memory by sending crafted requests with no chunk size or count limits enforced. The OutOfMemoryError triggered halts all deployments on the affected listener, not just the targeted application. CVSS metrics (AV:N/AC:L/PR:N/UI:N/A:H) confirm trivial exploitability with no authentication and no special conditions, making this a high-priority availability risk for any internet-facing EAP deployment. No public exploit or CISA KEV listing identified at time of analysis.
SAML authentication bypass in PicketLink's Service Provider signature validation allows a network-accessible attacker with low privileges to forge a SAML response and authenticate as any principal with any role on the protected application. The flaw, rooted in CWE-347 (Improper Verification of Cryptographic Signature), arises because the signature check vacuously passes when the SAML response contains zero matching assertion elements, giving the attacker full control over identity and role claims presented to the SP. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and high impact on confidentiality and integrity make this a critical authentication control failure.
Denial of service in ml-metadata (MLMD), a core metadata tracking component of Red Hat OpenShift AI (RHOAI), stems from an outdated statically-linked gRPC stack that retains known HTTP/2 resource exhaustion weaknesses. An in-cluster adversary with network reachability to the MLMD pod can crash it by sending specially crafted HTTP/2 requests, halting all ML pipeline runs within the affected namespace. No public exploit has been identified at time of analysis, and exploitation is constrained to actors already operating inside the Kubernetes cluster.
Authorization bypass in Feast's materialization API endpoints within Red Hat OpenShift AI (RHOAI) permits full re-materialization of all feature views by sending a crafted request that omits the feature_views field, circumventing permission checks. The consequence is a multi-tenant Denial of Service through data corruption and significant resource exhaustion, impacting all tenants sharing the deployment. No public exploit code has been identified at time of analysis, but the bypass mechanism is straightforward - a structural omission in the request body - making independent rediscovery likely for any attacker with API access.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
Zephyr RTOS versions 3.7.0 through 4.4.1 expose a remotely triggerable NULL pointer dereference in the UpdateHub OTA firmware-update agent that crashes and resets any affected device. The probe handler parses CoAP-delivered JSON metadata into a fixed nested-array struct but validates only the outer array length, leaving the inner sha256sum pointer NULL when the server returns an empty inner object array; a subsequent strlen() on that NULL pointer produces a fatal CPU fault. A malicious or compromised UpdateHub server - or a network man-in-the-middle when DTLS is disabled - can trigger this unconditionally. No public exploit is identified at time of analysis; a vendor patch is available in version 4.4.2.
Deadlock in the Linux kernel's drm/xe Intel Xe GPU driver allows a local low-privileged user with GPU queue access to hang or crash the kernel by triggering asynchronous GuC exec queue teardown at device removal time. Affected are kernel versions across the 6.10.14-6.12 stable series on systems with Intel Xe architecture GPUs (Arc, Lunar Lake). No public exploit has been identified and EPSS is at the 6th percentile, indicating low real-world exploitation probability; the risk is primarily an availability impact via kernel deadlock rather than code execution despite the high CVSS score.
Use-after-free in the ovpn (in-kernel OpenVPN data channel) module of the Linux kernel, present from version 6.16 onward, allows an authenticated remote VPN peer to trigger kernel memory corruption during peer cleanup. The flaw in unlock_ovpn() occurs because llist_for_each_entry() reads the next list pointer after ovpn_peer_put() may have already freed the peer structure, producing a classic UAF condition in kernel space. No public exploit code has been identified and EPSS probability is very low at 0.21% (11th percentile), though the theoretical worst-case per CVSS 3.1 is full kernel compromise (C:H/I:H/A:H).
Silent data corruption in the Linux kernel's airoha NPU mailbox driver affects EN7581-based systems (Cortex-A53 without hardware DMA cache coherency) when NPU response data is read back through a CPU cache that was never invalidated. The driver's airoha_npu_send_msg() function maps buffers exclusively as DMA_TO_DEVICE, causing dma_unmap_single() to skip cache invalidation on non-coherent architectures - so CPU reads of NPU-written responses observe stale cached values rather than actual NPU output. The CVSS 7.8 score reflects high confidentiality, integrity, and availability impact for local low-privilege users; however, hardware specificity and timing sensitivity keep real-world exploitation likelihood low (EPSS 0.20%, 10th percentile), and no public exploit or CISA KEV listing exists.
NULL pointer dereference in the Linux kernel's Intel Xe GPU SR-IOV virtual function (VF) driver allows a local user to crash the kernel during buffer object (BO) teardown. The flaw is triggered when CCS (Color Compression Surface) read/write buffers are freed after the device is unbound but while the DRM structure remains live, causing `xe_sriov_vf_ccs_rw_update_bb_addr` to dereference a NULL device pointer during process exit. CVSS rates this 7.8 (C:H/I:H/A:H) reflecting worst-case kernel-level impact, though practical exploitation is constrained by hardware and configuration prerequisites; EPSS is 0.16% (6th percentile) and no active exploitation is confirmed.
Integer truncation in the Linux kernel TIPC subsystem allows low-privileged local attackers - including unprivileged users leveraging user namespaces - to crash the kernel via division by zero or trigger link malfunction. Two independent netlink code paths (TIPC_NL_MEDIA_SET via tipc_udp_mtu_bad() and TIPC_NL_BEARER_SET via bearer.c:1160) accept MTU values above U16_MAX (65535) without enforcing an upper bound, causing silent truncation when the values are stored in u16 fields in tipc_link_create(). No exploit code is publicly known and the vulnerability is not listed in CISA KEV; EPSS at 0.17% (6th percentile) confirms very low observed exploitation probability.
Use-after-free and NULL pointer dereference vulnerabilities in the Linux kernel's amdgpu DRM driver allow a local authenticated user to corrupt kernel memory during GPU context initialization. The flaws stem from `amdgpu_ctx_init()` failing to acquire `adev->pm.stable_pstate_ctx_lock`, enabling a race between context initialization and concurrent sysfs pstate modifications, alongside a logic error where context finalization incorrectly restores pstate even when ownership has transferred to sysfs. CVSS rates this 7.8 (High), though EPSS at 0.18% (7th percentile) and absence from CISA KEV indicate no confirmed active exploitation at time of analysis.
NULL pointer dereference in the Linux kernel's drm/imagination PowerVR GPU driver allows a local attacker with low privileges to crash the kernel or potentially exploit kernel memory corruption. The vulnerability stems from pvr_vm_map() failing to acquire vm_ctx->lock before performing GPU virtual memory mapping operations, enabling a concurrent drm_gpuva_find() call to dereference a NULL pointer at kernel address offset 0x10 when map and find operations race. No public exploit code or confirmed active exploitation exists; vendor-released patches are available across multiple stable kernel branches as of Linux 6.12.101, 7.1.6, and 6.18.42.
Premature device-live marking in the Linux kernel ublk subsystem causes stranded block I/O requests and indefinite fsync hangs on ext4 filesystems. The flaw exists in ublk's user-recovery state machine: if a ublk daemon sends END_USER_RECOVERY after START_USER_RECOVERY fails (e.g., with -EBUSY) and the error is silently ignored, a stale edge-triggered completion latch from a prior recovery cycle satisfies the kernel's readiness wait prematurely, marking the device LIVE while I/O cancellation flags are still set. Any local low-privileged user able to control or interact with a ublk server process can trigger this race, causing persistent uninterruptible-sleep hangs across all fsync calls and blocking kernel teardown - confirmed by a real report of lost PREFLUSH with ext4 on ublk after daemon crash recovery. No public exploit code and no KEV listing have been identified at time of analysis.
Null pointer dereference in the Linux kernel's libceph client crashes affected hosts processing malformed CRUSH map data from a Ceph cluster. Specifically, get_immediate_parent() during localized read selection fails to validate that a parent bucket's type has a corresponding entry in type_names before dereferencing type_cn, which may be NULL when the CRUSH map contains an incomplete hierarchy. Any Linux host acting as a Ceph client - including Kubernetes nodes with Ceph-backed persistent volumes and OpenStack compute nodes - is vulnerable to a kernel panic triggerable by a party controlling or compromising the upstream Ceph cluster. No active exploitation is confirmed (not in CISA KEV) and EPSS is 0.20% (10th percentile), but the network-accessible crash path and the wide deployment of Ceph in enterprise environments make patching a practical priority.
Kernel panic via crafted zero-monitor Ceph monmap in Linux libceph allows a network-reachable attacker to crash systems running the Ceph client. The libceph subsystem's ceph_monmap_decode() function fails to reject CEPH_MSG_MON_MAP messages advertising zero monitors - a logically impossible state, since no live monitor could emit such a map - accepting the corrupted payload as valid. Subsequent session establishment in __open_session() calls pick_new_mon(), where the hardcoded assertion BUG_ON(monc->monmap->num_mon < 1) triggers an immediate kernel panic. With EPSS at 0.20% (10th percentile) and no CISA KEV listing, large-scale exploitation is not currently observed, but the unauthenticated network-reachable CVSS vector makes this relevant for any environment running Ceph-attached Linux hosts.
NULL pointer dereference in the Linux kernel's af_iucv network subsystem allows a remote attacker to crash a vulnerable kernel via a crafted SYN packet under low-memory conditions, resulting in a denial of service. The flaw resides in afiucv_hs_callback_syn(), where an unconditional call to iucv_sock_kill(nsk) is made even when nsk is NULL following a failed GFP_ATOMIC socket allocation, causing an immediate kernel panic. No public exploit is identified at time of analysis, and EPSS sits at 0.18% (7th percentile), reflecting low probability of widespread exploitation; however, the mainframe-specific HiperSockets network path reduces the realistic attacker pool significantly.
Kernel panic (denial of service) in the Linux kernel networking GRO path affects systems that forward or aggregate traffic. skb_gro_receive_list() is missing the NAPI_GRO_CB(skb)->flush validation that skb_gro_receive() already has, so flush-marked, already-aggregated frag_list packets get re-aggregated, corrupting the frag_list chain; a later skb_segment() on the TX path then dereferences a NULL/corrupted pointer and crashes the kernel. No public exploit identified at time of analysis and EPSS is low (0.18%), but a stable patch is available. Despite the NVD CVSS of 9.8, the described impact is availability-only (crash), not code execution.
Kernel crash via assertion failure in the RBD (RADOS Block Device) subsystem of the Linux kernel allows a denial-of-service condition when a crafted or corrupted OSD reply message with a positive result code is received during an object map update. Affected kernels from 5.3 onward lack the positive-result-code reset in `rbd_object_map_callback()` that already exists in `rbd_osd_req_callback()`, causing `rbd_assert(*result < 0)` in `__rbd_obj_handle_request()` to trigger and crash the kernel. No public exploit has been identified at time of analysis, and EPSS stands at 0.18% (7th percentile), indicating low observed exploitation probability.
Out-of-bounds bitmap write in the Linux kernel's Intel ICE SR-IOV driver allows a malicious Virtual Function guest to crash the host kernel or potentially escalate privileges to the host. The vulnerable function ice_parser_profile_init unconditionally passes caller-controlled ptype values from VIRTCHNL_OP_ADD_RSS_CFG into set_bit() against a statically sized 1024-bit bitmap, permitting a value such as 0xffff to write beyond the bitmap boundary and trigger a kernel NULL pointer dereference. No public exploit code has been identified and EPSS exploitation probability is low at 0.18%, but the CVSS 8.8 score and confirmed crash reproducibility signal real urgency for SR-IOV multi-tenant environments where stable-branch patches are already available.
Heap overflow in GIMP's Seattle Filmworks file loader allows an attacker who tricks a user into opening a specially crafted SFW file to write several kilobytes of attacker-controlled data beyond the intended buffer, resulting in memory corruption that can lead to arbitrary code execution or denial of service. Affected platforms confirmed via CPE data are Red Hat Enterprise Linux 6 through 9 with GIMP installed. No public exploit code has been identified and this CVE is not listed in CISA's KEV catalog, but the high CVSS 7.8 score reflects the full confidentiality, integrity, and availability impact achievable once a victim is socially engineered into opening the malicious file.
NULL pointer dereference in fastschema through v0.15.1 enables an unauthenticated remote attacker to crash the entire server process with a single HTTP request targeting the password-recovery endpoint. The flaw originates in the sendOTPEmail function in pkg/auth/local.go, which dereferences a pointer from an unchecked error path without nil validation, triggering a fatal Go panic that terminates the server. No public exploit or CISA KEV listing has been identified at time of analysis, but the trivial exploitation path (no authentication, no special configuration, single request) makes this a high-priority availability risk for any internet-exposed fastschema deployment.
Out-of-bounds read in Redis Cluster Bus PING message parsing affects Redis through version 8.8.1, enabling adjacent unauthenticated attackers to trigger denial of service or extract limited heap memory contents. The root cause is in the getPingExtLength() function, which fails to validate extension length fields against the actual remaining buffer size, allowing a crafted gossip-protocol PING packet to drive the parser past the allocated buffer boundary. No public exploit has been identified at time of analysis, and this vulnerability has not been confirmed in the CISA KEV catalog.
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the database by sending a single crafted malformed frame. Improper validation of length fields (CWE-789) causes IoTDB to attempt arbitrarily large heap allocations, exhausting JVM memory and terminating the process with an OutOfMemoryError. Versions before 1.3.8 on the 1.x branch and 2.0.0 through 2.0.8 on the 2.0.x branch are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user - including low-privilege subscribers - to read and delete arbitrary files under the WordPress installation directory. The weakness exposes sensitive configuration secrets such as database credentials stored in wp-config.php, and enables deliberate denial of service through file deletion. A publicly available exploit exists per WPScan reporting, though EPSS remains very low (0.14%, 4th percentile), suggesting targeted rather than broadly automated exploitation at time of analysis.
Integer overflow and underflow flaws in GStreamer's gst-plugins-ugly ASF demuxer expose systems to denial of service and limited heap data disclosure when processing attacker-controlled media files. The asfdemux plugin fails to adequately validate length and size fields inside ASF/WMV/WMA header objects, allowing arithmetic overflows to bypass bounds checks and trigger out-of-bounds heap reads. Any application or user that opens an untrusted media file through a GStreamer pipeline - browsers, media players, thumbnailers - is exposed; no public exploit or CISA KEV listing has been identified at time of analysis.
Heap out-of-bounds write in GStreamer's adpcmdec element allows a crafted WAV file containing malformed multi-channel IMA/DVI ADPCM audio to corrupt application memory, cause denial of service, or potentially achieve arbitrary code execution. Affected deployments include Red Hat Enterprise Linux 7 through 10, where the vulnerable gst-plugins-bad package is distributed. No confirmed active exploitation (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis, though the CVSS score of 7.6 reflects the realistic network-deliverable, user-interaction-dependent attack path.
Unauthenticated denial-of-service in WP Maps Pro WordPress plugin before 6.1.3 allows any remote attacker without credentials to exhaust server resources by triggering uncontrolled recursion through an exposed AJAX endpoint. The plugin fails to perform a capability check on at least one AJAX action accessible via the wp-ajax-nopriv_ hook and does not restrict the operation that action dispatches. No public exploit code has been identified at time of analysis and EPSS exploitation probability is very low (0.14%, 4th percentile), though successful exploitation can fully degrade availability of the affected WordPress installation.
NULL pointer dereference in Crypt::OpenSSL::PKCS12 before version 1.98 for Perl enables process crashes when any caller invokes info_as_hash() on a crafted PKCS#12 file containing a zero-length BMPSTRING bag attribute. The root cause is a zero-size Renew() call that Perl's memory allocator implements as a free() returning NULL, which is subsequently dereferenced inside strlen() within a call to newSVpvn(). With no public exploit identified at time of analysis and an EPSS of 0.19%, active exploitation is currently unlikely, though any service that parses attacker-supplied PKCS#12 data and calls info_as_hash() is directly exposed to denial of service.
Unbounded retry loops in BC-FJA's JNI native entropy layer cause calling threads to hang indefinitely when Intel RDSEED or RDRAND instructions persistently fail, producing a non-interruptible thread-level denial of service in any Java FIPS application backed by bc-fips 2.1.x before 2.1.3. The affected JNI seeding routine re-issues the CPU entropy instruction without any iteration limit whenever the carry flag signals failure - a condition reproducible by hardware entropy source faults, DRBG exhaustion under heavy multi-core contention, or hypervisors that do not forward these Intel instructions to guest VMs. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the conditions are routinely present in virtualized environments where hypervisors commonly withhold RDRAND/RDSEED forwarding, making this a realistic operational risk for enterprise Java FIPS deployments in cloud or VM-based infrastructure.
REST API connection exhaustion in Klever-Go versions 1.7.14 through 1.7.17 allows unauthenticated remote attackers to render node API services unavailable by holding slow-header connections open until server file descriptors are exhausted. The root cause is Gin's Engine.Run convenience method, which delegates to Go's default http.ListenAndServe without any ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured, leaving incoming connections open indefinitely if the client never completes request headers. A proof-of-concept documented in GHSA-w4c6-7r69-w7j9 confirmed that 120 such connections caused all 20 of 20 legitimate API probes to fail with 'accept: too many open files' on v1.7.17; no CISA KEV listing was found, and no public exploit beyond the researcher's PoC is identified at time of analysis.
Unbounded goroutine exhaustion in Klever-Go versions 1.7.14-1.7.17 allows any connected libp2p peer to remotely degrade or deny service to a Klever blockchain node by flooding it with well-formed direct messages. The root defect is architectural: `directMessageHandler` in `network/p2p/libp2p/netMessenger.go` spawns an unrestricted goroutine per incoming message before the processor-level antiflood layer can reject it, meaning admission control is structurally bypassed at ingress. No public exploit code has been identified at time of analysis, though the GHSA advisory provides a precise code walkthrough that substantially lowers exploitation complexity. The fix is available in v1.7.18.
Unauthenticated remote crash in Klever-Go versions 1.7.14-1.7.17 allows any network peer to terminate a node process by gossiping a 3-byte protobuf Transaction with the RawData sub-message omitted, triggering a nil-pointer dereference in the synchronous P2P validation callback with no panic recovery. No account, stake, validator key, or funds are required - the attacker only needs network reachability to the libp2p gossip port. Repeated delivery targeting enough BLS validators can halt block production entirely, constituting a chain-halt attack against the Klever network. No public exploit code or CISA KEV listing was identified, but the trivial payload and zero-prerequisite nature of exploitation make this a high-urgency upgrade target.
Denial-of-service via unbounded recursion in HAPI FHIR prior to 6.9.11 allows an unauthenticated remote attacker to crash parsing and validation worker threads by submitting FHIR resources containing deeply nested XHTML narratives, JSON objects, or XML elements. The commit diff reveals the flaw spans three parsers - XhtmlParser, JsonParser, and XMLUtil - each lacking a nesting depth guard, so crafted input triggers mutual recursion that exhausts the JVM thread stack and raises an unrecoverable StackOverflowError. No public exploit has been identified at time of analysis and this vulnerability does not appear in the CISA KEV catalog, but the AV:N/AC:L/PR:N/UI:N CVSS vector confirms trivial, unauthenticated exploitation against any internet-facing FHIR endpoint accepting resource submissions.
Unbounded recursive JSON parsing in HAPI FHIR's org.hl7.fhir.utilities.json.parser.JsonParser (versions prior to 6.9.11) allows unauthenticated remote attackers to crash JVM worker threads by submitting a syntactically valid but deeply nested FHIR JSON document. The mutual recursion between readObject() and readArray() carries no depth counter, so a document with as few as ~600 nesting levels exhausts the thread stack and raises a StackOverflowError before structural FHIR validation runs - any service that does not isolate StackOverflowError may lose the worker thread or destabilize the process entirely. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 7.5 (AV:N/AC:L/PR:N/UI:N) rating reflects that exploitation requires no authentication and minimal complexity against any exposed FHIR validation endpoint.
Unauthenticated denial of service in HashiCorp Consul's external gRPC listeners allows remote attackers to exhaust agent file descriptors, goroutines, and memory by flooding incomplete connections, rendering the agent unreachable to legitimate clients. Both Consul Community Edition and Consul Enterprise versions 1.13.0 through 2.0.2 are affected - a span covering nearly three years of releases. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 7.5 score and AV:N/AC:L/PR:N profile reflect a straightforwardly exploitable network condition requiring no attacker authentication or user interaction.
Unauthenticated remote denial-of-service in absinthe_federation 0.1.0-0.9.2 allows an attacker to permanently exhaust the BEAM (Erlang VM) atom table and crash the application node by sending crafted GraphQL `_entities` queries with large numbers of unique representation keys. The `convert_key/2` function in `entities_field.ex` unconditionally calls `String.to_atom/1` on all client-supplied keys, bypassing schema coercion through the open-ended `_Any` scalar; since BEAM atoms are never garbage collected and the atom table is hard-capped at approximately 1,048,576 entries, a handful of requests carrying tens of thousands of unique keys exhausts the table and aborts the node. No public exploit code or CISA KEV listing exists at time of analysis, but the attack mechanism is well-understood in the Erlang ecosystem and trivially automatable.
Persistent denial of service in Tobit Laboratories AG's TeamDavid (David/Webbox groupware) allows any remote, unauthenticated attacker to shut down the server by requesting the exposed /internalRestart endpoint, which fully halts the service rather than restarting it. All releases through Rollout 524 are affected, and recovery requires manual administrator intervention to bring the server back online. No public exploit identified at time of analysis, though the trigger is trivial (a single HTTP request to a known path).
Denial of service with potential for remote code execution affects Tobit Laboratories' TeamDavid (David Webbox) groupware through Rollout 524, where an unauthenticated attacker can crash the server by sending a specially crafted JSON body to a vulnerable API endpoint - a payload as small as 8 characters beginning with a number triggers an out-of-bounds stack write. The reliably reachable impact is a server crash, but the underlying buffer overflow could escalate to full server compromise if a stack canary is disclosed via a separate vulnerability. No public exploit identified at time of analysis and the flaw is not listed in CISA KEV; the high CVSS 4.0 base score (9.5) reflects the worst-case RCE potential rather than confirmed code execution.
Denial of service (with conditional remote code execution potential) affects Tobit Laboratories AG's TeamDavid groupware through Rollout 524, where the Webbox endpoint "//serverClient_close.html" fails to bounds-check multiple form-data parameters. An attacker submitting over-long parameter values triggers an out-of-bounds write (CWE-787) that crashes the server; if a stack canary can be leaked via a separate flaw, the memory corruption could escalate to full server compromise. No public exploit identified at time of analysis, and this CVE is one of 22 reported in the David platform by researchers at InfoGuard/NCSC.ch.
Denial of service, and potentially remote code execution, in Tobit Laboratories' David (TeamDavid/Webbox) collaboration suite affects all releases through Rollout 524. Multiple file-upload handlers fail to bounds-check the supplied filename, so an unauthenticated attacker who sends an upload request with an excessively long filename triggers an out-of-bounds stack write (CWE-787) that reliably crashes the server; where the stack layout is favorable or a stack canary can be leaked via a separate flaw, the same overflow may yield code execution and full server compromise. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw was reported by Switzerland's NCSC and detailed by InfoGuard Labs as one of 22 CVEs in David.
Denial of service in the Go implementation of Apache Fory allows unauthenticated remote attackers to crash affected services by sending crafted serialized data containing malformed type metadata, triggering an uncaught Go runtime panic. Affected versions span 0.16.0 through 1.5.0 (exclusive), while all non-Go language implementations remain unaffected. No public exploit code or active exploitation (CISA KEV) has been identified; the EPSS score of 0.18% (8th percentile) corroborates low current exploitation activity despite the high CVSS base score.
Heap type confusion in the Apache Fory C++ deserialization engine (versions 0.14.0 up to but not including 1.5.0) lets a crafted payload bypass type-compatibility checks during polymorphic smart-pointer deserialization, so an object of an incompatible type is handled as its declared base type. Because CWE-502 untrusted-data handling here corrupts memory rather than merely mis-parsing values, an attacker who controls serialized input can trigger undefined behavior ranging from denial of service to arbitrary code execution. This is rated CVSS 9.8 and is fixed in 1.5.0; there is no public exploit identified at time of analysis and EPSS is low at 0.21%.
Out-of-bounds heap read in Apache Fory C++ versions 0.14.0 through 1.4.x allows attackers supplying crafted deserialization payloads to trigger information disclosure or denial of service. The flaw resides specifically in the tagged integer fast-path deserializer and only manifests when the application processes structs with tagged integer fields. No public exploit or active exploitation has been identified at time of analysis, and a vendor-released patch is available in version 1.5.0.
Integer overflow in the llama.cpp LLaMA-Android JNI wrapper (builds b1886 through b7445) allows heap corruption through a crafted n_seq_max parameter, enabling denial of service or arbitrary code execution within Android applications that load untrusted GGUF model files. The flaw exists in the new_1batch() function, which multiplies sizeof(llama_seq_id) by an attacker-controlled value without bounds checking, causing heap allocation to wrap and undersize the buffer. No public exploit has been identified at time of analysis and this CVE is not in CISA KEV; a patched release (b7446) is confirmed available from the upstream ggml-org repository.
Denial of service in TimescaleDB through 2.29.1 allows authenticated database users holding DML privileges on a compressed hypertable to permanently crash the PostgreSQL backend on any reverse-order scan. The root cause is an unsigned integer underflow in the Gorilla compression reverse row iterator's bucket index computation when decompressing a crafted BitArray with zero elements, triggering a SIGSEGV that recurs on every subsequent reverse scan of the affected chunk until the malicious datum is removed or the database is patched. No public exploit has been identified at time of analysis and CISA KEV listing is absent, but the persistence of the malicious datum and low attack complexity make this a high-priority patch for any TimescaleDB deployment exposing DML access to untrusted users.
Catastrophic regex backtracking in pymdown-extensions 11.0 and earlier enables unauthenticated remote denial of service via crafted Markdown input under 50 bytes. The betterem, caret, tilde, and magiclink inline processors use ambiguous alternation groups that allow exponentially many partition paths for delimiter runs, causing the Python regex engine to spin without bound. Any web application rendering user-supplied Markdown with these extensions — including those using the pymdownx.extra bundle — is exposed to rendering-thread freeze with no authentication required, as confirmed by the CVSS PR:N/UI:N vector and GitHub security advisory GHSA-gm37-52c6-37mw. No public exploit or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write in the Contiki-NG MQTT client (os/net/app-layer/mqtt/mqtt.c) lets a malicious or compromised MQTT broker overflow a 65-byte topic[] buffer and corrupt the adjacent payload_chunk pointer, producing an arbitrary-pointer-write primitive that can escalate to remote code execution on embedded targets lacking memory protection. The flaw stems from parse_publish_vhdr() setting topic_len_received=1 before enforcing the 64-byte topic length limit, so an over-length topic split across TCP segments bypasses the guard on parser re-entry and reaches a memcpy() that trusts the unvalidated 16-bit topic_len. Because the stack has no TLS, the plaintext channel also exposes devices to network man-in-the-middle injection; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Integer underflow and heap out-of-bounds read in llama.cpp's DRY sampler (builds b3978 through b9058) allows remote unauthenticated attackers to crash the inference server or corrupt token sampling probabilities by sending a single crafted HTTP request. Setting the `dry_allowed_length` parameter to INT32_MIN triggers arithmetic wrap-around in the sampler, causing it to read memory before the allocated heap buffer and producing a SIGSEGV that terminates service for all connected users. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the trivially reproducible single-parameter trigger makes this a high-priority issue for any deployment exposing the llama.cpp HTTP API on a network.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, enables arbitrary code execution within the renderer sandbox in Google Chrome versions prior to 151.0.7922.109. Exploitation requires an attacker to have already achieved renderer process compromise, making this a second-stage chained payload rather than a standalone initial access vector - a prerequisite that materially constrains real-world exploit delivery. No public exploit code has been identified at time of analysis, and SSVC confirms Exploitation: none and Automatable: no, though C/I/A impacts are rated High within the sandboxed scope.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.109 stems from a use-after-free in the Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 due to a scope change, though exploitation requires user interaction (visiting a malicious page). There is no public exploit identified at time of analysis and no CISA KEV listing, but Chrome renderer/sandbox-escape bugs are historically high-value targets.
Use-after-free in Chrome's Views component prior to version 151.0.7922.109 enables a sandbox escape for remote attackers who have already compromised the renderer process, via a crafted HTML page. The CVSS scope change (S:C) confirms the potential for OS-level code execution beyond Chrome's renderer sandbox, earning a Critical severity designation from the Chromium security team despite an NVD score of 8.3. No public exploit code or CISA KEV confirmation has been identified at time of analysis, though this vulnerability class is a high-value target frequently weaponized as the second stage of browser exploit chains by sophisticated threat actors.
Privilege escalation via use-after-free in the Windows Telephony Service (TAPI) allows a locally authenticated, low-privileged attacker to gain SYSTEM-level access across a broad range of Windows desktop and server releases. The vulnerability affects Windows 10, Windows 11 (all current feature releases), and Windows Server 2012 through 2025, representing near-universal coverage of supported and legacy Microsoft platforms. No public exploit identified at time of analysis; vendor-released patches are available via Microsoft Update.
Use-after-free in Windows Winlogon enables a locally authenticated attacker to escalate privileges to SYSTEM level across a broad range of Windows desktop and server editions spanning Windows 10 through Windows 11 26H1 and Windows Server 2012 through 2025. The CVSS 7.0 score (AV:L/AC:H/PR:L) reflects that exploitation requires an existing low-privileged foothold and high attack complexity, placing this squarely in the post-compromise privilege escalation category rather than an initial access vector. No public exploit identified at time of analysis; Microsoft has released patches covering all affected build branches.
Privilege escalation in Windows Installer (msiexec) on Windows 11 and Windows Server 2025 allows a locally authenticated low-privileged user to gain SYSTEM-level privileges by exploiting a use-after-free memory corruption condition. Affected builds span Windows 11 versions 24H2, 25H2, and 26H1, as well as Windows Server 2025 including Server Core deployments. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available from Microsoft.
Privilege escalation via use-after-free in the Windows Bind Filter Driver affects Windows 11 (versions 23H2 through 26H1) and Windows Server 2025, allowing a locally authenticated attacker to gain SYSTEM-level privileges. The memory corruption flaw (CWE-416) is triggered through the kernel-mode filter driver component, yielding full confidentiality, integrity, and availability impact per CVSS. SSVC signals no confirmed exploitation and non-automatable attack path; a vendor patch is available and should be prioritized given the total technical impact rating.
Privilege escalation via use-after-free in the Windows Kernel allows a locally authenticated low-privilege attacker to gain SYSTEM-level access on Windows 11 and Windows Server 2025. The vulnerability carries a CVSS 7.0 score with high attack complexity (AC:H), indicating exploitation likely requires precise timing or heap-grooming to succeed. No public exploit identified at time of analysis, and Microsoft has released patches addressing all affected build versions.
Privilege escalation in the Windows Bind Filter Driver (bindflt.sys) permits a low-privileged local attacker to gain SYSTEM-level access on Windows 11 and Windows Server 2025 by exploiting a race condition that triggers a use-after-free in kernel memory. Affected builds span Windows 11 24H2, 25H2, and 26H1, as well as Windows Server 2025 including Server Core installations; Microsoft has released patched builds via the MSRC update guide. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Local code execution in the Windows DHCP Client exposes Windows 11 and Windows Server 2025 systems to privilege escalation by authorized local users via a use-after-free memory corruption condition. The flaw (CWE-416) requires high attack complexity - consistent with race-condition-dependent UAF exploitation - and an existing local foothold (PR:L, AV:L), limiting its practical reach compared to its full C:H/I:H/A:H impact triad. No public exploit has been identified at time of analysis, and Microsoft has released a vendor-confirmed patch.
Local privilege escalation in Windows Application Information Services (appinfo) allows an authenticated local user to gain SYSTEM-level privileges through a use-after-free memory corruption flaw (CWE-416). Affected systems span Windows 11 versions 24H2, 25H2, and 26H1, plus Windows Server 2025 and its Server Core variant - all current, widely-deployed Microsoft platforms. No public exploit identified at time of analysis, but the low attack complexity (AC:L) and full CIA impact (C:H/I:H/A:H) make this a high-priority patch for any environment where untrusted or low-privileged users have local access.
Privilege escalation in the Windows Work Folder Service allows an authenticated local attacker to gain SYSTEM-level privileges via a use-after-free memory corruption flaw rooted in a race condition (CWE-362). The vulnerability affects a wide range of Windows client and server releases from Windows Server 2012 R2 through Windows 11 26H1 and Windows Server 2025. No public exploit has been identified at time of analysis, and SSVC assessment confirms no observed exploitation; however, technical impact is rated 'total,' indicating full system compromise is achievable if exploited.
Privilege escalation in the Windows Ancillary Function Driver for WinSock (afd.sys) allows an authenticated local attacker with low privileges to elevate to SYSTEM-level access by exploiting a use-after-free memory corruption condition in the kernel-mode driver. The flaw spans a wide swath of Microsoft's supported and legacy Windows ecosystem, from Windows 10 1607 and Server 2012 through Windows 11 26H1 and Server 2025, making the patching surface unusually broad. No public exploit code or active exploitation has been confirmed at time of analysis; however, the combination of kernel-level impact, full C/I/A compromise upon success, and low privilege prerequisite makes this a meaningful post-compromise escalation risk.
Local privilege escalation in the Windows Graphics Kernel exposes a broad range of Windows 10, Windows 11, and Windows Server editions to a use-after-free memory corruption flaw (CWE-416). An attacker holding a low-privileged local account who can satisfy a race condition in the kernel graphics subsystem can gain SYSTEM-level control of the affected host. Microsoft has released patches across all identified product lines; no public exploit has been identified at time of analysis.
Null pointer dereference in the Windows TCP/IP kernel driver exposes virtually every supported Windows Server and desktop release to remote denial-of-service attacks without any authentication or user interaction. The flaw, rooted in CWE-476, causes a kernel panic (Blue Screen of Death) when a specially crafted network packet triggers a NULL pointer dereference in tcpip.sys, crashing the affected host. Nineteen distinct product/version combinations from Windows Server 2012 through Windows Server 2025 and Windows 11 25H2 are confirmed affected; no public exploit has been identified at time of analysis, and Microsoft has released corrective patches.
Privilege escalation in the Windows Virtual Hard Disk (VHD) Miniport Driver affects Windows 10, 11, and Server 2016 through 2025, enabling a low-privileged local attacker to achieve full kernel-level control via a use-after-free memory corruption in a kernel-mode driver. The CVSS AC:H rating indicates the exploit path likely requires precise timing - consistent with a race condition in driver memory management - which reduces but does not eliminate real-world risk. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch from Microsoft is available.
Unauthenticated network-based denial of service in the Windows Kernel results from unconstrained resource allocation (CWE-770), where the kernel fails to impose limits or throttling on network-triggered resource consumption. Affecting Windows 10, Windows 11, and Windows Server editions spanning 2012 through 2025, a remote attacker with no credentials or user interaction can exhaust system resources and render the host unavailable. No public exploit code or active exploitation has been identified at the time of analysis, though the low-complexity, unauthenticated attack surface warrants prompt patching across all affected enterprise environments.
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exhaust system resources and cause an application denial-of-service. Three distinct SDK components are affected: the Rust SDK (c2pa), the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), and the command-line tool (c2patool), all across their respective versions prior to the patched releases. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable without authentication or user interaction.
Null pointer dereference in Adobe's Content Credentials SDKs (Rust SDK ≤c2pa-v0.90.5, JS SDK ≤@contentauth/c2pa-web@0.12.1, CLI tool ≤c2patool-v0.27.5) enables unauthenticated remote attackers to crash any application built on these libraries by supplying a crafted C2PA media payload. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms straightforward remote exploitation with zero prerequisites or user involvement. No active exploitation has been confirmed in CISA KEV and no public exploit code has been identified at time of analysis; vendor-released patches are available for all three SDK components.
Denial of service via crafted HTTP requests to the Remote Access SSL VPN service affects Cisco Secure Firewall ASA and FTD Software across a broad range of versions, enabling unauthenticated remote attackers to force an unexpected device reload and take down the firewall entirely. The Changed scope (S:C) in the CVSS vector reflects that the impact extends beyond the VPN process itself to the entire device, disrupting all traffic passing through it. This vulnerability is confirmed actively exploited (CISA KEV), with SSVC marking it as automatable, making it a high-priority remediation target for any organization with internet-exposed ASA or FTD VPN endpoints.
Kernel-mode stack overflow in Intel PROSet/Wireless WiFi Software for Windows allows adjacent unauthenticated attackers to crash affected systems, resulting in a full system denial of service. The flaw resides in Ring 0 (kernel privilege level) WiFi driver code, meaning a successful exploit triggers a kernel panic or Blue Screen of Death rather than a user-space crash. No public exploit or CISA KEV listing has been identified at time of analysis, and no exact patched version is confirmed in the available reference data - the Intel advisory INTEL-SA-01468 should be consulted directly.
Kernel-mode denial of service in Intel PROSet/Wireless WiFi Software for Windows allows an adjacent unauthenticated attacker to crash the target system by triggering an improper buffer restriction in the Ring 0 (kernel-level) WiFi driver component. The vulnerability carries a CVSS 4.0 score of 8.3, requires no authentication or user interaction, and is confined to adjacent-network attackers. Intel has acknowledged the issue via security advisory INTEL-SA-01468; no public exploit code exists and no CISA KEV listing has been identified at time of analysis.
Denial of service in Intel PROSet/Wireless WiFi Software for Windows stems from a null pointer dereference (CWE-476) in the Ring 2 device driver layer, allowing an adjacent unauthenticated attacker to crash the affected system with no user interaction required. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VA:H) confirms low-complexity exploitation from the same network segment, resulting in high availability impact to the vulnerable system and residual low availability impact to subsequent systems. No public exploit code or CISA KEV entry has been identified at time of analysis, though the absence of authentication and interaction requirements makes this trivially triggerable by any adjacent network adversary.
Denial of service in Intel PROSet/Wireless WiFi Software for Windows stems from improper buffer restrictions (CWE-119) in the Ring 2 device driver layer, exploitable by an adjacent network attacker without authentication or user interaction. An attacker within Wi-Fi range or on the same network segment can trigger a driver-level crash by sending crafted wireless input, resulting in high availability impact on the target system and low availability impact on subsequent systems, with no confidentiality or integrity consequences. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog at time of analysis.
Null pointer dereference in Intel PROSet/Wireless WiFi Software for Windows at the Ring 2 device driver layer enables denial of service by an unauthenticated adjacent-network attacker. Disclosed by Intel in advisory INTEL-SA-01422, the flaw affects all currently indexed versions of the software and can be triggered at low complexity with no user interaction or special attack prerequisites. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Out-of-bounds read in the kernel-mode (Ring 0) component of Intel PROSet/Wireless WiFi Software for Windows enables a denial-of-service condition against affected Windows hosts. An unauthenticated attacker with adjacent network access and the ability to satisfy specific attack requirements can trigger a kernel-level crash, resulting in high availability impact to both the vulnerable system and any subsequent system processes. No public exploit code has been identified at time of analysis, and this CVE has not been listed in the CISA Known Exploited Vulnerabilities catalog.
Denial of service in Intel PROSet/Wireless WiFi Software affects the Ring 2 device driver layer, where an improper conditions check (CWE-754) can be triggered by an adjacent, unauthenticated attacker with no user interaction required. The vulnerability collapses wireless availability on the affected host and, per the CVSS 4.0 vector, cascades to subsequent system availability as well, meaning dependent network-connected services may also be disrupted. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial of service in Intel PROSet/Wireless WiFi Software device drivers (Ring 2) allows an unauthenticated adjacent-network attacker to crash or disable the wireless subsystem on affected systems. The flaw stems from an improper conditions check (CWE-754) within the WiFi driver stack, meaning edge-case or malformed network input is not handled safely, leading to complete availability loss of the vulnerable system. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the low-complexity, zero-privilege attack vector makes this straightforward to trigger from WiFi range.
Out-of-bounds write in Intel PROSet/Wireless WiFi Software for Windows device drivers (Ring 2) allows adjacent network attackers to trigger a denial of service condition without authentication or user interaction. Unauthenticated attackers on the same network segment can exploit this CWE-787 buffer overflow flaw with low complexity, causing high availability impact to the affected Windows system and low residual availability impact on subsequent systems. No public exploit code and no CISA KEV listing exist at time of analysis.
Improper access control in Intel PROSet/Wireless WiFi Software device drivers (Ring 2) allows a local unprivileged process to cause a denial of service affecting both the wireless subsystem and, to a lesser extent, downstream system integrity. Affected systems running Intel wireless drivers are exposed to any unprivileged local code - no authentication, no elevated privileges, and no user interaction are required. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in the CISA KEV catalog.
Denial-of-service in Intel PROSet/Wireless WiFi Software for Windows (Ring 2 device driver layer) allows an unauthenticated adjacent-network attacker to crash or disable the wireless driver with no user interaction. The flaw stems from an improper conditions check (CWE-754) in the driver, yielding complete loss of wireless availability on the affected system and minor downstream availability impact on subsequently connected systems. No public exploit or CISA KEV listing exists at time of analysis, and Intel has published an advisory at INTEL-SA-01422.
Intel PROSet/Wireless WiFi Software for Windows contains a null pointer dereference in Ring 0 (kernel space) that an adjacent, unauthenticated attacker can exploit to crash the target system, resulting in a denial of service. The flaw resides in the WiFi kernel driver, meaning a successful trigger causes a kernel panic (BSOD on Windows) with high availability impact on both the vulnerable component and the broader system. No public exploit code has been identified at time of analysis, and no KEV listing exists, but the adjacent-network attack vector and zero-privilege requirement make this relevant for any environment where untrusted parties share a wireless segment with Intel WiFi-equipped Windows endpoints.
Denial of service via improper input validation in Intel Active Management Technology (AMT) and Intel Standard Manageability firmware allows unauthenticated network-adjacent attackers to disrupt the out-of-band management interface. The CVSS 4.0 AT:P designation confirms that specific prerequisites - namely AMT being provisioned and network-accessible - must independently exist before exploitation is possible. No public exploit has been identified at time of analysis, and Intel has disclosed the issue under advisory INTEL-SA-01427.
Remote code execution in Zoom Clients' annotator function allows a malicious meeting participant to compromise another participant's device by exploiting a use-after-free memory corruption flaw during a live meeting session. The CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H vector confirms network-accessible cross-participant exploitation with full CIA impact and scope change, requiring no in-meeting privileges but demanding high attack complexity consistent with UAF heap manipulation. No public exploit code has been identified at time of analysis, and no CISA KEV listing was found.
Out-of-bounds read and memory exhaustion flaws in Velociraptor's NTFS parsing library allow denial of service when processing maliciously crafted NTFS images. Specifically affects deployments using the dead disk forensics workflow where Velociraptor ingests untrusted NTFS image files rather than live filesystems. An attacker who can supply a corrupted NTFS volume to a Velociraptor analyst can crash the tool, disrupting forensic investigations. No public exploit identified at time of analysis; patch available in version 0.77.2 and later.
Passkey authentication in Craft CMS before 5.10.5 is vulnerable to WebAuthn assertion replay, enabling an attacker who obtains a captured login request body to create additional authenticated sessions for a victim account without possessing the passkey device. The root cause is a dual failure at the `users/login-with-passkey` endpoint: the server accepts client-supplied `PublicKeyCredentialRequestOptions` - bypassing server-generated challenge binding - and never persists the updated credential counter after assertion validation, leaving it permanently stale. No public exploit code has been identified at time of analysis, though the GHSA advisory documents a complete step-by-step attack scenario; organizations with passkey authentication enabled in Craft CMS 5.x should treat the vendor-released patch (5.10.5) as urgent.
Prototype pollution in n8n's Edit Fields (Set) node allows any authenticated user with workflow execution permissions to corrupt a shared global in the main Node.js process, triggering an instance-wide denial of service that locks out all users until a manual process restart. Affected are all n8n releases before 1.123.67, 2.31.5, and 2.32.1 across the 1.x and 2.x branches. The attack requires only a low-privilege authenticated account and no special configuration, making this a high operational priority for any multi-user or shared n8n deployment; no public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Heap-based out-of-bounds read and write in FreeRDP before 3.30.0 can be triggered by a malicious peer during CredSSP/NLA Kerberos authentication, allowing information disclosure, heap memory corruption, or denial of service. The flaw exists in kerberos_DecryptMessage() where the peer-supplied 16-bit EC field of a GSS Wrap token is used directly in pointer arithmetic without bounds validation, enabling any RDP peer - rogue server or malicious client - to shift decrypt pointers up to 65535 bytes past the end of a ~60-byte token buffer. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Resource exhaustion in iperf3 server mode allows unauthenticated remote attackers to trigger a Denial of Service by submitting crafted control-channel JSON with oversized numeric values for the `parallel` and `len` parameters. The server performs no bounds validation on these fields, causing it to spawn excessive threads or streams and allocate disproportionately large buffers until system resources are exhausted. No public exploit code has been identified at time of analysis, and this vulnerability is not currently listed in the CISA KEV catalog.
Unauthenticated remote memory exhaustion in Undertow's WebSocket subsystem enables denial of service against any deployed application exposing a Jakarta @ServerEndpoint with an @OnMessage handler. An attacker needs only a standard WebSocket handshake - no credentials, no special tooling - to trigger unbounded Out of Memory conditions on the server. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the zero-prerequisite attack vector (CVSS AV:N/AC:L/PR:N/UI:N) makes exploitation trivially automatable against any reachable Undertow instance.
Denial of service in Red Hat JBoss Enterprise Application Platform's jboss-remoting component allows any remote unauthenticated attacker who can reach application or management ports to exhaust server memory through a crafted protocol handshake. By completing an Upgrade: jboss-remoting handshake on ports 8080, 9990, or 4447, an attacker triggers an integer overflow (CWE-190) that causes uncontrolled heap allocation, inducing OOM errors that degrade or halt request processing server-wide. No public exploit has been identified at time of analysis and the CVE is not listed in the CISA KEV catalog.
Denial of service in Red Hat EAP's Undertow HTTP/1.1 chunked-transfer decoder allows unauthenticated remote attackers to exhaust JVM heap memory by sending crafted requests with no chunk size or count limits enforced. The OutOfMemoryError triggered halts all deployments on the affected listener, not just the targeted application. CVSS metrics (AV:N/AC:L/PR:N/UI:N/A:H) confirm trivial exploitability with no authentication and no special conditions, making this a high-priority availability risk for any internet-facing EAP deployment. No public exploit or CISA KEV listing identified at time of analysis.
SAML authentication bypass in PicketLink's Service Provider signature validation allows a network-accessible attacker with low privileges to forge a SAML response and authenticate as any principal with any role on the protected application. The flaw, rooted in CWE-347 (Improper Verification of Cryptographic Signature), arises because the signature check vacuously passes when the SAML response contains zero matching assertion elements, giving the attacker full control over identity and role claims presented to the SP. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and high impact on confidentiality and integrity make this a critical authentication control failure.
Denial of service in ml-metadata (MLMD), a core metadata tracking component of Red Hat OpenShift AI (RHOAI), stems from an outdated statically-linked gRPC stack that retains known HTTP/2 resource exhaustion weaknesses. An in-cluster adversary with network reachability to the MLMD pod can crash it by sending specially crafted HTTP/2 requests, halting all ML pipeline runs within the affected namespace. No public exploit has been identified at time of analysis, and exploitation is constrained to actors already operating inside the Kubernetes cluster.
Authorization bypass in Feast's materialization API endpoints within Red Hat OpenShift AI (RHOAI) permits full re-materialization of all feature views by sending a crafted request that omits the feature_views field, circumventing permission checks. The consequence is a multi-tenant Denial of Service through data corruption and significant resource exhaustion, impacting all tenants sharing the deployment. No public exploit code has been identified at time of analysis, but the bypass mechanism is straightforward - a structural omission in the request body - making independent rediscovery likely for any attacker with API access.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
Zephyr RTOS versions 3.7.0 through 4.4.1 expose a remotely triggerable NULL pointer dereference in the UpdateHub OTA firmware-update agent that crashes and resets any affected device. The probe handler parses CoAP-delivered JSON metadata into a fixed nested-array struct but validates only the outer array length, leaving the inner sha256sum pointer NULL when the server returns an empty inner object array; a subsequent strlen() on that NULL pointer produces a fatal CPU fault. A malicious or compromised UpdateHub server - or a network man-in-the-middle when DTLS is disabled - can trigger this unconditionally. No public exploit is identified at time of analysis; a vendor patch is available in version 4.4.2.
Deadlock in the Linux kernel's drm/xe Intel Xe GPU driver allows a local low-privileged user with GPU queue access to hang or crash the kernel by triggering asynchronous GuC exec queue teardown at device removal time. Affected are kernel versions across the 6.10.14-6.12 stable series on systems with Intel Xe architecture GPUs (Arc, Lunar Lake). No public exploit has been identified and EPSS is at the 6th percentile, indicating low real-world exploitation probability; the risk is primarily an availability impact via kernel deadlock rather than code execution despite the high CVSS score.
Use-after-free in the ovpn (in-kernel OpenVPN data channel) module of the Linux kernel, present from version 6.16 onward, allows an authenticated remote VPN peer to trigger kernel memory corruption during peer cleanup. The flaw in unlock_ovpn() occurs because llist_for_each_entry() reads the next list pointer after ovpn_peer_put() may have already freed the peer structure, producing a classic UAF condition in kernel space. No public exploit code has been identified and EPSS probability is very low at 0.21% (11th percentile), though the theoretical worst-case per CVSS 3.1 is full kernel compromise (C:H/I:H/A:H).
Silent data corruption in the Linux kernel's airoha NPU mailbox driver affects EN7581-based systems (Cortex-A53 without hardware DMA cache coherency) when NPU response data is read back through a CPU cache that was never invalidated. The driver's airoha_npu_send_msg() function maps buffers exclusively as DMA_TO_DEVICE, causing dma_unmap_single() to skip cache invalidation on non-coherent architectures - so CPU reads of NPU-written responses observe stale cached values rather than actual NPU output. The CVSS 7.8 score reflects high confidentiality, integrity, and availability impact for local low-privilege users; however, hardware specificity and timing sensitivity keep real-world exploitation likelihood low (EPSS 0.20%, 10th percentile), and no public exploit or CISA KEV listing exists.
NULL pointer dereference in the Linux kernel's Intel Xe GPU SR-IOV virtual function (VF) driver allows a local user to crash the kernel during buffer object (BO) teardown. The flaw is triggered when CCS (Color Compression Surface) read/write buffers are freed after the device is unbound but while the DRM structure remains live, causing `xe_sriov_vf_ccs_rw_update_bb_addr` to dereference a NULL device pointer during process exit. CVSS rates this 7.8 (C:H/I:H/A:H) reflecting worst-case kernel-level impact, though practical exploitation is constrained by hardware and configuration prerequisites; EPSS is 0.16% (6th percentile) and no active exploitation is confirmed.
Integer truncation in the Linux kernel TIPC subsystem allows low-privileged local attackers - including unprivileged users leveraging user namespaces - to crash the kernel via division by zero or trigger link malfunction. Two independent netlink code paths (TIPC_NL_MEDIA_SET via tipc_udp_mtu_bad() and TIPC_NL_BEARER_SET via bearer.c:1160) accept MTU values above U16_MAX (65535) without enforcing an upper bound, causing silent truncation when the values are stored in u16 fields in tipc_link_create(). No exploit code is publicly known and the vulnerability is not listed in CISA KEV; EPSS at 0.17% (6th percentile) confirms very low observed exploitation probability.
Use-after-free and NULL pointer dereference vulnerabilities in the Linux kernel's amdgpu DRM driver allow a local authenticated user to corrupt kernel memory during GPU context initialization. The flaws stem from `amdgpu_ctx_init()` failing to acquire `adev->pm.stable_pstate_ctx_lock`, enabling a race between context initialization and concurrent sysfs pstate modifications, alongside a logic error where context finalization incorrectly restores pstate even when ownership has transferred to sysfs. CVSS rates this 7.8 (High), though EPSS at 0.18% (7th percentile) and absence from CISA KEV indicate no confirmed active exploitation at time of analysis.
NULL pointer dereference in the Linux kernel's drm/imagination PowerVR GPU driver allows a local attacker with low privileges to crash the kernel or potentially exploit kernel memory corruption. The vulnerability stems from pvr_vm_map() failing to acquire vm_ctx->lock before performing GPU virtual memory mapping operations, enabling a concurrent drm_gpuva_find() call to dereference a NULL pointer at kernel address offset 0x10 when map and find operations race. No public exploit code or confirmed active exploitation exists; vendor-released patches are available across multiple stable kernel branches as of Linux 6.12.101, 7.1.6, and 6.18.42.
Premature device-live marking in the Linux kernel ublk subsystem causes stranded block I/O requests and indefinite fsync hangs on ext4 filesystems. The flaw exists in ublk's user-recovery state machine: if a ublk daemon sends END_USER_RECOVERY after START_USER_RECOVERY fails (e.g., with -EBUSY) and the error is silently ignored, a stale edge-triggered completion latch from a prior recovery cycle satisfies the kernel's readiness wait prematurely, marking the device LIVE while I/O cancellation flags are still set. Any local low-privileged user able to control or interact with a ublk server process can trigger this race, causing persistent uninterruptible-sleep hangs across all fsync calls and blocking kernel teardown - confirmed by a real report of lost PREFLUSH with ext4 on ublk after daemon crash recovery. No public exploit code and no KEV listing have been identified at time of analysis.
Null pointer dereference in the Linux kernel's libceph client crashes affected hosts processing malformed CRUSH map data from a Ceph cluster. Specifically, get_immediate_parent() during localized read selection fails to validate that a parent bucket's type has a corresponding entry in type_names before dereferencing type_cn, which may be NULL when the CRUSH map contains an incomplete hierarchy. Any Linux host acting as a Ceph client - including Kubernetes nodes with Ceph-backed persistent volumes and OpenStack compute nodes - is vulnerable to a kernel panic triggerable by a party controlling or compromising the upstream Ceph cluster. No active exploitation is confirmed (not in CISA KEV) and EPSS is 0.20% (10th percentile), but the network-accessible crash path and the wide deployment of Ceph in enterprise environments make patching a practical priority.
Kernel panic via crafted zero-monitor Ceph monmap in Linux libceph allows a network-reachable attacker to crash systems running the Ceph client. The libceph subsystem's ceph_monmap_decode() function fails to reject CEPH_MSG_MON_MAP messages advertising zero monitors - a logically impossible state, since no live monitor could emit such a map - accepting the corrupted payload as valid. Subsequent session establishment in __open_session() calls pick_new_mon(), where the hardcoded assertion BUG_ON(monc->monmap->num_mon < 1) triggers an immediate kernel panic. With EPSS at 0.20% (10th percentile) and no CISA KEV listing, large-scale exploitation is not currently observed, but the unauthenticated network-reachable CVSS vector makes this relevant for any environment running Ceph-attached Linux hosts.
NULL pointer dereference in the Linux kernel's af_iucv network subsystem allows a remote attacker to crash a vulnerable kernel via a crafted SYN packet under low-memory conditions, resulting in a denial of service. The flaw resides in afiucv_hs_callback_syn(), where an unconditional call to iucv_sock_kill(nsk) is made even when nsk is NULL following a failed GFP_ATOMIC socket allocation, causing an immediate kernel panic. No public exploit is identified at time of analysis, and EPSS sits at 0.18% (7th percentile), reflecting low probability of widespread exploitation; however, the mainframe-specific HiperSockets network path reduces the realistic attacker pool significantly.
Kernel panic (denial of service) in the Linux kernel networking GRO path affects systems that forward or aggregate traffic. skb_gro_receive_list() is missing the NAPI_GRO_CB(skb)->flush validation that skb_gro_receive() already has, so flush-marked, already-aggregated frag_list packets get re-aggregated, corrupting the frag_list chain; a later skb_segment() on the TX path then dereferences a NULL/corrupted pointer and crashes the kernel. No public exploit identified at time of analysis and EPSS is low (0.18%), but a stable patch is available. Despite the NVD CVSS of 9.8, the described impact is availability-only (crash), not code execution.
Kernel crash via assertion failure in the RBD (RADOS Block Device) subsystem of the Linux kernel allows a denial-of-service condition when a crafted or corrupted OSD reply message with a positive result code is received during an object map update. Affected kernels from 5.3 onward lack the positive-result-code reset in `rbd_object_map_callback()` that already exists in `rbd_osd_req_callback()`, causing `rbd_assert(*result < 0)` in `__rbd_obj_handle_request()` to trigger and crash the kernel. No public exploit has been identified at time of analysis, and EPSS stands at 0.18% (7th percentile), indicating low observed exploitation probability.
Out-of-bounds bitmap write in the Linux kernel's Intel ICE SR-IOV driver allows a malicious Virtual Function guest to crash the host kernel or potentially escalate privileges to the host. The vulnerable function ice_parser_profile_init unconditionally passes caller-controlled ptype values from VIRTCHNL_OP_ADD_RSS_CFG into set_bit() against a statically sized 1024-bit bitmap, permitting a value such as 0xffff to write beyond the bitmap boundary and trigger a kernel NULL pointer dereference. No public exploit code has been identified and EPSS exploitation probability is low at 0.18%, but the CVSS 8.8 score and confirmed crash reproducibility signal real urgency for SR-IOV multi-tenant environments where stable-branch patches are already available.
Heap overflow in GIMP's Seattle Filmworks file loader allows an attacker who tricks a user into opening a specially crafted SFW file to write several kilobytes of attacker-controlled data beyond the intended buffer, resulting in memory corruption that can lead to arbitrary code execution or denial of service. Affected platforms confirmed via CPE data are Red Hat Enterprise Linux 6 through 9 with GIMP installed. No public exploit code has been identified and this CVE is not listed in CISA's KEV catalog, but the high CVSS 7.8 score reflects the full confidentiality, integrity, and availability impact achievable once a victim is socially engineered into opening the malicious file.
NULL pointer dereference in fastschema through v0.15.1 enables an unauthenticated remote attacker to crash the entire server process with a single HTTP request targeting the password-recovery endpoint. The flaw originates in the sendOTPEmail function in pkg/auth/local.go, which dereferences a pointer from an unchecked error path without nil validation, triggering a fatal Go panic that terminates the server. No public exploit or CISA KEV listing has been identified at time of analysis, but the trivial exploitation path (no authentication, no special configuration, single request) makes this a high-priority availability risk for any internet-exposed fastschema deployment.
Out-of-bounds read in Redis Cluster Bus PING message parsing affects Redis through version 8.8.1, enabling adjacent unauthenticated attackers to trigger denial of service or extract limited heap memory contents. The root cause is in the getPingExtLength() function, which fails to validate extension length fields against the actual remaining buffer size, allowing a crafted gossip-protocol PING packet to drive the parser past the allocated buffer boundary. No public exploit has been identified at time of analysis, and this vulnerability has not been confirmed in the CISA KEV catalog.
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the database by sending a single crafted malformed frame. Improper validation of length fields (CWE-789) causes IoTDB to attempt arbitrarily large heap allocations, exhausting JVM memory and terminating the process with an OutOfMemoryError. Versions before 1.3.8 on the 1.x branch and 2.0.0 through 2.0.8 on the 2.0.x branch are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user - including low-privilege subscribers - to read and delete arbitrary files under the WordPress installation directory. The weakness exposes sensitive configuration secrets such as database credentials stored in wp-config.php, and enables deliberate denial of service through file deletion. A publicly available exploit exists per WPScan reporting, though EPSS remains very low (0.14%, 4th percentile), suggesting targeted rather than broadly automated exploitation at time of analysis.
Integer overflow and underflow flaws in GStreamer's gst-plugins-ugly ASF demuxer expose systems to denial of service and limited heap data disclosure when processing attacker-controlled media files. The asfdemux plugin fails to adequately validate length and size fields inside ASF/WMV/WMA header objects, allowing arithmetic overflows to bypass bounds checks and trigger out-of-bounds heap reads. Any application or user that opens an untrusted media file through a GStreamer pipeline - browsers, media players, thumbnailers - is exposed; no public exploit or CISA KEV listing has been identified at time of analysis.
Heap out-of-bounds write in GStreamer's adpcmdec element allows a crafted WAV file containing malformed multi-channel IMA/DVI ADPCM audio to corrupt application memory, cause denial of service, or potentially achieve arbitrary code execution. Affected deployments include Red Hat Enterprise Linux 7 through 10, where the vulnerable gst-plugins-bad package is distributed. No confirmed active exploitation (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis, though the CVSS score of 7.6 reflects the realistic network-deliverable, user-interaction-dependent attack path.
Unauthenticated denial-of-service in WP Maps Pro WordPress plugin before 6.1.3 allows any remote attacker without credentials to exhaust server resources by triggering uncontrolled recursion through an exposed AJAX endpoint. The plugin fails to perform a capability check on at least one AJAX action accessible via the wp-ajax-nopriv_ hook and does not restrict the operation that action dispatches. No public exploit code has been identified at time of analysis and EPSS exploitation probability is very low (0.14%, 4th percentile), though successful exploitation can fully degrade availability of the affected WordPress installation.
NULL pointer dereference in Crypt::OpenSSL::PKCS12 before version 1.98 for Perl enables process crashes when any caller invokes info_as_hash() on a crafted PKCS#12 file containing a zero-length BMPSTRING bag attribute. The root cause is a zero-size Renew() call that Perl's memory allocator implements as a free() returning NULL, which is subsequently dereferenced inside strlen() within a call to newSVpvn(). With no public exploit identified at time of analysis and an EPSS of 0.19%, active exploitation is currently unlikely, though any service that parses attacker-supplied PKCS#12 data and calls info_as_hash() is directly exposed to denial of service.
Unbounded retry loops in BC-FJA's JNI native entropy layer cause calling threads to hang indefinitely when Intel RDSEED or RDRAND instructions persistently fail, producing a non-interruptible thread-level denial of service in any Java FIPS application backed by bc-fips 2.1.x before 2.1.3. The affected JNI seeding routine re-issues the CPU entropy instruction without any iteration limit whenever the carry flag signals failure - a condition reproducible by hardware entropy source faults, DRBG exhaustion under heavy multi-core contention, or hypervisors that do not forward these Intel instructions to guest VMs. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the conditions are routinely present in virtualized environments where hypervisors commonly withhold RDRAND/RDSEED forwarding, making this a realistic operational risk for enterprise Java FIPS deployments in cloud or VM-based infrastructure.
REST API connection exhaustion in Klever-Go versions 1.7.14 through 1.7.17 allows unauthenticated remote attackers to render node API services unavailable by holding slow-header connections open until server file descriptors are exhausted. The root cause is Gin's Engine.Run convenience method, which delegates to Go's default http.ListenAndServe without any ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured, leaving incoming connections open indefinitely if the client never completes request headers. A proof-of-concept documented in GHSA-w4c6-7r69-w7j9 confirmed that 120 such connections caused all 20 of 20 legitimate API probes to fail with 'accept: too many open files' on v1.7.17; no CISA KEV listing was found, and no public exploit beyond the researcher's PoC is identified at time of analysis.
Unbounded goroutine exhaustion in Klever-Go versions 1.7.14-1.7.17 allows any connected libp2p peer to remotely degrade or deny service to a Klever blockchain node by flooding it with well-formed direct messages. The root defect is architectural: `directMessageHandler` in `network/p2p/libp2p/netMessenger.go` spawns an unrestricted goroutine per incoming message before the processor-level antiflood layer can reject it, meaning admission control is structurally bypassed at ingress. No public exploit code has been identified at time of analysis, though the GHSA advisory provides a precise code walkthrough that substantially lowers exploitation complexity. The fix is available in v1.7.18.
Unauthenticated remote crash in Klever-Go versions 1.7.14-1.7.17 allows any network peer to terminate a node process by gossiping a 3-byte protobuf Transaction with the RawData sub-message omitted, triggering a nil-pointer dereference in the synchronous P2P validation callback with no panic recovery. No account, stake, validator key, or funds are required - the attacker only needs network reachability to the libp2p gossip port. Repeated delivery targeting enough BLS validators can halt block production entirely, constituting a chain-halt attack against the Klever network. No public exploit code or CISA KEV listing was identified, but the trivial payload and zero-prerequisite nature of exploitation make this a high-urgency upgrade target.
Denial-of-service via unbounded recursion in HAPI FHIR prior to 6.9.11 allows an unauthenticated remote attacker to crash parsing and validation worker threads by submitting FHIR resources containing deeply nested XHTML narratives, JSON objects, or XML elements. The commit diff reveals the flaw spans three parsers - XhtmlParser, JsonParser, and XMLUtil - each lacking a nesting depth guard, so crafted input triggers mutual recursion that exhausts the JVM thread stack and raises an unrecoverable StackOverflowError. No public exploit has been identified at time of analysis and this vulnerability does not appear in the CISA KEV catalog, but the AV:N/AC:L/PR:N/UI:N CVSS vector confirms trivial, unauthenticated exploitation against any internet-facing FHIR endpoint accepting resource submissions.
Unbounded recursive JSON parsing in HAPI FHIR's org.hl7.fhir.utilities.json.parser.JsonParser (versions prior to 6.9.11) allows unauthenticated remote attackers to crash JVM worker threads by submitting a syntactically valid but deeply nested FHIR JSON document. The mutual recursion between readObject() and readArray() carries no depth counter, so a document with as few as ~600 nesting levels exhausts the thread stack and raises a StackOverflowError before structural FHIR validation runs - any service that does not isolate StackOverflowError may lose the worker thread or destabilize the process entirely. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 7.5 (AV:N/AC:L/PR:N/UI:N) rating reflects that exploitation requires no authentication and minimal complexity against any exposed FHIR validation endpoint.
Unauthenticated denial of service in HashiCorp Consul's external gRPC listeners allows remote attackers to exhaust agent file descriptors, goroutines, and memory by flooding incomplete connections, rendering the agent unreachable to legitimate clients. Both Consul Community Edition and Consul Enterprise versions 1.13.0 through 2.0.2 are affected - a span covering nearly three years of releases. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 7.5 score and AV:N/AC:L/PR:N profile reflect a straightforwardly exploitable network condition requiring no attacker authentication or user interaction.
Unauthenticated remote denial-of-service in absinthe_federation 0.1.0-0.9.2 allows an attacker to permanently exhaust the BEAM (Erlang VM) atom table and crash the application node by sending crafted GraphQL `_entities` queries with large numbers of unique representation keys. The `convert_key/2` function in `entities_field.ex` unconditionally calls `String.to_atom/1` on all client-supplied keys, bypassing schema coercion through the open-ended `_Any` scalar; since BEAM atoms are never garbage collected and the atom table is hard-capped at approximately 1,048,576 entries, a handful of requests carrying tens of thousands of unique keys exhausts the table and aborts the node. No public exploit code or CISA KEV listing exists at time of analysis, but the attack mechanism is well-understood in the Erlang ecosystem and trivially automatable.
Persistent denial of service in Tobit Laboratories AG's TeamDavid (David/Webbox groupware) allows any remote, unauthenticated attacker to shut down the server by requesting the exposed /internalRestart endpoint, which fully halts the service rather than restarting it. All releases through Rollout 524 are affected, and recovery requires manual administrator intervention to bring the server back online. No public exploit identified at time of analysis, though the trigger is trivial (a single HTTP request to a known path).
Denial of service with potential for remote code execution affects Tobit Laboratories' TeamDavid (David Webbox) groupware through Rollout 524, where an unauthenticated attacker can crash the server by sending a specially crafted JSON body to a vulnerable API endpoint - a payload as small as 8 characters beginning with a number triggers an out-of-bounds stack write. The reliably reachable impact is a server crash, but the underlying buffer overflow could escalate to full server compromise if a stack canary is disclosed via a separate vulnerability. No public exploit identified at time of analysis and the flaw is not listed in CISA KEV; the high CVSS 4.0 base score (9.5) reflects the worst-case RCE potential rather than confirmed code execution.
Denial of service (with conditional remote code execution potential) affects Tobit Laboratories AG's TeamDavid groupware through Rollout 524, where the Webbox endpoint "//serverClient_close.html" fails to bounds-check multiple form-data parameters. An attacker submitting over-long parameter values triggers an out-of-bounds write (CWE-787) that crashes the server; if a stack canary can be leaked via a separate flaw, the memory corruption could escalate to full server compromise. No public exploit identified at time of analysis, and this CVE is one of 22 reported in the David platform by researchers at InfoGuard/NCSC.ch.
Denial of service, and potentially remote code execution, in Tobit Laboratories' David (TeamDavid/Webbox) collaboration suite affects all releases through Rollout 524. Multiple file-upload handlers fail to bounds-check the supplied filename, so an unauthenticated attacker who sends an upload request with an excessively long filename triggers an out-of-bounds stack write (CWE-787) that reliably crashes the server; where the stack layout is favorable or a stack canary can be leaked via a separate flaw, the same overflow may yield code execution and full server compromise. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw was reported by Switzerland's NCSC and detailed by InfoGuard Labs as one of 22 CVEs in David.
Denial of service in the Go implementation of Apache Fory allows unauthenticated remote attackers to crash affected services by sending crafted serialized data containing malformed type metadata, triggering an uncaught Go runtime panic. Affected versions span 0.16.0 through 1.5.0 (exclusive), while all non-Go language implementations remain unaffected. No public exploit code or active exploitation (CISA KEV) has been identified; the EPSS score of 0.18% (8th percentile) corroborates low current exploitation activity despite the high CVSS base score.
Heap type confusion in the Apache Fory C++ deserialization engine (versions 0.14.0 up to but not including 1.5.0) lets a crafted payload bypass type-compatibility checks during polymorphic smart-pointer deserialization, so an object of an incompatible type is handled as its declared base type. Because CWE-502 untrusted-data handling here corrupts memory rather than merely mis-parsing values, an attacker who controls serialized input can trigger undefined behavior ranging from denial of service to arbitrary code execution. This is rated CVSS 9.8 and is fixed in 1.5.0; there is no public exploit identified at time of analysis and EPSS is low at 0.21%.
Out-of-bounds heap read in Apache Fory C++ versions 0.14.0 through 1.4.x allows attackers supplying crafted deserialization payloads to trigger information disclosure or denial of service. The flaw resides specifically in the tagged integer fast-path deserializer and only manifests when the application processes structs with tagged integer fields. No public exploit or active exploitation has been identified at time of analysis, and a vendor-released patch is available in version 1.5.0.
Integer overflow in the llama.cpp LLaMA-Android JNI wrapper (builds b1886 through b7445) allows heap corruption through a crafted n_seq_max parameter, enabling denial of service or arbitrary code execution within Android applications that load untrusted GGUF model files. The flaw exists in the new_1batch() function, which multiplies sizeof(llama_seq_id) by an attacker-controlled value without bounds checking, causing heap allocation to wrap and undersize the buffer. No public exploit has been identified at time of analysis and this CVE is not in CISA KEV; a patched release (b7446) is confirmed available from the upstream ggml-org repository.
Denial of service in TimescaleDB through 2.29.1 allows authenticated database users holding DML privileges on a compressed hypertable to permanently crash the PostgreSQL backend on any reverse-order scan. The root cause is an unsigned integer underflow in the Gorilla compression reverse row iterator's bucket index computation when decompressing a crafted BitArray with zero elements, triggering a SIGSEGV that recurs on every subsequent reverse scan of the affected chunk until the malicious datum is removed or the database is patched. No public exploit has been identified at time of analysis and CISA KEV listing is absent, but the persistence of the malicious datum and low attack complexity make this a high-priority patch for any TimescaleDB deployment exposing DML access to untrusted users.
Catastrophic regex backtracking in pymdown-extensions 11.0 and earlier enables unauthenticated remote denial of service via crafted Markdown input under 50 bytes. The betterem, caret, tilde, and magiclink inline processors use ambiguous alternation groups that allow exponentially many partition paths for delimiter runs, causing the Python regex engine to spin without bound. Any web application rendering user-supplied Markdown with these extensions — including those using the pymdownx.extra bundle — is exposed to rendering-thread freeze with no authentication required, as confirmed by the CVSS PR:N/UI:N vector and GitHub security advisory GHSA-gm37-52c6-37mw. No public exploit or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write in the Contiki-NG MQTT client (os/net/app-layer/mqtt/mqtt.c) lets a malicious or compromised MQTT broker overflow a 65-byte topic[] buffer and corrupt the adjacent payload_chunk pointer, producing an arbitrary-pointer-write primitive that can escalate to remote code execution on embedded targets lacking memory protection. The flaw stems from parse_publish_vhdr() setting topic_len_received=1 before enforcing the 64-byte topic length limit, so an over-length topic split across TCP segments bypasses the guard on parser re-entry and reaches a memcpy() that trusts the unvalidated 16-bit topic_len. Because the stack has no TLS, the plaintext channel also exposes devices to network man-in-the-middle injection; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Integer underflow and heap out-of-bounds read in llama.cpp's DRY sampler (builds b3978 through b9058) allows remote unauthenticated attackers to crash the inference server or corrupt token sampling probabilities by sending a single crafted HTTP request. Setting the `dry_allowed_length` parameter to INT32_MIN triggers arithmetic wrap-around in the sampler, causing it to read memory before the allocated heap buffer and producing a SIGSEGV that terminates service for all connected users. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the trivially reproducible single-parameter trigger makes this a high-priority issue for any deployment exposing the llama.cpp HTTP API on a network.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, enables arbitrary code execution within the renderer sandbox in Google Chrome versions prior to 151.0.7922.109. Exploitation requires an attacker to have already achieved renderer process compromise, making this a second-stage chained payload rather than a standalone initial access vector - a prerequisite that materially constrains real-world exploit delivery. No public exploit code has been identified at time of analysis, and SSVC confirms Exploitation: none and Automatable: no, though C/I/A impacts are rated High within the sandboxed scope.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.109 stems from a use-after-free in the Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 due to a scope change, though exploitation requires user interaction (visiting a malicious page). There is no public exploit identified at time of analysis and no CISA KEV listing, but Chrome renderer/sandbox-escape bugs are historically high-value targets.
Use-after-free in Chrome's Views component prior to version 151.0.7922.109 enables a sandbox escape for remote attackers who have already compromised the renderer process, via a crafted HTML page. The CVSS scope change (S:C) confirms the potential for OS-level code execution beyond Chrome's renderer sandbox, earning a Critical severity designation from the Chromium security team despite an NVD score of 8.3. No public exploit code or CISA KEV confirmation has been identified at time of analysis, though this vulnerability class is a high-value target frequently weaponized as the second stage of browser exploit chains by sophisticated threat actors.