CVE-2026-0136
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 read due to a missing bounds check. This could lead to remote denial of service 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 missing bounds check in the Modem component allows an out of bounds memory read, leading to remote denial of service. The vulnerability can be exploited without requiring additional privileges or user interaction.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device's modem/baseband firmware versionNavigate to Settings > About Phone > Baseband version, or use ADB command: getprop gsm.version.basebandAffected if The baseband version cannot be verified against a safe version from the vendor (no specific vulnerable versions provided in CVE)
-
Confirm modem component is present and activeCheck if the device has cellular modem capability by verifying the presence of cellular network bars and running: getprop | grep -i modem or checking /dev/tty* entriesAffected if The device has an active cellular modem component that handles network communications
-
Verify cellular network exposureCheck if the device is connected to cellular network (LTE/5G/GSM) - this is where the attack surface existsAffected if The device has cellular connectivity and the modem is reachable over the air
-
Check Android security patch levelNavigate to Settings > About Phone > Security patch level to see when your device last received security updatesAffected if The security patch level is older than when vendors began releasing fixes for this modem vulnerability (contact vendor for specific timeline)
You are affected if your Android device has an active cellular modem and the vendor has not released or applied a firmware update addressing the missing bounds check in the Modem component.
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 updates for the Modem component that include proper bounds checking. If no update is available, consider network-level mitigations such as rate limiting to reduce attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,432.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0136 — 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-0136 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