dbcve.org
AndroidOperating system · Google

CVE-2025-71252

HIGH · 7.5 CVSS v3.1 Published 2026-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Modem IMS, there is a possible improper input validation. This could lead to remote denial of service with no additional execution privileges needed.

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

In Modem IMS (IP Multimedia Subsystem), improper input validation allows remote attackers to cause denial of service without requiring any authentication or special privileges. The vulnerability is network-exploitable and could crash or render the IMS service unavailable.

MitigationImplement proper input validation and sanitization on all IMS interface inputs, particularly those processing external network messages. Apply vendor patches when available and consider network-level filtering to limit exposure to untrusted sources.

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= 16.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is 13.0, 14.0, 15.0, or 16.0 exactly (note: only exact version matches are listed as affected)
  2. Determine if IMS (VoLTE/VoWiFi) is enabled
    Check Settings > Network & Internet > Calls > Calls over Wi-Fi or Settings > Connections > Mobile Networks > VoLTE. Alternatively, run 'getprop persist.radio.vomsrc' or check carrier-specific IMS settings in Settings
    Affected if IMS/VoLTE/VoWiFi functionality is turned on and the Android version matches the affected list (the vulnerability exists in the IMS component itself)
  3. Identify modem/radio firmware version
    Check Settings > About Phone > IMEI information, or run 'getprop gsm.version.baseband' via ADB shell. Also check 'getprop ro.build.version.incremental' for radio updates
    Affected if Modem firmware is from the same release cycle as the affected Android versions - the vulnerability resides in the modem IMS implementation, not just the OS layer
  4. Monitor for IMS service crashes or modem failures
    Check Android system logs via 'adb logcat -b system' for IMS-related crashes (search for 'ims', 'IMSM', ' volte', ' ModemService' entries), or review crash reports in Settings > Security > More security settings > Feedback diagnostics
    Affected if Repeated IMS service crashes, modem restarts, or 'Radio died' messages appear in logs, especially when network activity targets IMS ports or protocols
  5. Inspect network exposure of IMS component
    Review device network connections using 'adb shell netstat -an' or check for listening ports related to IMS (typically SIP/RTP ports in the 5000-6000 range or carrier-specific ranges). Verify if device is on a mobile network with IMS provisioning
    Affected if The device has active IMS bindings exposed on the network and is running an affected Android version - the attack vector is remote without authentication

A device is affected if it runs Android 13.0, 14.0, 15.0, or 16.0 and has IMS/VoLTE/VoWiFi functionality enabled, as the improper input validation flaw exists in the modem IMS component that processes incoming network data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and sanitization on all IMS interface inputs, particularly those processing external network messages. Apply vendor patches when available and consider network-level filtering to limit exposure to untrusted sources.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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