Skip to content
Noroxi
CVE-2025-26428· NVD / CVE Program· CNA google_android

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

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.

LowCVSS 3.2 · v3.1—No exploit No fix recorded
Published
Sep 4, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 1th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
googleandroid

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • google android13.0
  • google android14.0
  • google android15.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (google_android). Independent of NVD's CPE analysis and usually ahead of it.

  • Google Android

    • 15, 14, 13affected

Same product

google: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-2215A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel.KEV
    83Now
  • CVE-2011-1823The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows KEV
    73This week
  • CVE-2015-1538Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I all
    70This week
  • CVE-2015-3829Off-by-one error in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I allows re
    67This week
  • CVE-2015-3824The MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I does not properly restrict si
    67This week
  • CVE-2015-3864Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in Android before 5.1.1
    66This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-264210 days apartIn multiple locations, there is a possible lock screen bypass due to a logic error in the code.
    16Monitor
  • CVE-2025-264190 days apartIn initPhoneSwitch of SystemSettingsFragment.java, there is a possible FRP bypass due to a logic error in the code.
    13Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2025-323120 days apartIn createIntentsList of PackageParser.java , there is a possible way to bypass lazy bundle hardening, allowing modified data to be passed to
    31Monitor
  • CVE-2025-323270 days apartIn multiple functions of PickerDbFacade.java, there is a possible unauthorized data access due to SQL injection.
    31Monitor
  • CVE-2025-485440 days apartIn multiple locations, there is a possible way to read files belonging to other apps due to SQL injection.
    31Monitor
  • CVE-2025-485500 days apartIn testGrantSlicePermission of SliceManagerTest.java, there is a possible permanent denial of service due to a path traversal error.
    22Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-290 · Authentication Bypass by Spoofing

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records