Menu

Star on GitHub · 3.2k

CVE-2025-26428

3.2 · LOW

In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a logic error in the code.

Published Sep 4, 2025CWE-290EPSS 0.10%

Overview

CVE-2025-26428 is a low-severity vulnerability. It was published on September 4, 2025 and has a CVSS 3.1 base score of 3.2 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.2, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a logic error in the code. This could lead to physical escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-26428?

CVE-2025-26428 is a low-severity vulnerability. It was published on September 4, 2025 and has a CVSS 3.1 base score of 3.2 (LOW).

How severe is CVE-2025-26428?

This vulnerability has a CVSS 3.1 base score of 3.2, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2025-26428?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-26428?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-26428 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all