dbcve.org
AndroidOperating system · Google

CVE-2025-26431

HIGH · 7.8 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In setupAccessibilityServices of AccessibilityFragment.java, there is a possible way to hide an enabled accessibility service due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Android framework vulnerability in AccessibilityFragment.java where a logic error in the setupAccessibilityServices method allows hiding an enabled accessibility service. The flaw enables local privilege escalation without requiring user interaction or additional execution privileges.

MitigationApply the Android security patch that addresses the logic error in AccessibilityFragment.java. Users should ensure their devices receive the latest Android security updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is 14.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The displayed version is exactly 14.0 (note: other versions are not affected by this specific CVE)
  2. Confirm accessibility services are configured
    Navigate to Settings > Accessibility > Services, or inspect /data/system/accessibility_service_config.xml if accessible
    Affected if Any accessibility services are enabled or have been enabled on the device, as the vulnerability can hide their enabled state
  3. Check for unexpected accessibility service behavior
    Review the list of enabled accessibility services in Settings > Accessibility > Services and compare against known-expected services for your device
    Affected if Enabled accessibility services appear to be missing from the UI or their enabled status is inconsistently reported
  4. Verify system UI reflects accessibility status accurately
    Toggle an accessibility service off and on, then verify the status indicator in Settings reflects the change correctly
    Affected if The accessibility service status does not accurately reflect its enabled/disabled state after toggling

You are affected if your device runs Android 14.0 and has accessibility services configured, as the logic error in AccessibilityFragment.java can cause enabled accessibility services to be hidden from the system UI.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch that addresses the logic error in AccessibilityFragment.java. Users should ensure their devices receive the latest Android security updates.

Recommended fix Moderate confidence

Android 14.0 with subsequent security patch level (check source.android.com/security/bulletin for specific SPL containing fix)

  1. 1. Check the Android Security Bulletin for the patch that addresses this vulnerability (CVE-2025-26431)
  2. 2. Identify the required Security Patch Level (SPL) for your device
  3. 3. Apply the latest Android system update or security patch for Android 14.0
  4. 4. If no update is available from your device manufacturer, consider upgrading to a newer Android version if available
  5. 5. Verify the accessibility service settings are correctly configured after the update
Caveat Security updates for Android 14.0 typically do not introduce breaking changes; however, verify app compatibility after applying system updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26431 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data