# CVE-2026-113385: LeeDrOiD Labs Shortcutter 2 App ToggleGeneric.java Class.forName improper export of android application components


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-94q8-ww55-pw9r

## What is CVE-2026-113385?

CVE-2026-113385 is a medium-severity vulnerability in LeeDrOiD Labs Shortcutter 2 App, published on 20 Oct 2026. 

### Official description

A vulnerability has been found in LeeDrOiD Labs Shortcutter 2 App 9.0.48 on Android. This issue affects the function Class.forName of the file ToggleGeneric.java. The manipulation of the argument Class leads to improper export of android application components. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 9.0.90 is capable of addressing this issue. It is suggested to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-926 (Improper Export of Android Application Components)

## Which versions are affected by CVE-2026-113385?


## How do I fix CVE-2026-113385?

No fix has been published for CVE-2026-113385 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113385 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113385 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113385 and fix it if it is affected.

What it is: CVE-2026-113385 is a medium-severity vulnerability in LeeDrOiD Labs Shortcutter 2 App, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113385 exists.

Affected product: LeeDrOiD Labs Shortcutter 2 App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113385/ (Markdown: https://insights.sbomify.com/CVE-2026-113385/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113385
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113385
- OSV: https://osv.dev/vulnerability/CVE-2026-113385

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113385/
Summaries are generated and may contain mistakes; the official description above is the record.