CVE-2026-20458
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 memory corruption due to a missing bounds check. This could lead to remote escalation of privilege, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01402160; Issue ID: MSV-7298.
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 memory corruption when a User Equipment (UE) connects to a rogue base station controlled by an attacker. The vulnerability enables remote privilege escalation without requiring user interaction or additional privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/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 modem component in the deviceExamine the device hardware specifications, firmware documentation, or system logs to determine the modem chipset, firmware version, and vendor. On mobile devices, this may be found in 'AT+CGMR' or 'AT+CGMM' modem AT command output, or in the baseband firmware version displayed in about/ diag menus.Affected if The device contains a cellular modem component from a vendor using the affected codebase.
-
Retrieve the installed modem firmware versionQuery the modem firmware version through vendor-specific interfaces (for example, via AT commands like 'AT+CGMR', through diagnostic menus, or by inspecting /proc/version or baseband-related files on the device filesystem). Record the exact version string.Affected if The firmware version cannot be determined or is unavailable for comparison.
-
Compare the firmware version to the patched releaseCompare the installed firmware version against the patched version MOLY01402160. If the installed version is lower (earlier) than MOLY01402160, the device is running a vulnerable release. If the version is equal to or higher than MOLY01402160, or if the vendor indicates the patch is included, the vulnerability is addressed.Affected if The installed modem firmware version is lower than MOLY01402160.
-
Confirm the device operates as User EquipmentVerify that the device functions as User Equipment (UE) capable of connecting to cellular base stations, such as a smartphone, tablet, cellular IoT device, or mobile hotspot. This is typically evident if the device has cellular connectivity, a SIM card slot, or displays network operator information.Affected if The device is a UE that connects to cellular networks (3G, 4G, 5G).
The device is affected if it contains a cellular modem component, operates as User Equipment connecting to base stations, and runs modem firmware version lower than MOLY01402160.
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 the vendor patch (MOLY01402160) via carrier/firmware update. Users should avoid connecting to untrusted or unknown base stations as a general precaution until the patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20458 — 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-20458 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