CVE-2026-15193: Command Injection in AidanPark openclaw-android JsBridge

Technical summary

The vulnerability exists in the Android WebView Bridge implementation (JsBridge.kt) within openclaw-android up to version 0.4.0. The bridge fails to properly sanitize or validate user-supplied input before passing it to OS command execution functions, leading to command injection (CWE-77, CWE-78). The attack vector is local and requires the attacker to have local code execution privileges on the Android device; no user interaction is needed once execution begins. The flaw has been publicly disclosed, and a fix is pending in an open pull request awaiting maintainer acceptance.

Business impact

For organizations or individuals deploying openclaw-android, this vulnerability could enable a compromised app process or malicious actor with device access to execute commands outside the intended application scope, potentially leading to unauthorized access to sensitive application data, lateral movement to other app processes, or device compromise. The impact is amplified in enterprise settings where the app might handle sensitive workflows or integrate with corporate data systems.

Affected systems

The vulnerability affects AidanPark openclaw-android versions up to and including 0.4.0. The JsBridge component is the specific attack surface. Any Android application or deployment using this library is in scope. Users of newer versions released after the patch acceptance should verify they are running a version that includes the fix.

Exploitability

Exploitability is limited by the local-only attack vector; remote exploitation is not feasible. An attacker must have already obtained local code execution or device access. The public disclosure of this vulnerability means proof-of-concept code or detailed exploitation guidance is likely already available in public forums or repositories, reducing the skill bar for local attackers. The attack requires low privileges and no user interaction once initiated, making it relatively straightforward to execute for anyone with local access.

Remediation

Upgrade openclaw-android to a version that includes the command injection fix. Monitor the project repository (AidanPark openclaw-android) for an official release that incorporates the pending pull request. Until a patched version is available, restrict app installation to trusted environments and limit the device privileges of the app through Android permission controls. Consider isolating devices running affected versions from sensitive network segments.

Patch guidance

Check the AidanPark openclaw-android GitHub repository or official release channels for version 0.4.1 or later, which should include the merged fix from the pending pull request. Verify the patch notes reference the JsBridge command injection issue (CVE-2026-15193) before deploying. If the fix has not yet been released, monitor the project for updates and plan an immediate upgrade cycle once available. Test the patched version in a staging environment to confirm functionality before production deployment.

Detection guidance

Look for any local processes or apps invoking the openclaw-android JsBridge with unusual or shell-like command syntax. Monitor Android system logs for unexpected OS command execution originating from the openclaw-android application context. Endpoint detection and response (EDR) tools on rooted Android devices can flag suspicious Runtime.exec() calls or ProcessBuilder invocations from the app. Review application logs and audit trails for evidence of command execution outside the app's normal operation scope. In Android Security Center or Google Play Console, check for any app flagged as potentially malicious or modified if distributed outside official channels.

Why prioritize this

While the CVSS score of 5.3 reflects the local-only attack vector, this vulnerability merits prompt attention because the attack chain is straightforward, the flaw has been publicly disclosed, and exploitation does not require sophisticated techniques. In threat models involving insider threats, compromised devices, or physical access scenarios, this becomes a higher-priority concern. The pending patch status also creates urgency—once merged, users should upgrade quickly to close a known and documented gap.

Risk score, explained

The CVSS:3.1 score of 5.3 (Medium) reflects: local attack vector (AV:L), low attack complexity (AC:L), low privilege requirements (PR:L), no user interaction needed (UI:N), unchanged scope (S:U), and low impact across confidentiality, integrity, and availability (C:L, I:L, A:L). The score appropriately captures that while the flaw allows command injection, its local nature and the privilege requirements limit the overall severity. However, the public disclosure and ease of exploitation warrant treating this as higher priority in practical risk assessments than the raw score alone might suggest.

Frequently asked questions