2958 matches found
CVE-2026-14551 Local Privilege Escalation in servereye client (sensorhub)
The servereye client also known as sensorhub, technically ClientAgentContainerService versions 20.15 and earlier are vulnerable to Local Privilege Escalation. The high-privileged service SE3Recovery EmergencyRecoveryService.exe, running as SYSTEM, periodically monitors the directory...
EUVD-2026-47622
The servereye client also known as sensorhub, technically ClientAgentContainerService versions 20.15 and earlier are vulnerable to Local Privilege Escalation. The high-privileged service SE3Recovery EmergencyRecoveryService.exe, running as SYSTEM, periodically monitors the directory...
CVE-2026-14551
The servereye client also known as sensorhub, technically ClientAgentContainerService versions 20.15 and earlier are vulnerable to Local Privilege Escalation. The high-privileged service SE3Recovery EmergencyRecoveryService.exe, running as SYSTEM, periodically monitors the directory...
CVE-2026-14551
CVE-2026-14551 affects the servereye client (sensorhub), version 20.15 and earlier. A local privilege escalation occurs via the SE3Recovery service (EmergencyRecoveryService.exe), which runs as SYSTEM and periodically watches %ProgramData%\ServerEye3\update\ for a trigger file named update_availa...
PT-2026-63334
The servereye client also known as sensorhub, technically ClientAgentContainerService versions 20.15 and earlier are vulnerable to Local Privilege Escalation. The high-privileged service SE3Recovery EmergencyRecoveryService.exe, running as SYSTEM, periodically monitors the directory...
CVE-2026-15792
A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic...
SUSE CVE-2026-63965
In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...
SUSE CVE-2026-63966
In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...
CVE-2026-63966
A flaw was found in the Linux kernel's adis16550 Industrial Input/Output IIO Inertial Measurement Unit IMU driver. The adis16550triggerhandler function fails to fully initialize a stack-allocated data array. This oversight allows uninitialized stack memory to be exposed to userspace, leading to...
CVE-2026-13694
The Bit Form WordPress plugin before 3.1.0 does not properly validate its workflow-trigger token once the associated transient has expired, allowing unauthenticated attackers to re-trigger a form's configured workflow actions such as notification emails and integrations...
CVE-2026-13694 Bit Form < 3.1.0 - Unauthenticated Workflow Trigger via Authentication Bypass
The Bit Form WordPress plugin before 3.1.0 does not properly validate its workflow-trigger token once the associated transient has expired, allowing unauthenticated attackers to re-trigger a form's configured workflow actions such as notification emails and integrations...
CVE-2026-13694
CVE-2026-13694 affects the Bit Form WordPress plugin prior to 3.1.0. The root cause is improper validation of the workflow-trigger token after its transient expires, enabling unauthenticated attackers to re-trigger configured workflow actions (e.g., notification emails and integrations). Document...
CVE-2026-57852
Grav CMS scheduler-webhook plugin contains an authentication bypass vulnerability that allows unauthenticated remote attackers to trigger configured scheduled jobs by exploiting a short-circuit logic flaw in the webhook token validation. Attackers can send a single unauthenticated POST request to...
CVE-2026-57852 Authentication Bypass via Null Short-Circuit in Grav CMS Scheduler Webhook Token Check
Grav CMS scheduler-webhook plugin contains an authentication bypass vulnerability that allows unauthenticated remote attackers to trigger configured scheduled jobs by exploiting a short-circuit logic flaw in the webhook token validation. Attackers can send a single unauthenticated POST request to...
Linux Distros Unpatched Vulnerability : CVE-2026-63966
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the...
PT-2026-61740
Name of the Vulnerable Software and Affected Versions Grav CMS scheduler-webhook plugin affected versions not specified Description An authentication bypass exists in the scheduler-webhook plugin due to a short-circuit logic flaw during webhook token validation. This allows unauthenticated remote...
CVE-2026-63965
In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...
CVE-2026-63966
In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...
CVE-2026-63966
In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...
CVE-2026-63966
The CVE-2026-63966 issue affects the Linux kernel IIO imu driver for adis16550. The trigger handler allocates a scan data array on the stack but does not initialize it. A memcpy fills only the first 28 bytes (TEMP + 6 channels of GYRO/ACCEL), while a timestamp is written at offset 32, leaving byt...