# CVE-2025-68708: Auth bypass in n/a

> Local attackers with physical access can bypass the PIN lock in SailingLab AppLock by exploiting insecure navigation flows, leading to unauthorized access to protected apps.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-m432-67ph-xv3m

## What is CVE-2025-68708?

CVE-2025-68708 is a low-severity authentication bypass vulnerability in n/a, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SailingLab AppLock (aka com.alpha.applock) 4.3.8 for Android allows a local attacker with physical access to bypass the PIN lock. The lock is implemented as an overlay rather than by using Android's secure authentication APIs. By navigating cascading interface flows - insecure navigation through exposed routes facilitates app control evasion {I.N.T.E.R.F.A.C.E] via advertisement or browser intents - an attacker can evade lockscreen verification and access protected apps (e.g., Chrome). This results in information disclosure and privilege escalation.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-68708?


## How do I fix CVE-2025-68708?

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

## Is CVE-2025-68708 being exploited?

There is no known exploitation of CVE-2025-68708 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68708 and fix it if it is affected.

What it is: CVE-2025-68708 is a low-severity authentication bypass vulnerability in n/a, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68708 in the wild and no public exploit code.

Affected product: n/a. 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-2025-68708/ (Markdown: https://insights.sbomify.com/CVE-2025-68708/index.md)
```

## Sources

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

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