CWE-288Weakness · CWE-288

CVE-2026-20460

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges Zero-click 8 weeks old

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, there is a possible information disclosure due to improper input validation. This could lead to remote information disclosure, 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: MOLY01811421; Issue ID: MSV-6788.

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

This vulnerability exists in the modem component of user equipment where improper input validation allows a rogue base station to trigger information disclosure. An attacker controlling a malicious base station can exploit this to leak sensitive data from connected UE devices without requiring any user interaction or elevated privileges.

MitigationApply the vendor patch (MOLY01811421) via firmware update to affected devices. Additionally, users should be advised to connect only to trusted networks and cellular operators to reduce exposure to rogue base station attacks.

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
None
Availability
None

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 if your device has a cellular modem component
    Review device specifications or system information to confirm the presence of a modem/baseband component typically found in smartphones, tablets, or IoT devices with cellular connectivity
    Affected if Device does not have a cellular modem, then the vulnerability does not apply
  2. Determine the modem firmware version
    Access the device's baseband or modem firmware information through system settings (often under About Phone > SIM Status or through AT commands via serial/USB debugging interface), or check the vendor documentation for version retrieval methods
    Affected if Unable to determine the modem firmware version - further investigation needed with vendor tools
  3. Compare your modem firmware against the patched version
    Check if the installed modem firmware version includes the patch identifier MOLY01811421 or is newer than the vulnerable version that received this fix
    Affected if Modem firmware is older than the version containing patch MOLY01811421 and has not been updated
  4. Verify if the device connects to cellular networks
    Confirm whether the device has cellular network capability enabled and actively connects to mobile networks (2G/3G/4G/5G)
    Affected if Device does not have cellular connectivity enabled, the attack surface is reduced but the underlying vulnerable code may still exist in the firmware
  5. Check for vendor security advisories
    Review the device manufacturer's security bulletins or support pages for CVE-2026-20460 to confirm if your specific device model and version are listed as affected
    Affected if Device model and firmware version are confirmed affected by vendor advisory with no patch available

You are affected if your cellular device contains a modem component running firmware without the MOLY01811421 patch and has cellular network connectivity enabled.

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

Apply the vendor patch (MOLY01811421) via firmware update to affected devices. Additionally, users should be advised to connect only to trusted networks and cellular operators to reduce exposure to rogue base station attacks.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20460 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20460 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