CVE-2026-0120
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 · uneditedIn modem, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution 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 confidenceA critical out-of-bounds write vulnerability exists in modem firmware due to an incorrect bounds check, allowing remote attackers to execute arbitrary code without requiring any user interaction or elevated privileges.
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 dataall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and modem chipsetCheck your Android device settings under 'About Phone' to find the model number and 'SIM card status' or use 'AT commands' (if accessible) to query the modem chipset (e.g., Qualcomm, MediaTek, Samsung). The vulnerability exists in the modem firmware component, so knowing the specific modem hardware is essential for tracking vendor patches.Affected if The device has a cellular modem and runs Android - all Android devices are potentially affected according to the scope.
-
Check the baseband/modem firmware versionOn Android, dial *#*#4636#*#* or go to Settings > About Phone > SIM Status to view the baseband version. Alternatively, use ADB command 'adb shell getprop gsm.version.baseband' to retrieve the modem firmware version string.Affected if The displayed baseband version matches a version that contains the unpatched vulnerable code - however, since all Android versions are affected per the CVE, no specific vulnerable version string can be provided.
-
Verify vendor security patch levelGo to Settings > About Phone > Security Patch Level to see the date of the last security update. This indicates whether the vendor has released patches for this vulnerability.Affected if The Security Patch Level is older than the date when the vendor released a fix for CVE-2026-0120, or if no patch has been released for your specific device model.
-
Confirm modem interface is exposedCheck if the device has USB debugging enabled or if diagnostic modem interfaces (e.g., QCDM, AT ports) are accessible. The vulnerability can be exploited remotely without user interaction, meaning any device with an active cellular connection is potentially reachable.Affected if The device has cellular connectivity enabled and the modem is reachable - which is the default state for most Android devices.
A user is affected if their Android device contains this modem firmware vulnerability and the baseband/modem component has not been patched by the device vendor, regardless of Android OS version.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided firmware patches when available; until then, isolate modem-facing network segments and restrict exposure to untrusted networks.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0120 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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