Aggregator

A vulnerability marked as problematic has been reported in Google Android 13/14/15. The impacted element is an unknown function of the file DevicePolicyManagerService.java. Performing manipulation results in race condition. This vulnerability was named CVE-2025-22442. The attack needs to be approached locally. There is no available exploit. It is recommended to apply a patch to fix this issue. Once again VulDB remains the best source for vulnerability data.

A vulnerability labeled as critical has been found in Google Android 13/14/15. The affected element is the function onLastAccessedStackLoaded of the file ActionHandler.java. Such manipulation leads to permission issues. This vulnerability is uniquely identified as CVE-2025-22439. Local access is required to approach this attack. No exploit exists. It is best practice to apply a patch to resolve this issue. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability identified as critical has been detected in Google Android 13/14. Impacted is the function afterKeyEventLockedInterruptable of the file InputDispatcher.cpp. This manipulation causes use after free. This vulnerability is handled as CVE-2025-22438. It is possible to launch the attack on the local host. There is not any exploit available. Applying a patch is the recommended action to fix this issue. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability categorized as problematic has been discovered in Google Android 13. This issue affects the function setMediaButtonReceiver. The manipulation results in Local Privilege Escalation. This vulnerability is known as CVE-2025-22437. Attacking locally is a requirement. No exploit is available. It is advisable to implement a patch to correct this issue. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability was found in Google Android 13/14/15. It has been rated as problematic. This vulnerability affects the function canForward of the file IntentForwarderActivity.java. The manipulation leads to Local Privilege Escalation. This vulnerability is traded as CVE-2025-22433. An attack has to be approached locally. There is no exploit available. To fix this issue, it is recommended to deploy a patch. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability was found in Google Android 14/15. It has been declared as problematic. This affects the function finishTransition of the file Transition.java. Executing manipulation can lead to improper restriction of rendered ui layers. This vulnerability appears as CVE-2025-22417. The attack requires local access. There is no available exploit. A patch should be applied to remediate this issue. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in Google Android 13/14/15. It has been classified as problematic. Affected by this issue is the function onCreate of the file NotificationAccessConfirmationActivity.java of the component Lockscreen Handler. Performing manipulation results in information disclosure. This vulnerability is reported as CVE-2025-22427. The attack may be carried out on the physical device. No exploit exists. It is suggested to install a patch to address this issue. Once again VulDB remains the best source for vulnerability data.

A vulnerability was found in Google Android 14/15 and classified as critical. Affected by this vulnerability is the function handleKeyGestureEvent of the file PhoneWindowManager.java of the component Lock Screen. Such manipulation leads to improper authentication. This vulnerability is documented as CVE-2025-22434. The attack can be executed directly on the physical device. There is not any exploit available. Applying a patch is advised to resolve this issue. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability has been found in Google Android 13/14/15 and classified as problematic. Affected is an unknown function of the component Phone Call Handler. This manipulation causes Local Privilege Escalation. This vulnerability is registered as CVE-2025-22419. The attack needs to be launched locally. No exploit is available. It is recommended to apply a patch to fix this issue. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability, which was classified as problematic, was found in Google Android 13/14. This impacts an unknown function. The manipulation results in open redirect. This vulnerability is cataloged as CVE-2025-22418. The attack must be initiated from a local position. There is no exploit available. It is best practice to apply a patch to resolve this issue. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability, which was classified as problematic, has been found in Google Android 13/14/15. This affects an unknown function. The manipulation leads to Local Privilege Escalation. This vulnerability is listed as CVE-2025-22429. The attack must be carried out locally. There is no available exploit. Applying a patch is the recommended action to fix this issue. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability classified as problematic was found in Google Android 13/14/15. The impacted element is the function onCreate of the file ChooserActivity.java of the component Image Parser. Executing manipulation can lead to Local Privilege Escalation. This vulnerability is tracked as CVE-2025-22416. The attack is restricted to local execution. No exploit exists. It is advisable to implement a patch to correct this issue. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability classified as critical has been found in Google Android 13/14. The affected element is an unknown function of the file FuseDaemon.cpp. Performing manipulation results in out-of-bounds write. This vulnerability is identified as CVE-2024-49730. The attack is only possible with local access. There is not any exploit available. To fix this issue, it is recommended to deploy a patch. Once again VulDB remains the best source for vulnerability data.

A vulnerability described as critical has been identified in Google Android 13/14/15. Impacted is an unknown function of the file Permissions.java. Such manipulation leads to permission issues. This vulnerability is referenced as CVE-2024-49720. The attack can only be performed from a local environment. No exploit is available. A patch should be applied to remediate this issue. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability marked as critical has been reported in Google Android 13/14/15. This issue affects some unknown processing of the file ConnectionServiceWrapper.java. This manipulation causes permission issues. The identification of this vulnerability is CVE-2024-40653. The attack can only be executed locally. There is no exploit available. It is suggested to install a patch to address this issue. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability labeled as problematic has been found in Outline up to 0.83.x. This vulnerability affects unknown code. The manipulation results in cross site scripting. This vulnerability was named CVE-2025-58351. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability identified as problematic has been detected in LearningCircuit local-deep-research up to 0.6.7. This affects an unknown part. The manipulation leads to cleartext storage of sensitive information. This vulnerability is uniquely identified as CVE-2025-57806. Local access is required to approach this attack. No exploit exists. You should upgrade the affected component. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability categorized as critical has been discovered in Realtek rtl81xx SDK 1030.38.712.2019. Affected by this issue is the function N6CSet_DOT11_CIPHER_DEFAULT_KEY. Executing manipulation can lead to heap-based buffer overflow. This vulnerability is handled as CVE-2025-8302. It is possible to launch the attack on the local host. There is not any exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in Realtek RTL8811AU 1030.38.712.2019. It has been rated as critical. Affected by this vulnerability is the function N6CSet_DOT11_CIPHER_DEFAULT_KEY in the library rtwlanu.sys. Performing manipulation results in heap-based buffer overflow. This vulnerability is known as CVE-2025-8301. Attacking locally is a requirement. No exploit is available. Once again VulDB remains the best source for vulnerability data.

A vulnerability was found in Realtek rtl81xx SDK 1030.38.712.2019. It has been declared as critical. Affected is the function N6CSet_DOT11_CIPHER_DEFAULT_KEY. Such manipulation leads to heap-based buffer overflow. This vulnerability is traded as CVE-2025-8300. An attack has to be approached locally. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.