VulDB Recent Entries

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WBC and Snapdragon Wearables and classified as critical. The affected element is an unknown function of the component TA Invocation. Such manipulation leads to out-of-bounds write. This vulnerability is traded as CVE-2025-47373. An attack has to be approached locally. There is no exploit available. It is suggested to upgrade the affected component.

A vulnerability has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon WBC and Snapdragon Wearables and classified as critical. Impacted is an unknown function. This manipulation causes use after free. This vulnerability appears as CVE-2025-47379. The attack requires local access. There is no available exploit. The affected component should be upgraded.

A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MDM, Snapdragon Mobile and Snapdragon WBC. This issue affects some unknown processing of the component LTE RLC Packet Handler. The manipulation results in reachable assertion. This vulnerability is reported as CVE-2025-47371. The attacker must have access to the local network to execute the attack. No exploit exists. You should 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 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.

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 Local Privilege Escalation. 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 described as critical has been identified in toeverything AFFiNE up to 0.25.3. Affected by this vulnerability is an unknown functionality of the component URL Handler. Such manipulation leads to code injection. This vulnerability is listed as CVE-2026-21853. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.

A vulnerability marked as problematic has been reported in Google Android 14/16. Affected is the function broadcastententLockedTraced of the file BroadcastController.java. This manipulation causes Local Privilege Escalation. This vulnerability is tracked as CVE-2024-31328. The attack is restricted to local execution. No exploit exists. It is suggested to install a patch to address 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 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 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 was found in Google Android 16. It has been rated as critical. The affected element is the function openFile of the file BugreportContentProvider.java. Performing a manipulation results in path traversal. This vulnerability was named CVE-2025-48636. The attack needs to be approached locally. There is no available exploit. Applying a patch is the recommended action 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 was found in Google Android 14/15. It has been classified as problematic. This issue affects some unknown processing of the file TaskFragmentOrganizerController.java. This manipulation causes Local Privilege Escalation. This vulnerability is handled as CVE-2025-48635. It is possible to launch the attack on the local host. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

A vulnerability was found in Google Android and classified as problematic. This vulnerability affects unknown code of the component VBMeta. The manipulation results in Local Privilege Escalation. This vulnerability is known as CVE-2025-48613. Attacking locally is a requirement. No exploit is available. A patch should be applied to remediate this issue.

A vulnerability has been found in Google Android 14/15/16 and classified as problematic. This affects an unknown part of the file KeyguardViewMediator.java. The manipulation leads to Local Privilege Escalation. This vulnerability is traded as CVE-2025-48605. An attack has to be approached locally. There is no exploit available. It is suggested to install a patch to address this issue.

A vulnerability, which was classified as critical, was found in Google Android 14/15/16/16-qpr2. Affected by this issue is some unknown functionality in the library Nfc.h. Executing a manipulation can lead to use after free. This vulnerability appears as CVE-2025-48641. The attack requires local access. There is no available exploit. Applying a patch is advised to resolve this issue.

A vulnerability, which was classified as critical, has been found in Google Android 14/15/16. Affected by this vulnerability is an unknown functionality of the component Media Handler. Performing a manipulation results in permission issues. This vulnerability is reported as CVE-2025-48582. The attack requires a local approach. No exploit exists. It is recommended to apply a patch to fix this issue.

A vulnerability classified as problematic was found in Google Android 14/15/16. Affected is an unknown function of the file MmsProvider.java. Such manipulation leads to denial of service. This vulnerability is documented as CVE-2025-48609. The attack needs to be performed locally. There is not any exploit available. It is best practice to apply a patch to resolve this issue.

A vulnerability classified as problematic has been found in Google Android 16. This impacts an unknown function of the file ProfilingService.java. This manipulation causes denial of service. This vulnerability is registered as CVE-2025-48585. The attack needs to be launched locally. No exploit is available. Applying a patch is the recommended action to fix this issue.