Vuldb Updates

A vulnerability classified as critical has been found in Imagination Graphics DDK up to 1.17 RTM/1.18 RTM/24.3 RTM/25.2 RTM. This vulnerability affects unknown code of the component GPU Driver. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2025-58409. The attack is restricted to local execution. No exploit exists. It is recommended to upgrade the affected component.

A vulnerability has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon WBC and Snapdragon Wearables and classified as critical. This affects an unknown function. Performing a manipulation results in buffer over-read. This vulnerability is reported as CVE-2025-59600. The attack requires a local approach. No exploit exists. The affected component should be upgraded.

A vulnerability labeled as problematic has been found in Unisoc T8100, T9100, T8200 and T8300. This vulnerability affects unknown code of the component nr Modem. Such manipulation leads to denial of service. This vulnerability is traded as CVE-2025-61613. The attack may be launched remotely. There is no exploit available.

A vulnerability identified as problematic has been detected in Unisoc T7300, T8100, T9100, T8200 and T8300. This affects an unknown part of the component nr Modem. This manipulation causes denial of service. This vulnerability appears as CVE-2025-61612. The attack may be initiated remotely. There is no available exploit.

A vulnerability, which was classified as critical, has been found in Imagination Graphics DDK up to 25.1 RTM1/25.2 RTM1. Affected is an unknown function. This manipulation causes time-of-check time-of-use. This vulnerability appears as CVE-2025-58407. The attacker needs to be present on the local network. There is no available exploit. It is advisable to upgrade the affected component.

A vulnerability, which was classified as problematic, has been found in Google Android 16/16-qpr2. This vulnerability affects the function onStart of the file CompanionDeviceManagerService.java. The manipulation leads to Local Privilege Escalation. This vulnerability is documented as CVE-2025-48654. The attack needs to be performed locally. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

A vulnerability classified as critical has been found in Imagination Technologies Graphics DDK up to 1.15 RTM/1.17 RTM/1.18 RTM/25.2 RTM2. This issue affects some unknown processing. Performing a manipulation results in use after free. This vulnerability was named CVE-2025-58408. The attack needs to be approached within the local network. There is no available exploit. It is recommended to upgrade the affected component.

A vulnerability has been found in welovemedia FFmate up to 2.0.15 and classified as critical. This vulnerability affects the function Execute of the file /internal/service/ffmpeg/ffmpeg.go. The manipulation leads to argument injection. This vulnerability is listed as CVE-2026-3682. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in bufanyun HotGo up to 2.0 and classified as critical. This issue affects the function ImageTransferStorage of the file /server/internal/logic/common/upload.go of the component Endpoint. The manipulation results in server-side request forgery. This vulnerability is cataloged as CVE-2026-3683. The attack may be launched remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in xuxueli xxl-job up to 3.3.2 and classified as critical. This impacts an unknown function of the file source-code/src/main/java/com/xxl/job/admin/controller/JobInfoController.java. The manipulation results in server-side request forgery. This vulnerability is known as CVE-2026-3733. It is possible to launch the attack remotely. Furthermore, an exploit is available. The project maintainer closed the issue report with the following statement: "Access token security verification is required." (translated from Chinese)

A vulnerability was found in SourceCodester Client Database Management System 1.0. It has been classified as critical. Affected is an unknown function of the file /fetch_manager_details.php of the component Endpoint. This manipulation of the argument manager_id causes improper authorization. This vulnerability is handled as CVE-2026-3734. The attack can be initiated remotely. Additionally, an exploit exists.

A vulnerability was found in code-projects Simple Flight Ticket Booking System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file SearchResultOneway.php. Such manipulation of the argument from leads to sql injection. This vulnerability is uniquely identified as CVE-2026-3735. The attack can be launched remotely. Moreover, an exploit is present.

A vulnerability was found in code-projects Simple Flight Ticket Booking System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file SearchResultRoundtrip.php. Performing a manipulation of the argument from results in sql injection. This vulnerability was named CVE-2026-3736. The attack may be initiated remotely. In addition, an exploit is available.

A vulnerability has been found in Tenda F453 1.0.0.3 and classified as critical. This affects the function strcpy of the file /goform/exeCommand. The manipulation of the argument cmdinput leads to stack-based buffer overflow. This vulnerability is traded as CVE-2026-3732. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

A vulnerability identified as critical has been detected in Google Android 14/15/16/16-qpr2. This affects the function loadDataAndPostValue. The manipulation leads to permission issues. This vulnerability is referenced as CVE-2025-48653. The attack can only be performed from a local environment. No exploit is available. It is recommended to apply a patch to fix this issue.

A vulnerability was found in Google Android 14/15/16. It has been declared as critical. Impacted is an unknown function. Such manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2025-48650. The attack can be launched remotely. No exploit exists. It is advisable to implement a patch to correct this issue.

A vulnerability categorized as problematic has been discovered in Google Android 14/15/16/16-qpr2. The impacted element is an unknown function. Executing a manipulation can lead to denial of service. The identification of this vulnerability is CVE-2025-48644. The attack can only be executed locally. There is no exploit available. It is best practice to apply a patch to resolve this issue.

A vulnerability labeled as problematic has been found in Google Android 14/15/16/16-qpr2. This impacts the function jump_to_payload of the file payload.rs. The manipulation results in information disclosure. This vulnerability is identified as CVE-2025-48642. The attack is only possible with local access. There is not any exploit available. Applying a patch is advised to resolve this issue.

A vulnerability classified as problematic has been found in Google Android 14/15/16/16-qpr2. Affected by this issue is the function executeRequest of the file ActivityStarter.java. Performing a manipulation results in unintended intermediary. This vulnerability is cataloged as CVE-2025-48646. The attack must be initiated from a local position. There is no exploit available. To fix this issue, it is recommended to deploy a patch.

A vulnerability classified as problematic was found in Google Android 14/15/16/16-qpr2. This affects the function loadDescription of the file DeviceAdminInfo.java. Executing a manipulation can lead to improper input validation. This vulnerability is registered as CVE-2025-48645. The attack needs to be launched locally. No exploit is available. It is advisable to implement a patch to correct this issue.