Information Disclosure
Monthly
Kernel-state confusion in the Linux MPTCP subsystem allows a remote peer to leave stale Multipath TCP Fast Open (MPTFO) state on a passively-opened socket by sending a valid-cookie TCP Fast Open SYN that carries no payload. Because mptcp_fastopen_subflow_synack_set_params() set the is_mptfo flag before verifying that data was actually queued, a data-less TFO SYN triggers a WARN and, if non-fatal, leaves the subflow in an inconsistent state that can later be tripped inside check_fully_established(). The upstream fix marks the subflow as MPTFO only after an SKB is confirmed queued and returns quietly on an empty receive queue. No public exploit identified at time of analysis; the input carries the inflated CVSS 9.4 typical of automated kernel-CVE scoring rather than a demonstrated high-impact primitive.
Heap buffer overflow in the Linux kernel's s390/qeth driver exposes IBM System z hosts to local kernel memory corruption via malformed SNMP and ARP query ioctl calls. Affected systems run Linux kernel versions from 2.6.26 through the last unfixed stable releases across eight stable branches, with patches available in 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2. An attacker supplying a zero or undersized udata_len value to qeth_snmp_command() or qeth_l3_arp_query() triggers a u32 integer underflow in the callback bounds check, allowing memcpy to write past the kernel heap allocation and potentially achieve kernel code execution. No public exploit code and no CISA KEV listing have been identified at time of analysis.
PMD huge page mapping boundary violation in the Linux kernel's drm/shmem_helper subsystem allows local users with low privileges to trigger out-of-bounds memory mappings via the DRM ->huge_fault handler. The handler installs PMD-level Transparent Huge Page mappings without verifying they remain within Virtual Memory Area boundaries, triggering a VM_BUG_ON_VMA() assertion when the mapping subsequently reaches copy_pmd_range() during fork or remap operations. Patches have been committed to Linux 7.1.10 and 7.2 stable branches; no public exploit has been identified at time of analysis.
Out-of-bounds kernel memory write in the Linux framebuffer device (fbdev) subsystem exposes systems to potential privilege escalation by local low-privileged users. The flaw resides in show_modes(), which accumulates unchecked snprintf() return values while building sysfs output, allowing the write offset to advance beyond the PAGE_SIZE sysfs buffer when a display device has a sufficiently long modelist. No public exploit has been identified at time of analysis; patched kernel versions 7.1.10 and 7.2 are available via the stable kernel tree.
Use-after-free in the Linux kernel's fbdev framebuffer subsystem allows a local low-privileged user to trigger a stale pointer dereference with potential for information disclosure, memory corruption, or privilege escalation. When userspace issues FBIOPUT_VSCREENINFO with FB_ACTIVATE_INV_MODE via the fb_set_var() path, a videomode entry may be deleted from the modelist while fb_info->mode still holds a dangling pointer to the freed entry; a subsequent sysfs read via show_mode() then dereferences freed kernel memory. No public exploit has been identified at time of analysis, and this vulnerability is not listed in CISA KEV.
Missing bounds validation in the amdgpu DRM driver's GFX ring command submission path allows a local low-privileged user to submit oversized Indirect Buffer (IB) requests that corrupt adjacent control bits in GPU ring packet fields, destabilizing command submission and potentially achieving kernel memory corruption with scope-changing impact. Affected systems must have AMD GPU hardware and the amdgpu kernel module loaded; the vulnerability is present across multiple stable branches prior to Linux 6.12.105, 7.1.10, 6.18.46, and 7.2. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor-released patches are available for all affected stable branches.
Out-of-bounds memory access in the Linux kernel's cs40l50-vibra haptic driver allows a local low-privileged user to read or write beyond allocated kernel buffers by submitting a crafted force-feedback effect via EVIOCSFF ioctl. The driver's cs40l50_add() function fails to validate user-supplied custom_len before dereferencing custom_data[0] and custom_data[1], and an integer sign-wrap in bank type handling permits negative array indexing into vib->dsp.banks[]. Three distinct code paths are exploitable: zero-length allocation returning ZERO_SIZE_PTR, single-word allocation followed by a two-word read, and s16 overflow enabling out-of-bounds bank array access. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
Use-after-free race condition in the Linux kernel BYD PS/2 mouse driver allows a local low-privileged user to corrupt kernel memory by racing a device disconnect event against in-flight timer callbacks. Affected systems must run an unpatched Linux kernel with BYD PS/2 touchpad hardware present and the byd module loaded, spanning stable branches from approximately kernel 4.6 through pre-fix releases ahead of 6.18.46, 7.1.10, and 7.2. No public exploit code has been identified at time of analysis, and this vulnerability is not currently listed in the CISA KEV catalog.
Out-of-bounds memory write in the Linux kernel's synaptics-rmi4 input driver allows a local attacker with access to a malicious or malfunctioning RMI4 touchpad device to corrupt kernel memory, potentially enabling privilege escalation or information disclosure. The root cause is a mismatch between the F54 report buffer allocation size (derived from F54 electrode counts) and the transfer size computed from F55 electrode counts - both sourced directly from device queries with no cross-validation. Vendor patches are confirmed across multiple stable kernel branches; no public exploit or CISA KEV listing has been identified at time of analysis.
Incorrect error-path logic in the Linux kernel's Qualcomm Crypto Engine (QCE) driver allows a local attacker with low privileges on Qualcomm SoC-based hardware to potentially trigger memory corruption via a use-after-free or improper resource release condition. The flaw resides in `devm_qce_register_algs`, where a failed `ops->register_algs()` call causes the cleanup loop to repeatedly invoke `ops->unregister_algs()` on the failed slot rather than iterating over previously successfully registered algorithm slots - leaving registered algorithms unreleased and potentially double-freeing or corrupting state. No public exploit identified at time of analysis, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.
Out-of-bounds kernel memory read in the Linux kernel's libceph client (decode_watchers()) lets a malicious or compromised Ceph OSD trigger a 4-byte read past a validated buffer when it returns an obj_list_watch_response_t reply with struct_len=0. Any kernel client issuing CEPH_OSD_OP_LIST_WATCHERS is affected; the leaked garbage value is then used as a watcher count for allocation, risking information disclosure or unstable allocation behavior. Tagged as Information Disclosure with no public exploit identified at time of analysis and no CISA KEV listing, despite an NVD CVSS of 9.8.
Use-after-free race condition in the Linux kernel atmel-mci MMC/SD controller driver allows a local privileged user to corrupt freed kernel memory by racing module removal against queued bottom-half work items. Systems running Linux on Atmel AT91 or AVR32 SoC hardware with the atmel-mci driver loaded are exclusively affected; x86/x64 deployments are unaffected by design. Patch commits are confirmed available for stable branches 6.12.x, 6.18.x, 7.1.x, and 7.2, with no public exploit identified at time of analysis.
Memory leak in the Linux kernel s390/vfio_ccw subsystem enables a guest VM user to exhaust host kernel memory by submitting crafted channel programs that trigger cp_init() failure paths, leaving ccwchain segments unfreed. Affected deployments are IBM s390 (mainframe) KVM hosts that have vfio channel command word (CCW) device passthrough configured, making the attack surface highly specific. No public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog; CVSS 7.1 with S:C reflects the guest-to-host cross-boundary availability impact.
Uncontrolled recursion in the Linux kernel's s390 vfio-ccw driver lets a local actor on IBM Z (s390) hosts submit a channel program containing an unbounded number of chained CCW/Transfer-in-Channel (TIC) segments, which are processed recursively and can exhaust the kernel stack. Affected are s390 systems using vfio-ccw device passthrough to KVM guests; the impact is host instability and potential kernel memory corruption. No public exploit is identified at time of analysis, it is not in CISA KEV, and no EPSS score was provided.
Use-after-free in the Linux kernel's s390/vfio_ccw subsystem allows a local low-privileged user on IBM Z hardware to corrupt freed kernel memory by triggering workqueue dispatch after the owning private struct has been released. Affected systems are those running KVM guests with VFIO CCW I/O channel passthrough on s390 architecture, spanning kernel versions from 4.12 through multiple unpatched stable branches. No public exploit or CISA KEV entry exists at time of analysis, but the scope-changing CVSS vector reflects the potential to compromise the host kernel or co-resident VMs.
Out-of-bounds region index access in the Linux kernel's s390/vfio_ccw subsystem exposes systems to potential guest-to-host privilege escalation on IBM mainframe KVM deployments. The read/write region handlers lack the bounds clamping that was applied to the capability chain regions, allowing a low-privileged local attacker - typically a KVM guest with vfio_ccw passthrough access - to trigger out-of-bounds memory access with a CVSS Scope:Changed impact. Vendor-released patches are available across multiple stable kernel branches, and no public exploit has been identified at time of analysis.
Host-side memory corruption/information disclosure in the Linux kernel s390 vfio_ccw driver allows a malicious or compromised KVM guest on IBM Z mainframes to exploit a double-fetch race when the driver reads a guest-supplied IDAL (Indirect Data Address List). Because the first IDAW is read separately to size the transfer buffer, a guest that changes that address between reads can desynchronize the buffer size from the actual IDAW set, corrupting or leaking host memory (S:C, C:H/I:H/A:H, CVSS 9.3). No public exploit identified at time of analysis and the issue is not in CISA KEV; the fix (verifying the first IDAW is unchanged between reads) is available upstream via stable kernel commits.
Out-of-bounds read in the Linux kernel's s390/vfio_ccw subsystem exposes host kernel memory to guest VM users, caused by an off-by-one error in the CCW chain length validation loop within `ccwchain_calc_length()`. Affected versions span from Linux 4.12 across multiple stable branches, with vendor-released patches confirmed in 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV; however, the guest-to-host scope change and high confidentiality impact warrant prioritized patching in any s390/IBM Z virtualization environment using vfio_ccw device passthrough.
Improper lock-aware cleanup in the s390/vfio_ccw subsystem of the Linux kernel exposes host systems to memory corruption when a virtualized channel device transitions to a non-operational state. The fsm_notoper() routine, invoked asynchronously upon device loss, performs private->cp resource cleanup while potentially holding the CIO subchannel lock, creating a lock inversion or use-after-free condition that crosses the VM-to-host boundary (CVSS S:C). The affected code path is specific to IBM Z (s390) architectures using vfio_ccw for channel I/O device passthrough to guests. No public exploit code has been identified at time of analysis, and vendor-released patches are available across multiple stable kernel branches.
Race conditions in the s390/vfio_ccw subsystem of the Linux kernel arise from an insufficiently scoped io_mutex that serialized io_regions but left other I/O operations unserialized, creating exploitable synchronization windows. Local low-privilege users inside guest VMs on IBM s390/zSeries hosts running vfio_ccw can exploit these races to achieve scope-changed privilege escalation into the host kernel, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified; vendor patches are confirmed across stable branches 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2.
Race condition in the Linux kernel's s390/vfio_ccw CRW (Channel Report Word) subsystem allows low-privileged local attackers on IBM mainframe KVM hosts to read incoherent CRW payload state, with CVSS-assessed potential for high confidentiality, integrity, and availability impact including scope change into the hypervisor. The root cause is an absent lock on the CRW payload list, which receives exclusively asynchronous hardware events and was therefore never protected for concurrent access. No public exploit code or CISA KEV listing exists; patches have been backported across multiple stable kernel branches including 6.12.105, 6.18.46, 7.1.10, and 7.2.
Local privilege escalation and kernel panic in the Linux kernel AMDGPU DRM subsystem allows a low-privileged local user to crash the system or potentially corrupt kernel memory by submitting a crafted GEM_CREATE ioctl with invalid domain flag combinations. The AMDGPU_GEM_CREATE ioctl validated individual domain bits against AMDGPU_GEM_DOMAIN_MASK but failed to reject illegal combinations of CPU, GTT, or VRAM domains mixed with special-purpose domains (DOORBELL, GDS, GWS, OA), causing amdgpu_bo_placement_from_domain() to write past the AMDGPU_BO_MAX_PLACEMENTS array boundary and trigger BUG_ON(), resulting in a kernel panic. No public exploit code or CISA KEV listing has been identified at time of analysis; patches are available across all active stable kernel branches.
Error propagation failure in the Linux kernel's XFS realtime filesystem subsystem corrupts filesystem state during xfs_growfs operations. The function xfs_rtginode_ensure() silently discards all non-ENOENT errors returned by xfs_rtginode_load(), leaving the realtime group inode pointer unset while growfs proceeds as though load succeeded - producing a null pointer dereference, kernel panic, or realtime subvolume metadata corruption. Patch commits targeting Linux 6.18.46, 7.1.10, and 7.2 are available via kernel.org stable branches; no public exploit or CISA KEV listing exists at time of analysis.
Use-After-Free in the XFS filesystem online repair subsystem of the Linux kernel allows a local low-privileged user to potentially achieve full kernel memory corruption and privilege escalation to root. The flaw in `xrep_tempfile_create` leaves `sc->tempip` as a dangling pointer when tempfile creation fails partway through, enabling subsequent dereference of freed memory. No public exploit has been identified at time of analysis, but the AV:L/AC:L/PR:L/C:H/I:H/A:H CVSS vector indicates any authenticated local user on an XFS-backed system can attempt exploitation with low complexity.
Data corruption in the Linux kernel's XFS exchange-range subsystem allows a low-privileged local attacker to trigger incorrect reflink inode flag clearing, causing subsequent writes to bypass Copy-on-Write protection on shared extents. Affected are Linux kernel versions prior to 6.12.105, 7.1.10, and 7.2 on systems using XFS volumes with reflink support enabled. No public exploit or CISA KEV listing exists at time of analysis, but the low-complexity local vector and high integrity/confidentiality impact make this a meaningful priority for XFS-heavy enterprise deployments such as RHEL-based systems where XFS is the default filesystem.
Indefinite process hang in the Linux kernel Ceph filesystem client allows a remote Ceph cluster participant to cause a denial of service by triggering MDS capability revocation on a victim client. The flaw in `__ceph_get_caps()` causes a reading process to sleep forever on `i_cap_wq` when stale `cap->mds_wanted` state prevents the client from reacquiring FILE_RD without an external wake-up. No public exploit code has been identified at time of analysis; patches are available across multiple Linux stable branches.
The SpacemiT K3 clock driver in the Linux kernel fails to mark the HDMA clock as CLK_IS_CRITICAL, allowing the kernel's Common Clock Framework to gate it during power management. On SpacemiT K3 SoCs running an X100 RISC-V core, this produces an irrecoverable system hang whenever TCM-dependent operations - such as page fault handling triggered by vector instructions - are attempted while the HDMA clock is inactive. No public exploit has been identified at time of analysis and exposure is strictly bounded to SpacemiT K3 hardware; upstream fix commits are confirmed available for affected stable branches.
Use-after-free race condition in the Linux kernel's AF_UNIX garbage collector (GC) allows a local user with low privileges to corrupt kernel heap memory with potential for privilege escalation. The race occurs between concurrent send() and close() operations on a crafted set of Unix domain sockets forming a Strongly Connected Component (SCC), causing unix_walk_scc_fast() to dereference a freed scc_entry when a partially-freed SCC is walked during the next GC cycle. The vulnerability is not in CISA KEV and no public exploit code has been identified at time of analysis; however, the CVSS 7.8 score and C:H/I:H/A:H impact triad reflect realistic kernel memory corruption severity.
NULL pointer dereference in the Linux kernel's in-kernel OpenVPN data-plane module (ovpn) allows a network-reachable peer to crash the kernel by triggering key removal against a crypto slot that is not populated. Affected kernels span the ovpn-enabled range from commit 89d3c0e4612afa1c6429ed68d298e35592fbe208 through versions prior to 6.18.46, 7.1.10, and 7.2. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation impact is full availability loss of the VPN gateway via kernel panic.
A use-after-free / lifetime race in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets crypto completion callbacks outlive the peer and netdev they depend on. Because the callback holds both key-slot and peer references, dropping the last peer reference too early can schedule an RCU callback backed by already-freed module text after ovpn_cleanup's rcu_barrier has run, corrupting kernel memory during peer teardown or module removal. There is no public exploit identified at time of analysis, and despite the input's 9.8 CVSS this is a teardown-path race, not a remote unauthenticated RCE.
Use-after-free in the Linux kernel perf subsystem allows a local low-privileged user to obtain a dangling pointer to a freed perf_event structure, enabling memory corruption with full confidentiality, integrity, and availability impact. Affected are stable kernel series 6.6.x, 6.12.x, 6.18.x (up to 6.18.46), and 7.1.x (up to 7.1.10). No public exploit code or CISA KEV listing exists at time of analysis, but the local privilege escalation primitive is significant on multi-tenant Linux systems.
Out-of-bounds read in the RISC-V ZBB-optimized strnlen() routine of the Linux kernel allows the aligned-word loop to load one machine word past the caller-supplied count boundary; when the source is aligned and count is a multiple of the register size, the extra load lands exactly at s+count and faults if that address sits on an unmapped page boundary. The affected code path only runs on RISC-V hardware exposing the Zbb bitmanip extension. This has been fixed upstream (stable commits e697e30f and 5d588c68); no public exploit identified at time of analysis, and the CNA's 9.4 network-vector scoring is inconsistent with an arch-local kernel string-length primitive.
Unsafe sleeping in atomic context within the Linux kernel's ovpn module can crash affected systems during VPN key slot teardown. When AEAD crypto transforms are freed via a plain RCU callback, implementations backed by asynchronous or hardware crypto accelerators may block inside crypto_free_aead - an operation forbidden in softirq/atomic context - triggering a kernel BUG or panic and denying service to the host. Systems running Linux 6.16 or unpatched stable branches with the ovpn kernel module active and a non-synchronous AEAD backend are at risk; no public exploit has been identified and the flaw is absent from CISA KEV.
Reference count corruption in the Linux kernel netfilter ipset subsystem allows a local low-privileged attacker to trigger a kernel panic via a race condition between list:set garbage collection and ip_set_swap(). The flaw exists because __ip_set_put_byindex() resolves a set index to a pointer under RCU but acquires ip_set_ref_lock only afterward to decrement the refcount, creating a window where ip_set_swap() can atomically reassign both the ip_set_list slot and the associated refcount before the lock is taken - causing the GC path to decrement a refcount that has already moved, hitting BUG_ON(set->ref == 0) and a fatal kernel panic. All Linux stable branches from 3.8 through pre-patch 5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.1, and 7.2 are affected; no public exploit has been identified at time of analysis.
Use-after-free in the Linux kernel netfilter flowtable (nf_flow_table_offload) arises from an ordering bug in how connection-tracking tuple nodes are published to the rhashtable. Because nf_flow_table_iterate() treats only the original-direction node as the owning entry, publishing it before the reply node lets the garbage collector observe and free a flow while flow_offload_add() is still inserting the reply node, producing slab-use-after-free reads and writes reachable through rht_deferred_worker, jhash, flow_offload_del and flow_offload_lookup. The flaw affects systems using software/hardware flow offload; no public exploit identified at time of analysis, though the CNA-assigned CVSS is 9.8.
Deadlock vulnerability in the Linux kernel's bnxt (Broadcom NetXtreme) ethernet driver causes kernel hangs or crashes on systems with Broadcom bnxt NICs when an IRQ affinity notifier callback and the bnxt work-cancellation path simultaneously contend for the netdev instance lock. The affinity notifier callback acquires the lock to restart the queue while cancellation synchronously waits for that callback to finish - both paths block indefinitely, resulting in full availability loss for the affected network interface and potentially the host. No public exploit code exists and the vulnerability is absent from CISA KEV; the assigned CVSS vector (AV:N/PR:N) is inconsistent with the described kernel-local race and should be treated with skepticism.
Indefinite TX queue stall in the Linux kernel veth driver allows a denial-of-service condition against multi-queue virtual Ethernet interfaces running GRO without an XDP program attached. The root cause is that veth_poll() incorrectly uses rq->xdp_rxq.queue_index to determine which peer TX queue to wake - a field that is zero-initialized and only populated when XDP is active - causing all NAPI instances to wake peer TX queue 0 instead of the correct queue. In a multi-queue veth setup, a stopped TX queue (e.g., queue 1 halted due to ptr_ring saturation) is never woken, producing an indefinite transmit stall with no watchdog recovery because veth implements no ndo_tx_timeout. No public exploit is identified at time of analysis; reproduction scripts are publicly available from the reporter.
Traffic Control BPF classifier (cls_bpf) in the Linux kernel fails to validate that a hardware-offloaded SCHED_CLS program's bound network device matches the target TC classifier device, allowing a local attacker with CAP_NET_ADMIN to attach a program loaded for device A to device B via skip_sw. When device A is subsequently removed, the kernel destroys the program's offload state while it remains live on device B, producing a use-after-free condition that triggers a kernel WARN or panic (guaranteed denial of service with panic_on_warn=1, with potential for privilege escalation via the memory corruption primitive). Patches are available across multiple stable kernel branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Credential exposure in Rently Smart Home versions 20.1.0 and prior allows authenticated network-based attackers to retrieve all property access PINs, including the Master Pin that overrides the standard user permission hierarchy. Reported by ICS-CERT via CISA advisory ICSA-26-237-01, the flaw is particularly severe in property rental contexts where Master Pin retrieval translates directly to unauthorized physical access to tenant properties. No public exploit code has been identified at time of analysis, but the low attack complexity and network-accessible vector make this a genuine operational and physical security risk.
Arbitrary file deletion in the Order Tip for WooCommerce WordPress plugin (versions before 1.6.0) allows authenticated Shop Managers to delete any file on the web server by exploiting missing capability checks and absent path restrictions on the deletion endpoint. The plugin fails to validate both the requesting user's permissions and the target file path, meaning a malicious or compromised Shop Manager account could remove critical WordPress files such as wp-config.php, leading to full site compromise. A publicly available proof-of-concept exists per WPScan; however, EPSS sits at only 0.17% (6th percentile) and CISA has not added this to KEV, consistent with the SSVC assessment of no observed exploitation.
Improper access control on the debug and engineering interfaces of Danfoss iC7-Automation SP, iC7-Marine, and iC7-Hybrid GR3 drive platforms lets attackers read and write internal device values and, more critically, upload and execute unsigned applications, EEPROM data, and firmware through exposed service and software-update mechanisms. Rated CVSS 4.0 9.3, the flaw effectively bypasses code-signing and grants full control over affected industrial drive controllers. There is no public exploit identified at time of analysis, but the missing authentication and firmware-overwrite capability make this a severe integrity and availability risk for operational technology environments.
Privilege boundary violation in FreeBSD's hwpmc(4) hardware performance monitoring subsystem allows a low-privileged local user to continue observing a process via attached PMCs after that process elevates privileges by executing a setuid or setgid binary, directly contrary to the kernel's intended security policy. Affected versions span FreeBSD 14.4-RELEASE before p9, 15.0-RELEASE before p13, and 15.1-RELEASE before p3; vendor patches are available per FreeBSD Security Advisory SA-26:56. No public exploit has been identified and EPSS sits at 0.15% (5th percentile), placing this as a low near-term exploitation priority despite the high vendor CVSS score.
Mailbox initialization in Trusted Firmware-M (TF-M) versions 2 through 2.3.0 on PSOC64 and RP2350 platforms fails to validate a pointer supplied by non-secure world code, allowing a low-privileged attacker with physical access to supply a crafted pointer that crosses the TrustZone-M hardware security boundary. Successful exploitation yields full read, write, and denial-of-service capability over the Secure Processing Environment (SPE), collapsing the hardware-enforced isolation TF-M is designed to guarantee - including potential exposure of cryptographic keys, attestation credentials, and secure boot state. No public exploit code exists and this vulnerability is absent from the CISA KEV catalog; the physical attack vector and high complexity substantially constrain opportunistic exploitation, but the full C/I/A scope change makes targeted supply-chain or insider-threat scenarios consequential.
Unauthenticated administrator account takeover affects the TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress in all versions through 3.3.1, where the 'trp_get_translations_regular' AJAX action returns raw translation-dictionary entries without access control. Because an administrator's password-reset URL can be persisted into the secondary-language dictionary as a translatable string, an unauthenticated attacker can read the plaintext reset key and login parameters and seize the admin account. Reported by Wordfence; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Cleartext exposure of LoRaWAN cryptographic session keys via NFC interface in dozens of Milesight IoT sensor and controller models allows any physically proximate unauthenticated attacker to retrieve ABP NwkSKey, AppSKey, and D2D keys through a commodity NFC read operation. The stolen keys enable full compromise of LoRaWAN communications for the affected device, including decryption of captured traffic, forgery of uplink and downlink frames with valid message integrity codes, injection of falsified sensor data, issuance of device commands, and disruption of legitimate frame processing. No public exploit has been identified at time of analysis, and this CVE is not listed in CISA KEV, but the attack itself requires no technical sophistication once physical proximity is achieved.
Cleartext exposure of LoRaWAN cryptographic session keys through the NFC interface of Milesight IoT sensor devices enables a physically proximate unauthenticated attacker to retrieve NwkSKey, AppSKey, and D2D keys from any affected device via a trivial NFC read operation. With these keys, an adversary can decrypt all ABP-mode LoRaWAN traffic for the compromised device, forge both uplink and downlink frames with valid session keys, inject falsified sensor readings into network servers, issue supported device commands, and cause legitimate frames to be rejected by consuming frame counters. No active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified at time of analysis, but the attack requires no credentials and succeeds in seconds with commodity NFC hardware against any physically accessible affected device.
Unauthenticated arbitrary file download in DocSys V2.02.80 exposes the entire server filesystem to remote attackers via the `downloadDocEx.do` endpoint. The `targetPath` parameter accepts arbitrary filesystem paths with no authentication gate, allowing any unauthenticated network attacker to retrieve sensitive files such as configuration files, credentials, or application data. No public exploit code has been identified at time of analysis, and EPSS at 0.17% (6th percentile) signals low current exploitation activity, though the attack is trivially simple to reproduce.
Kimai's Twig sandbox exposes server-wide secrets through an unrestricted config() function in administrator-uploaded invoice and export templates, affecting all versions before 2.56.0. An administrator with template upload privileges can craft a malicious template that renders sensitive configuration values - including LDAP bind passwords and SAML SP private keys - directly into invoice or export documents. Those documents are then delivered to lower-privileged users such as team leads who generate them, creating a stealthy credential exfiltration channel. No public exploit identified at time of analysis, and no CISA KEV listing is present in the provided data.
Unauthorized project report export in Kimai before 2.64.0 allows any authenticated user, regardless of role, to download the full project overview export via the unprotected `report_project_view_export` route, exposing customer names, project names, currency, budget type, and aggregate totals across all customers. The root cause is a misplaced authorization guard attached to the `__invoke` method on a sibling route rather than at the controller class level, leaving the export route with no access control. No public exploit code has been identified at time of analysis, but the vulnerability is trivially exploitable by any valid Kimai account holder.
Uncontrolled ZIP extraction in LeafWiki 0.10.0 through 0.12.0 allows any authenticated Editor or Admin to exhaust server disk or memory by uploading a crafted ZIP bomb via the import route. The vulnerable function ZipExtractor.ExtractToDir uses Go's io.Copy without a decompressed-size limit, so a maximally compressed archive well inside the 500 MiB upload cap can expand to hundreds of gigabytes on disk - or into RAM when the OS temporary directory is tmpfs-backed. No public exploit has been identified at time of analysis, though the attack is mechanically simple for any credentialed Editor.
DPoP proof replay attack in Spring Security's DPoPProofJwtDecoderFactory allows unauthenticated network attackers to bypass token binding protections by evicting cached JWT ID entries through request flooding, then replaying captured valid DPoP proofs to impersonate legitimate users. Affected versions span Spring Security 6.5.0-6.5.11, 7.0.0-7.0.6, and 7.1.0, impacting any Java application using Spring Security's DPoP-based OAuth 2.0 validation. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS C:H/I:H ratings reflect full token-holder impersonation upon successful exploitation.
Information disclosure in the Drupal Commerce Elavon payment-gateway module stems from improper input validation (CWE-20) and, per the NVD scoring, is reachable by remote unauthenticated attackers. The Drupal security advisory (SA-CONTRIB-2026-084) leaves the affected range wholly unspecified ('*.*'), so every published version should be treated as potentially vulnerable until a fixed release is identified. No public exploit identified at time of analysis, and the EPSS score sits in the 4th percentile, indicating little observed exploitation interest despite the headline 9.8 rating.
Observable timing discrepancy in the Drupal Token Content Access module exposes token-protected content to brute-force enumeration via side-channel analysis. All module versions from 0.0.0 through 3.1.2 are affected; unauthenticated remote attackers (PR:N, AV:N per CVSS) can measure differential response times during token validation to reconstruct valid access tokens character-by-character, ultimately bypassing content access restrictions. No active exploitation has been confirmed (SSVC exploitation: none, EPSS 0.14%, no KEV listing), and a vendor patch is available per Drupal SA-CONTRIB-2026-090.
Rewrite valve processing in Apache Tomcat contains an off-by-one error (CWE-193) in the handling of the [N] (Next) flag, causing rule iteration to restart from the second rewrite rule instead of the first, which can produce unintended looping behavior and result in a denial-of-service condition. Affected supported versions span Tomcat 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24; the EOL 8.5.x branch is also affected but will not receive a fix. No active exploitation is confirmed (not in CISA KEV), EPSS stands at 0.20% (10th percentile), and no public exploit code has been identified at time of analysis.
Improper input validation in Apache Tomcat 9.0.115-9.0.120, 10.1.53-10.1.57, and 11.0.20-11.0.24 stems from an incomplete fix for CVE-2026-32990 and, per its CVSS:3.1 vector, permits remote unauthenticated attackers to compromise confidentiality, integrity, and availability of the servlet container. Reported by the Apache security team, it carries a critical 9.8 base score, though vendor tagging labels the impact as Information Disclosure, which is narrower than the vector implies. No public exploit identified at time of analysis, and EPSS estimates exploitation probability at just 0.21% (11th percentile).
Apache Tomcat's Unix domain socket creation path exposes a TOCTOU race condition across versions 9.0.42-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, enabling an unauthorized local OS user to seize the socket before Tomcat finalizes access permissions. The vendor-assigned CVSS 8.1 with AV:N directly conflicts with the description's explicit 'local user' constraint and the inherently host-local nature of Unix domain sockets - the effective attack surface is limited to users with OS-level access on Tomcat hosts. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% (5th percentile), indicating negligible real-world exploitation pressure at time of analysis.
Arbitrary local file read in self-hosted Typebot prior to 3.18.0 allows any registered user to exfiltrate files readable by the server process - including environment variable secrets, credential encryption keys, and database connection strings - by publishing a chatbot whose Send Email block specifies an absolute filesystem path such as /etc/passwd or /proc/self/environ as an attachment. The root cause is a missing URL-scheme validation in the parseAttachments helper: any value not prefixed with the application's own base URL is passed directly to Nodemailer as a filesystem path, and the Nodemailer transport is instantiated without disableFileAccess, so it reads and emails the file to an attacker-controlled recipient. No public exploit has been identified at time of analysis, but the attack requires no special server configuration because open signup and system SMTP are both enabled by default.
TOTP second-factor brute-force protection in Punk::Plugin::TOTP before 0.05 for Perl is defeated by replaying a saved session cookie, allowing an attacker with valid first-factor credentials to reset the TOTP failure counter indefinitely. Because Punk::Session stores the entire session state - including the TOTP attempt counter - in a client-side signed cookie when no server-side store is configured, an attacker can save the cookie before failures accumulate and replay it to restore a fresh counter, cycling this indefinitely within the pending_ttl window. No public exploit has been identified at time of analysis, but the technique is trivially reproducible from the advisory description alone.
Two-factor authentication bypass in the Perl module Punk::Plugin::TOTP before 0.05 lets an attacker who already knows a victim's password clear the victim's TOTP challenge using a recovery code issued to the attacker's own account. The flaw stems from the recovery-code helper looking up codes by digest across all users and then binding ownership through a numeric comparison of user identifiers, which fails whenever accounts are keyed by username, email, or UUID. No CISA KEV listing and no public exploit identified at time of analysis, with a low EPSS score of 0.44% (37th percentile) despite the 9.8 CVSS rating.
Privilege escalation via symlink attack in SonicWall NetExtender Linux client (versions 10.3.5 and earlier) stems from the NEService auto-upgrade component insecurely handling temporary files, enabling a local low-privileged attacker to manipulate file paths and potentially overwrite or read privileged system files. The CVSS vector confirms full confidentiality, integrity, and availability impact despite requiring local access with high attack complexity. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, though SSVC classifies the technical impact as total.
Out-of-bounds read in OpenEXRUtil's SampleCountChannel::row() API allows an attacker to crash applications or leak adjacent heap memory by supplying a crafted deep EXR file with a non-zero dataWindow origin. Affected are OpenEXR releases through 3.2.10, 3.3.0-3.3.12, and 3.4.0-3.4.13 - the complete release history prior to the coordinated January 2026 patch. The CVSS vector (AV:N/AC:L/PR:N/UI:R) reflects that exploitation requires no authentication but does require a user or automated pipeline to open an attacker-controlled file; no public exploit code and no CISA KEV listing exist at time of analysis.
Unauthenticated access to the NVIDIA NemoClaw inference server on Linux exposes sensitive model inference data and enables denial of service by adjacent network attackers. The flaw stems from a missing authentication check (CWE-306) on the inference service endpoint, meaning any host on the same network segment can interact with the service without credentials. No active exploitation has been confirmed by CISA KEV and no public exploit code is known at time of analysis, but the low attack complexity and absence of authentication barriers make this straightforward to exploit for any attacker with adjacent network positioning.
Improper certificate validation in NVIDIA NemoClaw for Linux (versions up to and including 0.0.1) allows network attackers to intercept or manipulate the deployment process, potentially yielding information disclosure, data tampering, remote code execution, and privilege escalation. The flaw stems from the deployment routine failing to properly verify TLS certificates (CWE-295), enabling machine-in-the-middle attacks. No public exploit is identified at time of analysis and it is not listed in CISA KEV, but the vendor rates full technical impact.
Privilege escalation and remote code execution in NVIDIA OpenShell for Linux stem from an incomplete deny-list in its sandbox provisioning API, letting an authenticated attacker submit inputs that were meant to be blocked but were not. Because the flaw crosses the sandbox boundary (CVSS scope change), a successful exploit can yield code execution, privilege escalation, information disclosure, data tampering, and denial of service against the host. No public exploit identified at time of analysis, and the issue is not in CISA KEV.
Code injection in NVIDIA NemoClaw's migration command (Linux, versions up to 0.0.17) allows a local attacker with low-privilege access to inject and execute arbitrary code within the process context, yielding full confidentiality, integrity, and availability impact on the vulnerable system. SSVC rates technical impact as total, consistent with the CVSS 7.8 rating, though EPSS remains very low at 0.16% (5th percentile) and no active exploitation has been observed. No public exploit has been identified at time of analysis.
Untrusted code execution in NVIDIA NemoClaw for Linux (versions up to and including 0.0.21) stems from the installer executing code without verifying its integrity, letting an attacker who can supply or interpose malicious code during installation achieve arbitrary code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA assigns a CVSS of 9.8 with a fully network-based, no-privilege, no-interaction vector, though the flaw is rooted in the install process. There is no public exploit identified at time of analysis, EPSS is low at 0.25% (17th percentile), and CISA SSVC records no known exploitation.
OS command injection in NVIDIA NemoClaw for Linux allows a local low-privileged attacker to execute arbitrary operating system commands through the application's status and logs plugin command interfaces. The CVSS 7.8 score reflects high impact across confidentiality, integrity, and availability with low attack complexity and no user interaction required. No public exploit identified at time of analysis, and no CISA KEV listing observed, but the fully unscopeed local impact makes this a meaningful risk on multi-tenant or shared Linux systems running NemoClaw.
OS command injection in NVIDIA NemoClaw's NIM management component on Linux enables a local authenticated attacker to execute arbitrary operating system commands with the privileges of the targeted process. All versions of NemoClaw are indicated as affected per NVD CPE data (wildcard version range). Successful exploitation can result in full code execution, persistent data tampering, sensitive information disclosure, and denial of service on the host. No public exploit code or CISA KEV listing has been identified at time of analysis.
OS command injection in NVIDIA NemoClaw's command-line interface on Linux enables a local low-privileged attacker to execute arbitrary operating system commands, leading to full compromise of confidentiality, integrity, and availability. All versions of NemoClaw appear affected per the CPE wildcard (*), and the vulnerability is rooted in improper neutralization of user-supplied input passed to shell commands (CWE-78). No public exploit code and no CISA KEV listing have been identified at time of analysis, limiting current real-world risk primarily to environments with untrusted local users.
Weak authentication in NVIDIA NemoClaw for Linux (versions 0 through 0.0.4) lets remote attackers bypass the authentication enforced by its remote-access helper workflow, enabling code execution, information disclosure, and data tampering on the host. The flaw was self-reported by NVIDIA and carries a critical 9.8 CVSS rating with a fully unauthenticated network vector. No public exploit identified at time of analysis, and EPSS estimates only a 0.57% 30-day exploitation probability, so the raw severity outpaces observed real-world activity.
Unverified code download in NVIDIA NemoClaw installation scripts for Linux (versions 0.0.0 through 0.0.21) allows a network-positioned attacker to substitute malicious payloads during installation, enabling code execution, privilege escalation, information disclosure, and data tampering on the target host. The root cause is CWE-494: the installation pipeline fetches remote code without cryptographic integrity verification, leaving the download channel open to man-in-the-middle substitution or upstream server compromise. No public exploit has been identified at time of analysis; EPSS sits at 0.20% (9th percentile) and SSVC confirms Exploitation: none, placing this firmly in the theoretical high-severity category rather than an actively exploited threat.
OS command injection in NVIDIA NemoClaw's Telegram bridge component on Linux enables a local attacker with low-privileged access to execute arbitrary operating system commands. Exploitation yields full confidentiality, integrity, and availability compromise on the affected host, with potential for privilege escalation beyond the invoking user. No active exploitation is confirmed in CISA KEV and no public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) and minimal privilege requirement (PR:L) lower the practical bar for exploitation once local access is obtained.
Sandbox escape in NVIDIA OpenShell for Linux lets a low-privileged actor already operating inside the sandbox break its isolation boundary, potentially achieving code execution, privilege escalation, data tampering, and information disclosure on the host. The flaw is rooted in an uncontrolled search path element (CWE-427), so a resource the sandbox loads can be redirected to attacker-supplied code. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the assigned 9.9 CVSS reflects the full compromise achievable once the sandbox boundary is breached.
Path traversal in NVIDIA OpenShell Sandbox for Linux permits low-privileged network-authenticated attackers to bypass L7 REST network policy enforcement, reaching REST endpoints that policy rules were designed to block. The Changed Scope (S:C) in the CVSS vector signals that the real impact falls on downstream services or data stores protected by the bypassed policy, yielding high confidentiality exposure (C:H) and limited integrity impact (I:L) on resources outside the sandbox trust boundary. No active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified at time of analysis.
OS command injection in NVIDIA OpenShell across all supported platforms allows a network-accessible malicious gateway to execute arbitrary operating system commands on a victim host when a user interacts with that gateway. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) reflects that an attacker requires no privileges on the victim system but does require the victim to interact with a malicious or attacker-controlled gateway endpoint. Successful exploitation yields full code execution, data tampering, and information disclosure - with no public exploit or CISA KEV listing identified at time of analysis.
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Improper state validation in Google Chrome's Performance component (all versions prior to 152.0.7977.65) enables remote attackers to read memory contents within the Chrome sandbox by luring a user to a crafted HTML page. The scope is contained to the sandbox (S:U), limiting blast radius to in-process data, but sensitive browser state such as cookies, session tokens, or page content may be exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS of 0.22% (13th percentile) corroborates low observed exploitation activity.
Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).
DNS rebinding in genieacs-mcp's Streamable HTTP transport (versions <= 0.3.1) allows a malicious website to route browser requests through loopback to the unauthenticated /mcp listener and invoke arbitrary GenieACS NBI operations against managed CPE devices. Affected deployments expose full read/write access to TR-069 device state - including firmware update tasks, parameter changes, device reboots, presets, and connection requests - to any attacker who can lure the server operator to a malicious web page. A proof-of-concept is documented in the GitHub security advisory (GHSA-cmwv-wf9p-p8wx); no CISA KEV listing is present, indicating targeted rather than widespread exploitation at time of analysis.
Out-of-bounds pointer arithmetic in OpenEXR's TypedDeepImageChannel::row() - and parallel methods in FlatImageChannel and SampleCountChannel - affects all releases before 3.2.11, 3.3.13, and 3.4.14, exposing applications that process deep EXR files with nonzero dataWindow origins to deterministic crash or limited heap memory disclosure. The CVSS 7.1 score (AV:N/AC:L/PR:N/UI:R) reflects unauthenticated, low-complexity delivery of a crafted image file requiring only that a user or pipeline opens it, with high availability impact and limited confidentiality exposure. No CISA KEV listing and no public exploit code have been identified at time of analysis; patched releases are available from the Academy Software Foundation.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a victim opens a specially crafted VI (Virtual Instrument) file. The root cause is CWE-787 (Out-of-bounds Write), indicating a write operation beyond the bounds of an allocated buffer during VI file parsing. No public exploit code or active exploitation has been identified at time of analysis, but the file-borne delivery model is realistic in engineering and research environments where LabVIEW projects are routinely shared.
Heap out-of-bounds read in OpenEXRUtil's deep and flat image channel row() API allows an attacker supplying a crafted EXR file with a non-zero dataWindow origin to crash any application that processes the file, with conditional heap memory disclosure dependent on attacker-controlled heap layout. Affected are OpenEXRUtil versions 3.3.0-3.3.12 and 3.4.0-3.4.12; the flaw exists across three channel header implementations (ImfDeepImageChannel.h, ImfFlatImageChannel.h, ImfSampleCountChannel.h). No public exploit identified at time of analysis, and patched releases 3.3.13 and 3.4.13 are available.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The root cause is an out-of-bounds read (CWE-125) that, combined with tags indicating buffer overflow behavior, can corrupt memory state sufficient to achieve code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.5 reflects the high impact potential once a victim opens a malicious VI file.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Rooted in CWE-125 (Out-of-bounds Read), the parser reads beyond allocated buffer boundaries, which can expose adjacent memory or - under favorable heap conditions - enable full code execution. No public exploit or CISA KEV listing has been identified at time of analysis, though the RCE potential and broad LabVIEW user base warrant prioritized patching.
Memory corruption in NI LabVIEW (all versions through 26.3.0) enables information disclosure or arbitrary code execution when a user opens a specially crafted VI (Virtual Instrument) file. The CVSS 4.0 base score of 8.5 reflects high impact across confidentiality, integrity, and availability on the vulnerable system, with local file-based delivery requiring passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE potential and industrial control / engineering deployment context warrant prompt patching.
Memory corruption in NI LabVIEW 26.3.0 and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Classified under CWE-125 (Out-of-bounds Read), the flaw's buffer-overflow and RCE tags suggest that the out-of-bounds read condition can, under certain memory layout circumstances, corrupt control-flow data and escalate beyond information disclosure to full code execution. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis; NI has published a vendor security advisory.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The CWE-787 out-of-bounds write root cause combined with the high-impact CVSS 4.0 score of 8.5 places this in a serious tier for LabVIEW deployments across engineering, scientific, and industrial automation environments. No public exploit code has been identified at time of analysis, but the user-interaction trigger (social engineering via malicious VI file) is a well-understood threat model for desktop engineering tools.
Kernel-state confusion in the Linux MPTCP subsystem allows a remote peer to leave stale Multipath TCP Fast Open (MPTFO) state on a passively-opened socket by sending a valid-cookie TCP Fast Open SYN that carries no payload. Because mptcp_fastopen_subflow_synack_set_params() set the is_mptfo flag before verifying that data was actually queued, a data-less TFO SYN triggers a WARN and, if non-fatal, leaves the subflow in an inconsistent state that can later be tripped inside check_fully_established(). The upstream fix marks the subflow as MPTFO only after an SKB is confirmed queued and returns quietly on an empty receive queue. No public exploit identified at time of analysis; the input carries the inflated CVSS 9.4 typical of automated kernel-CVE scoring rather than a demonstrated high-impact primitive.
Heap buffer overflow in the Linux kernel's s390/qeth driver exposes IBM System z hosts to local kernel memory corruption via malformed SNMP and ARP query ioctl calls. Affected systems run Linux kernel versions from 2.6.26 through the last unfixed stable releases across eight stable branches, with patches available in 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2. An attacker supplying a zero or undersized udata_len value to qeth_snmp_command() or qeth_l3_arp_query() triggers a u32 integer underflow in the callback bounds check, allowing memcpy to write past the kernel heap allocation and potentially achieve kernel code execution. No public exploit code and no CISA KEV listing have been identified at time of analysis.
PMD huge page mapping boundary violation in the Linux kernel's drm/shmem_helper subsystem allows local users with low privileges to trigger out-of-bounds memory mappings via the DRM ->huge_fault handler. The handler installs PMD-level Transparent Huge Page mappings without verifying they remain within Virtual Memory Area boundaries, triggering a VM_BUG_ON_VMA() assertion when the mapping subsequently reaches copy_pmd_range() during fork or remap operations. Patches have been committed to Linux 7.1.10 and 7.2 stable branches; no public exploit has been identified at time of analysis.
Out-of-bounds kernel memory write in the Linux framebuffer device (fbdev) subsystem exposes systems to potential privilege escalation by local low-privileged users. The flaw resides in show_modes(), which accumulates unchecked snprintf() return values while building sysfs output, allowing the write offset to advance beyond the PAGE_SIZE sysfs buffer when a display device has a sufficiently long modelist. No public exploit has been identified at time of analysis; patched kernel versions 7.1.10 and 7.2 are available via the stable kernel tree.
Use-after-free in the Linux kernel's fbdev framebuffer subsystem allows a local low-privileged user to trigger a stale pointer dereference with potential for information disclosure, memory corruption, or privilege escalation. When userspace issues FBIOPUT_VSCREENINFO with FB_ACTIVATE_INV_MODE via the fb_set_var() path, a videomode entry may be deleted from the modelist while fb_info->mode still holds a dangling pointer to the freed entry; a subsequent sysfs read via show_mode() then dereferences freed kernel memory. No public exploit has been identified at time of analysis, and this vulnerability is not listed in CISA KEV.
Missing bounds validation in the amdgpu DRM driver's GFX ring command submission path allows a local low-privileged user to submit oversized Indirect Buffer (IB) requests that corrupt adjacent control bits in GPU ring packet fields, destabilizing command submission and potentially achieving kernel memory corruption with scope-changing impact. Affected systems must have AMD GPU hardware and the amdgpu kernel module loaded; the vulnerability is present across multiple stable branches prior to Linux 6.12.105, 7.1.10, 6.18.46, and 7.2. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor-released patches are available for all affected stable branches.
Out-of-bounds memory access in the Linux kernel's cs40l50-vibra haptic driver allows a local low-privileged user to read or write beyond allocated kernel buffers by submitting a crafted force-feedback effect via EVIOCSFF ioctl. The driver's cs40l50_add() function fails to validate user-supplied custom_len before dereferencing custom_data[0] and custom_data[1], and an integer sign-wrap in bank type handling permits negative array indexing into vib->dsp.banks[]. Three distinct code paths are exploitable: zero-length allocation returning ZERO_SIZE_PTR, single-word allocation followed by a two-word read, and s16 overflow enabling out-of-bounds bank array access. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
Use-after-free race condition in the Linux kernel BYD PS/2 mouse driver allows a local low-privileged user to corrupt kernel memory by racing a device disconnect event against in-flight timer callbacks. Affected systems must run an unpatched Linux kernel with BYD PS/2 touchpad hardware present and the byd module loaded, spanning stable branches from approximately kernel 4.6 through pre-fix releases ahead of 6.18.46, 7.1.10, and 7.2. No public exploit code has been identified at time of analysis, and this vulnerability is not currently listed in the CISA KEV catalog.
Out-of-bounds memory write in the Linux kernel's synaptics-rmi4 input driver allows a local attacker with access to a malicious or malfunctioning RMI4 touchpad device to corrupt kernel memory, potentially enabling privilege escalation or information disclosure. The root cause is a mismatch between the F54 report buffer allocation size (derived from F54 electrode counts) and the transfer size computed from F55 electrode counts - both sourced directly from device queries with no cross-validation. Vendor patches are confirmed across multiple stable kernel branches; no public exploit or CISA KEV listing has been identified at time of analysis.
Incorrect error-path logic in the Linux kernel's Qualcomm Crypto Engine (QCE) driver allows a local attacker with low privileges on Qualcomm SoC-based hardware to potentially trigger memory corruption via a use-after-free or improper resource release condition. The flaw resides in `devm_qce_register_algs`, where a failed `ops->register_algs()` call causes the cleanup loop to repeatedly invoke `ops->unregister_algs()` on the failed slot rather than iterating over previously successfully registered algorithm slots - leaving registered algorithms unreleased and potentially double-freeing or corrupting state. No public exploit identified at time of analysis, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.
Out-of-bounds kernel memory read in the Linux kernel's libceph client (decode_watchers()) lets a malicious or compromised Ceph OSD trigger a 4-byte read past a validated buffer when it returns an obj_list_watch_response_t reply with struct_len=0. Any kernel client issuing CEPH_OSD_OP_LIST_WATCHERS is affected; the leaked garbage value is then used as a watcher count for allocation, risking information disclosure or unstable allocation behavior. Tagged as Information Disclosure with no public exploit identified at time of analysis and no CISA KEV listing, despite an NVD CVSS of 9.8.
Use-after-free race condition in the Linux kernel atmel-mci MMC/SD controller driver allows a local privileged user to corrupt freed kernel memory by racing module removal against queued bottom-half work items. Systems running Linux on Atmel AT91 or AVR32 SoC hardware with the atmel-mci driver loaded are exclusively affected; x86/x64 deployments are unaffected by design. Patch commits are confirmed available for stable branches 6.12.x, 6.18.x, 7.1.x, and 7.2, with no public exploit identified at time of analysis.
Memory leak in the Linux kernel s390/vfio_ccw subsystem enables a guest VM user to exhaust host kernel memory by submitting crafted channel programs that trigger cp_init() failure paths, leaving ccwchain segments unfreed. Affected deployments are IBM s390 (mainframe) KVM hosts that have vfio channel command word (CCW) device passthrough configured, making the attack surface highly specific. No public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog; CVSS 7.1 with S:C reflects the guest-to-host cross-boundary availability impact.
Uncontrolled recursion in the Linux kernel's s390 vfio-ccw driver lets a local actor on IBM Z (s390) hosts submit a channel program containing an unbounded number of chained CCW/Transfer-in-Channel (TIC) segments, which are processed recursively and can exhaust the kernel stack. Affected are s390 systems using vfio-ccw device passthrough to KVM guests; the impact is host instability and potential kernel memory corruption. No public exploit is identified at time of analysis, it is not in CISA KEV, and no EPSS score was provided.
Use-after-free in the Linux kernel's s390/vfio_ccw subsystem allows a local low-privileged user on IBM Z hardware to corrupt freed kernel memory by triggering workqueue dispatch after the owning private struct has been released. Affected systems are those running KVM guests with VFIO CCW I/O channel passthrough on s390 architecture, spanning kernel versions from 4.12 through multiple unpatched stable branches. No public exploit or CISA KEV entry exists at time of analysis, but the scope-changing CVSS vector reflects the potential to compromise the host kernel or co-resident VMs.
Out-of-bounds region index access in the Linux kernel's s390/vfio_ccw subsystem exposes systems to potential guest-to-host privilege escalation on IBM mainframe KVM deployments. The read/write region handlers lack the bounds clamping that was applied to the capability chain regions, allowing a low-privileged local attacker - typically a KVM guest with vfio_ccw passthrough access - to trigger out-of-bounds memory access with a CVSS Scope:Changed impact. Vendor-released patches are available across multiple stable kernel branches, and no public exploit has been identified at time of analysis.
Host-side memory corruption/information disclosure in the Linux kernel s390 vfio_ccw driver allows a malicious or compromised KVM guest on IBM Z mainframes to exploit a double-fetch race when the driver reads a guest-supplied IDAL (Indirect Data Address List). Because the first IDAW is read separately to size the transfer buffer, a guest that changes that address between reads can desynchronize the buffer size from the actual IDAW set, corrupting or leaking host memory (S:C, C:H/I:H/A:H, CVSS 9.3). No public exploit identified at time of analysis and the issue is not in CISA KEV; the fix (verifying the first IDAW is unchanged between reads) is available upstream via stable kernel commits.
Out-of-bounds read in the Linux kernel's s390/vfio_ccw subsystem exposes host kernel memory to guest VM users, caused by an off-by-one error in the CCW chain length validation loop within `ccwchain_calc_length()`. Affected versions span from Linux 4.12 across multiple stable branches, with vendor-released patches confirmed in 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV; however, the guest-to-host scope change and high confidentiality impact warrant prioritized patching in any s390/IBM Z virtualization environment using vfio_ccw device passthrough.
Improper lock-aware cleanup in the s390/vfio_ccw subsystem of the Linux kernel exposes host systems to memory corruption when a virtualized channel device transitions to a non-operational state. The fsm_notoper() routine, invoked asynchronously upon device loss, performs private->cp resource cleanup while potentially holding the CIO subchannel lock, creating a lock inversion or use-after-free condition that crosses the VM-to-host boundary (CVSS S:C). The affected code path is specific to IBM Z (s390) architectures using vfio_ccw for channel I/O device passthrough to guests. No public exploit code has been identified at time of analysis, and vendor-released patches are available across multiple stable kernel branches.
Race conditions in the s390/vfio_ccw subsystem of the Linux kernel arise from an insufficiently scoped io_mutex that serialized io_regions but left other I/O operations unserialized, creating exploitable synchronization windows. Local low-privilege users inside guest VMs on IBM s390/zSeries hosts running vfio_ccw can exploit these races to achieve scope-changed privilege escalation into the host kernel, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified; vendor patches are confirmed across stable branches 6.6.153, 6.12.105, 6.18.46, 7.1.10, and 7.2.
Race condition in the Linux kernel's s390/vfio_ccw CRW (Channel Report Word) subsystem allows low-privileged local attackers on IBM mainframe KVM hosts to read incoherent CRW payload state, with CVSS-assessed potential for high confidentiality, integrity, and availability impact including scope change into the hypervisor. The root cause is an absent lock on the CRW payload list, which receives exclusively asynchronous hardware events and was therefore never protected for concurrent access. No public exploit code or CISA KEV listing exists; patches have been backported across multiple stable kernel branches including 6.12.105, 6.18.46, 7.1.10, and 7.2.
Local privilege escalation and kernel panic in the Linux kernel AMDGPU DRM subsystem allows a low-privileged local user to crash the system or potentially corrupt kernel memory by submitting a crafted GEM_CREATE ioctl with invalid domain flag combinations. The AMDGPU_GEM_CREATE ioctl validated individual domain bits against AMDGPU_GEM_DOMAIN_MASK but failed to reject illegal combinations of CPU, GTT, or VRAM domains mixed with special-purpose domains (DOORBELL, GDS, GWS, OA), causing amdgpu_bo_placement_from_domain() to write past the AMDGPU_BO_MAX_PLACEMENTS array boundary and trigger BUG_ON(), resulting in a kernel panic. No public exploit code or CISA KEV listing has been identified at time of analysis; patches are available across all active stable kernel branches.
Error propagation failure in the Linux kernel's XFS realtime filesystem subsystem corrupts filesystem state during xfs_growfs operations. The function xfs_rtginode_ensure() silently discards all non-ENOENT errors returned by xfs_rtginode_load(), leaving the realtime group inode pointer unset while growfs proceeds as though load succeeded - producing a null pointer dereference, kernel panic, or realtime subvolume metadata corruption. Patch commits targeting Linux 6.18.46, 7.1.10, and 7.2 are available via kernel.org stable branches; no public exploit or CISA KEV listing exists at time of analysis.
Use-After-Free in the XFS filesystem online repair subsystem of the Linux kernel allows a local low-privileged user to potentially achieve full kernel memory corruption and privilege escalation to root. The flaw in `xrep_tempfile_create` leaves `sc->tempip` as a dangling pointer when tempfile creation fails partway through, enabling subsequent dereference of freed memory. No public exploit has been identified at time of analysis, but the AV:L/AC:L/PR:L/C:H/I:H/A:H CVSS vector indicates any authenticated local user on an XFS-backed system can attempt exploitation with low complexity.
Data corruption in the Linux kernel's XFS exchange-range subsystem allows a low-privileged local attacker to trigger incorrect reflink inode flag clearing, causing subsequent writes to bypass Copy-on-Write protection on shared extents. Affected are Linux kernel versions prior to 6.12.105, 7.1.10, and 7.2 on systems using XFS volumes with reflink support enabled. No public exploit or CISA KEV listing exists at time of analysis, but the low-complexity local vector and high integrity/confidentiality impact make this a meaningful priority for XFS-heavy enterprise deployments such as RHEL-based systems where XFS is the default filesystem.
Indefinite process hang in the Linux kernel Ceph filesystem client allows a remote Ceph cluster participant to cause a denial of service by triggering MDS capability revocation on a victim client. The flaw in `__ceph_get_caps()` causes a reading process to sleep forever on `i_cap_wq` when stale `cap->mds_wanted` state prevents the client from reacquiring FILE_RD without an external wake-up. No public exploit code has been identified at time of analysis; patches are available across multiple Linux stable branches.
The SpacemiT K3 clock driver in the Linux kernel fails to mark the HDMA clock as CLK_IS_CRITICAL, allowing the kernel's Common Clock Framework to gate it during power management. On SpacemiT K3 SoCs running an X100 RISC-V core, this produces an irrecoverable system hang whenever TCM-dependent operations - such as page fault handling triggered by vector instructions - are attempted while the HDMA clock is inactive. No public exploit has been identified at time of analysis and exposure is strictly bounded to SpacemiT K3 hardware; upstream fix commits are confirmed available for affected stable branches.
Use-after-free race condition in the Linux kernel's AF_UNIX garbage collector (GC) allows a local user with low privileges to corrupt kernel heap memory with potential for privilege escalation. The race occurs between concurrent send() and close() operations on a crafted set of Unix domain sockets forming a Strongly Connected Component (SCC), causing unix_walk_scc_fast() to dereference a freed scc_entry when a partially-freed SCC is walked during the next GC cycle. The vulnerability is not in CISA KEV and no public exploit code has been identified at time of analysis; however, the CVSS 7.8 score and C:H/I:H/A:H impact triad reflect realistic kernel memory corruption severity.
NULL pointer dereference in the Linux kernel's in-kernel OpenVPN data-plane module (ovpn) allows a network-reachable peer to crash the kernel by triggering key removal against a crypto slot that is not populated. Affected kernels span the ovpn-enabled range from commit 89d3c0e4612afa1c6429ed68d298e35592fbe208 through versions prior to 6.18.46, 7.1.10, and 7.2. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation impact is full availability loss of the VPN gateway via kernel panic.
A use-after-free / lifetime race in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets crypto completion callbacks outlive the peer and netdev they depend on. Because the callback holds both key-slot and peer references, dropping the last peer reference too early can schedule an RCU callback backed by already-freed module text after ovpn_cleanup's rcu_barrier has run, corrupting kernel memory during peer teardown or module removal. There is no public exploit identified at time of analysis, and despite the input's 9.8 CVSS this is a teardown-path race, not a remote unauthenticated RCE.
Use-after-free in the Linux kernel perf subsystem allows a local low-privileged user to obtain a dangling pointer to a freed perf_event structure, enabling memory corruption with full confidentiality, integrity, and availability impact. Affected are stable kernel series 6.6.x, 6.12.x, 6.18.x (up to 6.18.46), and 7.1.x (up to 7.1.10). No public exploit code or CISA KEV listing exists at time of analysis, but the local privilege escalation primitive is significant on multi-tenant Linux systems.
Out-of-bounds read in the RISC-V ZBB-optimized strnlen() routine of the Linux kernel allows the aligned-word loop to load one machine word past the caller-supplied count boundary; when the source is aligned and count is a multiple of the register size, the extra load lands exactly at s+count and faults if that address sits on an unmapped page boundary. The affected code path only runs on RISC-V hardware exposing the Zbb bitmanip extension. This has been fixed upstream (stable commits e697e30f and 5d588c68); no public exploit identified at time of analysis, and the CNA's 9.4 network-vector scoring is inconsistent with an arch-local kernel string-length primitive.
Unsafe sleeping in atomic context within the Linux kernel's ovpn module can crash affected systems during VPN key slot teardown. When AEAD crypto transforms are freed via a plain RCU callback, implementations backed by asynchronous or hardware crypto accelerators may block inside crypto_free_aead - an operation forbidden in softirq/atomic context - triggering a kernel BUG or panic and denying service to the host. Systems running Linux 6.16 or unpatched stable branches with the ovpn kernel module active and a non-synchronous AEAD backend are at risk; no public exploit has been identified and the flaw is absent from CISA KEV.
Reference count corruption in the Linux kernel netfilter ipset subsystem allows a local low-privileged attacker to trigger a kernel panic via a race condition between list:set garbage collection and ip_set_swap(). The flaw exists because __ip_set_put_byindex() resolves a set index to a pointer under RCU but acquires ip_set_ref_lock only afterward to decrement the refcount, creating a window where ip_set_swap() can atomically reassign both the ip_set_list slot and the associated refcount before the lock is taken - causing the GC path to decrement a refcount that has already moved, hitting BUG_ON(set->ref == 0) and a fatal kernel panic. All Linux stable branches from 3.8 through pre-patch 5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.1, and 7.2 are affected; no public exploit has been identified at time of analysis.
Use-after-free in the Linux kernel netfilter flowtable (nf_flow_table_offload) arises from an ordering bug in how connection-tracking tuple nodes are published to the rhashtable. Because nf_flow_table_iterate() treats only the original-direction node as the owning entry, publishing it before the reply node lets the garbage collector observe and free a flow while flow_offload_add() is still inserting the reply node, producing slab-use-after-free reads and writes reachable through rht_deferred_worker, jhash, flow_offload_del and flow_offload_lookup. The flaw affects systems using software/hardware flow offload; no public exploit identified at time of analysis, though the CNA-assigned CVSS is 9.8.
Deadlock vulnerability in the Linux kernel's bnxt (Broadcom NetXtreme) ethernet driver causes kernel hangs or crashes on systems with Broadcom bnxt NICs when an IRQ affinity notifier callback and the bnxt work-cancellation path simultaneously contend for the netdev instance lock. The affinity notifier callback acquires the lock to restart the queue while cancellation synchronously waits for that callback to finish - both paths block indefinitely, resulting in full availability loss for the affected network interface and potentially the host. No public exploit code exists and the vulnerability is absent from CISA KEV; the assigned CVSS vector (AV:N/PR:N) is inconsistent with the described kernel-local race and should be treated with skepticism.
Indefinite TX queue stall in the Linux kernel veth driver allows a denial-of-service condition against multi-queue virtual Ethernet interfaces running GRO without an XDP program attached. The root cause is that veth_poll() incorrectly uses rq->xdp_rxq.queue_index to determine which peer TX queue to wake - a field that is zero-initialized and only populated when XDP is active - causing all NAPI instances to wake peer TX queue 0 instead of the correct queue. In a multi-queue veth setup, a stopped TX queue (e.g., queue 1 halted due to ptr_ring saturation) is never woken, producing an indefinite transmit stall with no watchdog recovery because veth implements no ndo_tx_timeout. No public exploit is identified at time of analysis; reproduction scripts are publicly available from the reporter.
Traffic Control BPF classifier (cls_bpf) in the Linux kernel fails to validate that a hardware-offloaded SCHED_CLS program's bound network device matches the target TC classifier device, allowing a local attacker with CAP_NET_ADMIN to attach a program loaded for device A to device B via skip_sw. When device A is subsequently removed, the kernel destroys the program's offload state while it remains live on device B, producing a use-after-free condition that triggers a kernel WARN or panic (guaranteed denial of service with panic_on_warn=1, with potential for privilege escalation via the memory corruption primitive). Patches are available across multiple stable kernel branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Credential exposure in Rently Smart Home versions 20.1.0 and prior allows authenticated network-based attackers to retrieve all property access PINs, including the Master Pin that overrides the standard user permission hierarchy. Reported by ICS-CERT via CISA advisory ICSA-26-237-01, the flaw is particularly severe in property rental contexts where Master Pin retrieval translates directly to unauthorized physical access to tenant properties. No public exploit code has been identified at time of analysis, but the low attack complexity and network-accessible vector make this a genuine operational and physical security risk.
Arbitrary file deletion in the Order Tip for WooCommerce WordPress plugin (versions before 1.6.0) allows authenticated Shop Managers to delete any file on the web server by exploiting missing capability checks and absent path restrictions on the deletion endpoint. The plugin fails to validate both the requesting user's permissions and the target file path, meaning a malicious or compromised Shop Manager account could remove critical WordPress files such as wp-config.php, leading to full site compromise. A publicly available proof-of-concept exists per WPScan; however, EPSS sits at only 0.17% (6th percentile) and CISA has not added this to KEV, consistent with the SSVC assessment of no observed exploitation.
Improper access control on the debug and engineering interfaces of Danfoss iC7-Automation SP, iC7-Marine, and iC7-Hybrid GR3 drive platforms lets attackers read and write internal device values and, more critically, upload and execute unsigned applications, EEPROM data, and firmware through exposed service and software-update mechanisms. Rated CVSS 4.0 9.3, the flaw effectively bypasses code-signing and grants full control over affected industrial drive controllers. There is no public exploit identified at time of analysis, but the missing authentication and firmware-overwrite capability make this a severe integrity and availability risk for operational technology environments.
Privilege boundary violation in FreeBSD's hwpmc(4) hardware performance monitoring subsystem allows a low-privileged local user to continue observing a process via attached PMCs after that process elevates privileges by executing a setuid or setgid binary, directly contrary to the kernel's intended security policy. Affected versions span FreeBSD 14.4-RELEASE before p9, 15.0-RELEASE before p13, and 15.1-RELEASE before p3; vendor patches are available per FreeBSD Security Advisory SA-26:56. No public exploit has been identified and EPSS sits at 0.15% (5th percentile), placing this as a low near-term exploitation priority despite the high vendor CVSS score.
Mailbox initialization in Trusted Firmware-M (TF-M) versions 2 through 2.3.0 on PSOC64 and RP2350 platforms fails to validate a pointer supplied by non-secure world code, allowing a low-privileged attacker with physical access to supply a crafted pointer that crosses the TrustZone-M hardware security boundary. Successful exploitation yields full read, write, and denial-of-service capability over the Secure Processing Environment (SPE), collapsing the hardware-enforced isolation TF-M is designed to guarantee - including potential exposure of cryptographic keys, attestation credentials, and secure boot state. No public exploit code exists and this vulnerability is absent from the CISA KEV catalog; the physical attack vector and high complexity substantially constrain opportunistic exploitation, but the full C/I/A scope change makes targeted supply-chain or insider-threat scenarios consequential.
Unauthenticated administrator account takeover affects the TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress in all versions through 3.3.1, where the 'trp_get_translations_regular' AJAX action returns raw translation-dictionary entries without access control. Because an administrator's password-reset URL can be persisted into the secondary-language dictionary as a translatable string, an unauthenticated attacker can read the plaintext reset key and login parameters and seize the admin account. Reported by Wordfence; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Cleartext exposure of LoRaWAN cryptographic session keys via NFC interface in dozens of Milesight IoT sensor and controller models allows any physically proximate unauthenticated attacker to retrieve ABP NwkSKey, AppSKey, and D2D keys through a commodity NFC read operation. The stolen keys enable full compromise of LoRaWAN communications for the affected device, including decryption of captured traffic, forgery of uplink and downlink frames with valid message integrity codes, injection of falsified sensor data, issuance of device commands, and disruption of legitimate frame processing. No public exploit has been identified at time of analysis, and this CVE is not listed in CISA KEV, but the attack itself requires no technical sophistication once physical proximity is achieved.
Cleartext exposure of LoRaWAN cryptographic session keys through the NFC interface of Milesight IoT sensor devices enables a physically proximate unauthenticated attacker to retrieve NwkSKey, AppSKey, and D2D keys from any affected device via a trivial NFC read operation. With these keys, an adversary can decrypt all ABP-mode LoRaWAN traffic for the compromised device, forge both uplink and downlink frames with valid session keys, inject falsified sensor readings into network servers, issue supported device commands, and cause legitimate frames to be rejected by consuming frame counters. No active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified at time of analysis, but the attack requires no credentials and succeeds in seconds with commodity NFC hardware against any physically accessible affected device.
Unauthenticated arbitrary file download in DocSys V2.02.80 exposes the entire server filesystem to remote attackers via the `downloadDocEx.do` endpoint. The `targetPath` parameter accepts arbitrary filesystem paths with no authentication gate, allowing any unauthenticated network attacker to retrieve sensitive files such as configuration files, credentials, or application data. No public exploit code has been identified at time of analysis, and EPSS at 0.17% (6th percentile) signals low current exploitation activity, though the attack is trivially simple to reproduce.
Kimai's Twig sandbox exposes server-wide secrets through an unrestricted config() function in administrator-uploaded invoice and export templates, affecting all versions before 2.56.0. An administrator with template upload privileges can craft a malicious template that renders sensitive configuration values - including LDAP bind passwords and SAML SP private keys - directly into invoice or export documents. Those documents are then delivered to lower-privileged users such as team leads who generate them, creating a stealthy credential exfiltration channel. No public exploit identified at time of analysis, and no CISA KEV listing is present in the provided data.
Unauthorized project report export in Kimai before 2.64.0 allows any authenticated user, regardless of role, to download the full project overview export via the unprotected `report_project_view_export` route, exposing customer names, project names, currency, budget type, and aggregate totals across all customers. The root cause is a misplaced authorization guard attached to the `__invoke` method on a sibling route rather than at the controller class level, leaving the export route with no access control. No public exploit code has been identified at time of analysis, but the vulnerability is trivially exploitable by any valid Kimai account holder.
Uncontrolled ZIP extraction in LeafWiki 0.10.0 through 0.12.0 allows any authenticated Editor or Admin to exhaust server disk or memory by uploading a crafted ZIP bomb via the import route. The vulnerable function ZipExtractor.ExtractToDir uses Go's io.Copy without a decompressed-size limit, so a maximally compressed archive well inside the 500 MiB upload cap can expand to hundreds of gigabytes on disk - or into RAM when the OS temporary directory is tmpfs-backed. No public exploit has been identified at time of analysis, though the attack is mechanically simple for any credentialed Editor.
DPoP proof replay attack in Spring Security's DPoPProofJwtDecoderFactory allows unauthenticated network attackers to bypass token binding protections by evicting cached JWT ID entries through request flooding, then replaying captured valid DPoP proofs to impersonate legitimate users. Affected versions span Spring Security 6.5.0-6.5.11, 7.0.0-7.0.6, and 7.1.0, impacting any Java application using Spring Security's DPoP-based OAuth 2.0 validation. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS C:H/I:H ratings reflect full token-holder impersonation upon successful exploitation.
Information disclosure in the Drupal Commerce Elavon payment-gateway module stems from improper input validation (CWE-20) and, per the NVD scoring, is reachable by remote unauthenticated attackers. The Drupal security advisory (SA-CONTRIB-2026-084) leaves the affected range wholly unspecified ('*.*'), so every published version should be treated as potentially vulnerable until a fixed release is identified. No public exploit identified at time of analysis, and the EPSS score sits in the 4th percentile, indicating little observed exploitation interest despite the headline 9.8 rating.
Observable timing discrepancy in the Drupal Token Content Access module exposes token-protected content to brute-force enumeration via side-channel analysis. All module versions from 0.0.0 through 3.1.2 are affected; unauthenticated remote attackers (PR:N, AV:N per CVSS) can measure differential response times during token validation to reconstruct valid access tokens character-by-character, ultimately bypassing content access restrictions. No active exploitation has been confirmed (SSVC exploitation: none, EPSS 0.14%, no KEV listing), and a vendor patch is available per Drupal SA-CONTRIB-2026-090.
Rewrite valve processing in Apache Tomcat contains an off-by-one error (CWE-193) in the handling of the [N] (Next) flag, causing rule iteration to restart from the second rewrite rule instead of the first, which can produce unintended looping behavior and result in a denial-of-service condition. Affected supported versions span Tomcat 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24; the EOL 8.5.x branch is also affected but will not receive a fix. No active exploitation is confirmed (not in CISA KEV), EPSS stands at 0.20% (10th percentile), and no public exploit code has been identified at time of analysis.
Improper input validation in Apache Tomcat 9.0.115-9.0.120, 10.1.53-10.1.57, and 11.0.20-11.0.24 stems from an incomplete fix for CVE-2026-32990 and, per its CVSS:3.1 vector, permits remote unauthenticated attackers to compromise confidentiality, integrity, and availability of the servlet container. Reported by the Apache security team, it carries a critical 9.8 base score, though vendor tagging labels the impact as Information Disclosure, which is narrower than the vector implies. No public exploit identified at time of analysis, and EPSS estimates exploitation probability at just 0.21% (11th percentile).
Apache Tomcat's Unix domain socket creation path exposes a TOCTOU race condition across versions 9.0.42-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, enabling an unauthorized local OS user to seize the socket before Tomcat finalizes access permissions. The vendor-assigned CVSS 8.1 with AV:N directly conflicts with the description's explicit 'local user' constraint and the inherently host-local nature of Unix domain sockets - the effective attack surface is limited to users with OS-level access on Tomcat hosts. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% (5th percentile), indicating negligible real-world exploitation pressure at time of analysis.
Arbitrary local file read in self-hosted Typebot prior to 3.18.0 allows any registered user to exfiltrate files readable by the server process - including environment variable secrets, credential encryption keys, and database connection strings - by publishing a chatbot whose Send Email block specifies an absolute filesystem path such as /etc/passwd or /proc/self/environ as an attachment. The root cause is a missing URL-scheme validation in the parseAttachments helper: any value not prefixed with the application's own base URL is passed directly to Nodemailer as a filesystem path, and the Nodemailer transport is instantiated without disableFileAccess, so it reads and emails the file to an attacker-controlled recipient. No public exploit has been identified at time of analysis, but the attack requires no special server configuration because open signup and system SMTP are both enabled by default.
TOTP second-factor brute-force protection in Punk::Plugin::TOTP before 0.05 for Perl is defeated by replaying a saved session cookie, allowing an attacker with valid first-factor credentials to reset the TOTP failure counter indefinitely. Because Punk::Session stores the entire session state - including the TOTP attempt counter - in a client-side signed cookie when no server-side store is configured, an attacker can save the cookie before failures accumulate and replay it to restore a fresh counter, cycling this indefinitely within the pending_ttl window. No public exploit has been identified at time of analysis, but the technique is trivially reproducible from the advisory description alone.
Two-factor authentication bypass in the Perl module Punk::Plugin::TOTP before 0.05 lets an attacker who already knows a victim's password clear the victim's TOTP challenge using a recovery code issued to the attacker's own account. The flaw stems from the recovery-code helper looking up codes by digest across all users and then binding ownership through a numeric comparison of user identifiers, which fails whenever accounts are keyed by username, email, or UUID. No CISA KEV listing and no public exploit identified at time of analysis, with a low EPSS score of 0.44% (37th percentile) despite the 9.8 CVSS rating.
Privilege escalation via symlink attack in SonicWall NetExtender Linux client (versions 10.3.5 and earlier) stems from the NEService auto-upgrade component insecurely handling temporary files, enabling a local low-privileged attacker to manipulate file paths and potentially overwrite or read privileged system files. The CVSS vector confirms full confidentiality, integrity, and availability impact despite requiring local access with high attack complexity. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, though SSVC classifies the technical impact as total.
Out-of-bounds read in OpenEXRUtil's SampleCountChannel::row() API allows an attacker to crash applications or leak adjacent heap memory by supplying a crafted deep EXR file with a non-zero dataWindow origin. Affected are OpenEXR releases through 3.2.10, 3.3.0-3.3.12, and 3.4.0-3.4.13 - the complete release history prior to the coordinated January 2026 patch. The CVSS vector (AV:N/AC:L/PR:N/UI:R) reflects that exploitation requires no authentication but does require a user or automated pipeline to open an attacker-controlled file; no public exploit code and no CISA KEV listing exist at time of analysis.
Unauthenticated access to the NVIDIA NemoClaw inference server on Linux exposes sensitive model inference data and enables denial of service by adjacent network attackers. The flaw stems from a missing authentication check (CWE-306) on the inference service endpoint, meaning any host on the same network segment can interact with the service without credentials. No active exploitation has been confirmed by CISA KEV and no public exploit code is known at time of analysis, but the low attack complexity and absence of authentication barriers make this straightforward to exploit for any attacker with adjacent network positioning.
Improper certificate validation in NVIDIA NemoClaw for Linux (versions up to and including 0.0.1) allows network attackers to intercept or manipulate the deployment process, potentially yielding information disclosure, data tampering, remote code execution, and privilege escalation. The flaw stems from the deployment routine failing to properly verify TLS certificates (CWE-295), enabling machine-in-the-middle attacks. No public exploit is identified at time of analysis and it is not listed in CISA KEV, but the vendor rates full technical impact.
Privilege escalation and remote code execution in NVIDIA OpenShell for Linux stem from an incomplete deny-list in its sandbox provisioning API, letting an authenticated attacker submit inputs that were meant to be blocked but were not. Because the flaw crosses the sandbox boundary (CVSS scope change), a successful exploit can yield code execution, privilege escalation, information disclosure, data tampering, and denial of service against the host. No public exploit identified at time of analysis, and the issue is not in CISA KEV.
Code injection in NVIDIA NemoClaw's migration command (Linux, versions up to 0.0.17) allows a local attacker with low-privilege access to inject and execute arbitrary code within the process context, yielding full confidentiality, integrity, and availability impact on the vulnerable system. SSVC rates technical impact as total, consistent with the CVSS 7.8 rating, though EPSS remains very low at 0.16% (5th percentile) and no active exploitation has been observed. No public exploit has been identified at time of analysis.
Untrusted code execution in NVIDIA NemoClaw for Linux (versions up to and including 0.0.21) stems from the installer executing code without verifying its integrity, letting an attacker who can supply or interpose malicious code during installation achieve arbitrary code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA assigns a CVSS of 9.8 with a fully network-based, no-privilege, no-interaction vector, though the flaw is rooted in the install process. There is no public exploit identified at time of analysis, EPSS is low at 0.25% (17th percentile), and CISA SSVC records no known exploitation.
OS command injection in NVIDIA NemoClaw for Linux allows a local low-privileged attacker to execute arbitrary operating system commands through the application's status and logs plugin command interfaces. The CVSS 7.8 score reflects high impact across confidentiality, integrity, and availability with low attack complexity and no user interaction required. No public exploit identified at time of analysis, and no CISA KEV listing observed, but the fully unscopeed local impact makes this a meaningful risk on multi-tenant or shared Linux systems running NemoClaw.
OS command injection in NVIDIA NemoClaw's NIM management component on Linux enables a local authenticated attacker to execute arbitrary operating system commands with the privileges of the targeted process. All versions of NemoClaw are indicated as affected per NVD CPE data (wildcard version range). Successful exploitation can result in full code execution, persistent data tampering, sensitive information disclosure, and denial of service on the host. No public exploit code or CISA KEV listing has been identified at time of analysis.
OS command injection in NVIDIA NemoClaw's command-line interface on Linux enables a local low-privileged attacker to execute arbitrary operating system commands, leading to full compromise of confidentiality, integrity, and availability. All versions of NemoClaw appear affected per the CPE wildcard (*), and the vulnerability is rooted in improper neutralization of user-supplied input passed to shell commands (CWE-78). No public exploit code and no CISA KEV listing have been identified at time of analysis, limiting current real-world risk primarily to environments with untrusted local users.
Weak authentication in NVIDIA NemoClaw for Linux (versions 0 through 0.0.4) lets remote attackers bypass the authentication enforced by its remote-access helper workflow, enabling code execution, information disclosure, and data tampering on the host. The flaw was self-reported by NVIDIA and carries a critical 9.8 CVSS rating with a fully unauthenticated network vector. No public exploit identified at time of analysis, and EPSS estimates only a 0.57% 30-day exploitation probability, so the raw severity outpaces observed real-world activity.
Unverified code download in NVIDIA NemoClaw installation scripts for Linux (versions 0.0.0 through 0.0.21) allows a network-positioned attacker to substitute malicious payloads during installation, enabling code execution, privilege escalation, information disclosure, and data tampering on the target host. The root cause is CWE-494: the installation pipeline fetches remote code without cryptographic integrity verification, leaving the download channel open to man-in-the-middle substitution or upstream server compromise. No public exploit has been identified at time of analysis; EPSS sits at 0.20% (9th percentile) and SSVC confirms Exploitation: none, placing this firmly in the theoretical high-severity category rather than an actively exploited threat.
OS command injection in NVIDIA NemoClaw's Telegram bridge component on Linux enables a local attacker with low-privileged access to execute arbitrary operating system commands. Exploitation yields full confidentiality, integrity, and availability compromise on the affected host, with potential for privilege escalation beyond the invoking user. No active exploitation is confirmed in CISA KEV and no public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) and minimal privilege requirement (PR:L) lower the practical bar for exploitation once local access is obtained.
Sandbox escape in NVIDIA OpenShell for Linux lets a low-privileged actor already operating inside the sandbox break its isolation boundary, potentially achieving code execution, privilege escalation, data tampering, and information disclosure on the host. The flaw is rooted in an uncontrolled search path element (CWE-427), so a resource the sandbox loads can be redirected to attacker-supplied code. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the assigned 9.9 CVSS reflects the full compromise achievable once the sandbox boundary is breached.
Path traversal in NVIDIA OpenShell Sandbox for Linux permits low-privileged network-authenticated attackers to bypass L7 REST network policy enforcement, reaching REST endpoints that policy rules were designed to block. The Changed Scope (S:C) in the CVSS vector signals that the real impact falls on downstream services or data stores protected by the bypassed policy, yielding high confidentiality exposure (C:H) and limited integrity impact (I:L) on resources outside the sandbox trust boundary. No active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified at time of analysis.
OS command injection in NVIDIA OpenShell across all supported platforms allows a network-accessible malicious gateway to execute arbitrary operating system commands on a victim host when a user interacts with that gateway. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) reflects that an attacker requires no privileges on the victim system but does require the victim to interact with a malicious or attacker-controlled gateway endpoint. Successful exploitation yields full code execution, data tampering, and information disclosure - with no public exploit or CISA KEV listing identified at time of analysis.
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Improper state validation in Google Chrome's Performance component (all versions prior to 152.0.7977.65) enables remote attackers to read memory contents within the Chrome sandbox by luring a user to a crafted HTML page. The scope is contained to the sandbox (S:U), limiting blast radius to in-process data, but sensitive browser state such as cookies, session tokens, or page content may be exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS of 0.22% (13th percentile) corroborates low observed exploitation activity.
Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).
DNS rebinding in genieacs-mcp's Streamable HTTP transport (versions <= 0.3.1) allows a malicious website to route browser requests through loopback to the unauthenticated /mcp listener and invoke arbitrary GenieACS NBI operations against managed CPE devices. Affected deployments expose full read/write access to TR-069 device state - including firmware update tasks, parameter changes, device reboots, presets, and connection requests - to any attacker who can lure the server operator to a malicious web page. A proof-of-concept is documented in the GitHub security advisory (GHSA-cmwv-wf9p-p8wx); no CISA KEV listing is present, indicating targeted rather than widespread exploitation at time of analysis.
Out-of-bounds pointer arithmetic in OpenEXR's TypedDeepImageChannel::row() - and parallel methods in FlatImageChannel and SampleCountChannel - affects all releases before 3.2.11, 3.3.13, and 3.4.14, exposing applications that process deep EXR files with nonzero dataWindow origins to deterministic crash or limited heap memory disclosure. The CVSS 7.1 score (AV:N/AC:L/PR:N/UI:R) reflects unauthenticated, low-complexity delivery of a crafted image file requiring only that a user or pipeline opens it, with high availability impact and limited confidentiality exposure. No CISA KEV listing and no public exploit code have been identified at time of analysis; patched releases are available from the Academy Software Foundation.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a victim opens a specially crafted VI (Virtual Instrument) file. The root cause is CWE-787 (Out-of-bounds Write), indicating a write operation beyond the bounds of an allocated buffer during VI file parsing. No public exploit code or active exploitation has been identified at time of analysis, but the file-borne delivery model is realistic in engineering and research environments where LabVIEW projects are routinely shared.
Heap out-of-bounds read in OpenEXRUtil's deep and flat image channel row() API allows an attacker supplying a crafted EXR file with a non-zero dataWindow origin to crash any application that processes the file, with conditional heap memory disclosure dependent on attacker-controlled heap layout. Affected are OpenEXRUtil versions 3.3.0-3.3.12 and 3.4.0-3.4.12; the flaw exists across three channel header implementations (ImfDeepImageChannel.h, ImfFlatImageChannel.h, ImfSampleCountChannel.h). No public exploit identified at time of analysis, and patched releases 3.3.13 and 3.4.13 are available.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The root cause is an out-of-bounds read (CWE-125) that, combined with tags indicating buffer overflow behavior, can corrupt memory state sufficient to achieve code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.5 reflects the high impact potential once a victim opens a malicious VI file.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Rooted in CWE-125 (Out-of-bounds Read), the parser reads beyond allocated buffer boundaries, which can expose adjacent memory or - under favorable heap conditions - enable full code execution. No public exploit or CISA KEV listing has been identified at time of analysis, though the RCE potential and broad LabVIEW user base warrant prioritized patching.
Memory corruption in NI LabVIEW (all versions through 26.3.0) enables information disclosure or arbitrary code execution when a user opens a specially crafted VI (Virtual Instrument) file. The CVSS 4.0 base score of 8.5 reflects high impact across confidentiality, integrity, and availability on the vulnerable system, with local file-based delivery requiring passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE potential and industrial control / engineering deployment context warrant prompt patching.
Memory corruption in NI LabVIEW 26.3.0 and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Classified under CWE-125 (Out-of-bounds Read), the flaw's buffer-overflow and RCE tags suggest that the out-of-bounds read condition can, under certain memory layout circumstances, corrupt control-flow data and escalate beyond information disclosure to full code execution. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis; NI has published a vendor security advisory.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The CWE-787 out-of-bounds write root cause combined with the high-impact CVSS 4.0 score of 8.5 places this in a serious tier for LabVIEW deployments across engineering, scientific, and industrial automation environments. No public exploit code has been identified at time of analysis, but the user-interaction trigger (social engineering via malicious VI file) is a well-understood threat model for desktop engineering tools.