CVE-2021-26687
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 · uneditedAn issue was discovered on LG mobile devices with Android OS 8.0, 8.1, 9.0, and 10 software. In preloaded applications, the HostnameVerified default is mishandled. The LG ID is LVE-SMP-200029 (February 2021).
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 confidenceThis vulnerability involves improper handling of the HostnameVerifier default behavior in preloaded applications on LG mobile devices running Android 8.0, 8.1, 9.0, and 10. This mishandling likely allows SSL/TLS certificate validation to be bypassed, potentially enabling man-in-the-middle attacks against affected devices.
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= 8.0= 8.1= 9.0= 10.0CVSS 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 device manufacturerCheck the device settings to confirm the manufacturer is LG. Navigate to Settings > About Phone > Manufacturer or Brand.Affected if Device is manufactured by LG
-
Check Android versionNavigate to Settings > About Phone > Android Version. Confirm the version is 8.0, 8.1, 9.0, or 10.0.Affected if Android version equals 8.0, 8.1, 9.0, or 10.0
-
Verify affected preloaded applications existReview the list of preinstalled applications on the device. Since the vulnerability affects the HostnameVerifier default behavior in preloaded apps, examine which preloaded apps handle network/SSL connections.Affected if Preloaded applications with SSL/TLS capabilities are present on the device
-
Inspect SSL certificate validation behaviorUse a network traffic analysis tool (such as a proxy or packet capture) to test SSL/TLS connections from preloaded applications. Observe if certificate hostname validation is being bypassed or ignored.Affected if Preloaded applications fail to properly validate SSL/TLS certificate hostnames, allowing connections to proceed despite hostname mismatches
The device is affected if it is an LG device running Android 8.0, 8.1, 9.0, or 10.0 and contains preloaded applications that improperly handle HostnameVerifier, resulting in bypassed SSL/TLS certificate validation.
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-supplied security patch from LG (LVE-SMP-200029) immediately. If no patch is available for affected devices, consider retiring or replacing those devices given the critical severity.
- Consultation8.0 h
- Implementation16.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26687 — 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-2021-26687 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