CVE-2026-95180 in agentweb-core
Summary
by MITRE • 10/15/2026
An issue in Justson agentweb-core v5.1.6-androidx and earlier allows a local attacker to obtain sensitive information and launch non-exported host application components via incorrect access control in the handling of intent:// URLS in DefaultWebClient
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 10/15/2026
The vulnerability identified in Justson AgentWeb-Core versions 5.1.6-androidx and prior releases stems from an improper implementation of access controls within the DefaultWebClient component, specifically regarding the processing of intent:// URLs. This flaw allows a local attacker to exploit weaknesses in how Android intents are handled by the web view engine embedded within the application. The core issue lies in the failure to adequately validate or restrict the scope of actions that can be triggered through these specific URL schemes when loaded from untrusted sources, such as malicious websites accessed via the browser component.
From a technical perspective, intent:// URLs provide a mechanism for applications on Android devices to interact with other installed apps by launching intents. While this is a standard feature for deep linking and app-to-app communication, it introduces significant security risks if not properly sandboxed or restricted within a web view context. In the affected versions of AgentWeb-Core, the DefaultWebClient does not sufficiently enforce access control policies when parsing these URLs. This oversight permits an attacker who has local execution capabilities to craft malicious intent payloads that bypass expected restrictions. By leveraging this flaw, the attacker can manipulate the application into launching components or accessing resources that were intended to remain private and non-exported by the host application developer.
The operational impact of this vulnerability is twofold, involving both information disclosure and unauthorized component invocation. First, the incorrect access control allows for the extraction of sensitive information stored within the host application's internal state or protected storage areas. Because the attacker can trigger actions that interact with these protected resources without proper authorization checks, confidential data such as user credentials, session tokens, or personal identifiable information may be exfiltrated to an external location controlled by the attacker. Second, and potentially more critical, is the ability to launch non-exported host application components. In Android architecture, activities, services, and broadcast receivers marked as not exported are designed to be accessible only within their own application package for security reasons. By exploiting this vulnerability, a local attacker can circumvent these boundaries, effectively breaking the app sandbox and gaining elevated privileges or performing actions on behalf of the user without explicit consent.
This type of flaw is categorized under CWE-284, which describes Improper Access Control, as it involves failing to restrict access to resources based on identity or privilege levels. Furthermore, from a threat modeling perspective aligned with the MITRE ATT&CK framework for mobile platforms, this vulnerability facilitates techniques related to Privilege Escalation and Defense Evasion. The attacker uses the web view's functionality to bypass security constraints, effectively moving laterally within the device ecosystem by leveraging trusted application components that were not intended for external interaction. This can serve as a stepping stone for further exploitation, such as installing malware or maintaining persistent access on the compromised device.
To mitigate this vulnerability, developers must upgrade to version 5.1.7-androidx of AgentWeb-Core or later, where these access control issues have been addressed in the DefaultWebClient implementation. For applications that cannot immediately update their dependencies, a temporary mitigation involves implementing custom URL interception logic within the web view client. This includes strictly validating all intent:// URLs before they are processed, ensuring that only whitelisted schemes and actions are permitted. Additionally, developers should review their AndroidManifest.xml files to ensure that critical components remain properly secured with android:exported=false where appropriate, although this alone is insufficient without fixing the underlying web view handling logic. Regular security audits of third-party libraries used in mobile applications are also recommended to identify similar misconfigurations before they can be exploited by local attackers.