dbcve.org
AndroidOperating system · Google

CVE-2025-22433

HIGH · 7.8 CVSS v3.1 Published 2025-09-02
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 canForward of IntentForwarderActivity.java, there is a possible bypass of the cross profile intent filter most commonly used in Work Profile scenarios 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 · high confidence

A logic error in the canForward method of IntentForwarderActivity.java allows bypass of cross-profile intent filters in Android Work Profile scenarios. The vulnerability enables local privilege escalation by allowing intents to be forwarded across profile boundaries without proper validation, despite the cross-profile intent filter protections.

MitigationApply the vendor-provided Android security patch containing the fix for the logic error in IntentForwarderActivity.java canForward method. Organizations with managed Work Profiles should verify the patch is applied to all affected devices.

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:= 13.0= 14.0= 15.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
    Go to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)
    Affected if Device runs Android 13.0, 14.0, or 15.0 specifically (not other versions)
  2. Confirm Work Profile is configured
    Go to Settings > Accounts > Work Profile (or check for work profile icon in status bar, or run 'dumpsys device_policy' via ADB)
    Affected if A managed Work Profile is set up on the device (vulnerability only applies in Work Profile scenarios)
  3. Check Security Patch Level
    Go to Settings > About Phone > Security patch level (or run 'getprop ro.build.version.security_patch' via ADB)
    Affected if Security patch level is earlier than the vendor fix for this specific logic error in IntentForwarderActivity.java canForward method
  4. Inspect IntentForwarderActivity accessibility
    Check if IntentForwarderActivity component is exported and accessible across profiles (run 'dumpsys package <packagename>' for system packages containing this activity)
    Affected if IntentForwarderActivity is exported and no additional profile-boundary enforcement is present beyond the vulnerable canForward method logic

Device is affected if running Android 13.0, 14.0, or 15.0 with an active Work Profile and a Security Patch Level predating the vendor fix for the canForward logic error in IntentForwarderActivity.

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 vendor-provided Android security patch containing the fix for the logic error in IntentForwarderActivity.java canForward method. Organizations with managed Work Profiles should verify the patch is applied to all affected devices.

Recommended fix Moderate confidence

Android Security Patch Level (date varies by device manufacturer - check Android Security Bulletin for the specific release containing the fix)

  1. Check your Android device's current security patch level in Settings > About Phone > Android version > Security patch level
  2. Identify which Android Security Bulletin addressed this vulnerability (CVE-2025-22433)
  3. If your device has not received a security update containing the fix for this CVE, contact your device manufacturer or carrier for the latest security update
  4. Apply the latest available Android security update for your device model
  5. After updating, verify the security patch level has been updated to include the fix for CVE-2025-22433
Caveat Security updates are generally backward compatible and contain bug fixes; minimal risk of breaking changes for this type of fix

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22433 — 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-22433 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