dbcve.org
VulnerabilityAwaiting classification

CVE-2026-21051

MEDIUM · 5.1 CVSS v4.0 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click 6 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
Incorrect default permissions in WLAN security prior to SMR Jul-2026 Release 1 allows local attackers to configure TencentWifiSecurity settings.

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 is a local privilege escalation vulnerability in Samsung mobile devices where incorrect default permissions in WLAN security components allow a local attacker to modify TencentWifiSecurity settings without proper authorization. The vulnerability exists in versions prior to the SMR July-2026 Release 1 security patch.

MitigationApply the Samsung SMR July-2026 Release 1 security update or later to patch the incorrect default permissions in the WLAN security component.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Samsung device model and Android version
    Go to Settings > About Phone and record the device model number and Android version
    Affected if The device is a Samsung mobile device running Android
  2. Check Samsung security patch level
    Go to Settings > About Phone > Software Information and look for the 'Security patch level' or 'SMR' version date
    Affected if The security patch level is earlier than July-2026 or the SMR version is earlier than SMR-July-2026-R1
  3. Verify TencentWifiSecurity component presence
    Check installed apps in Settings > Apps for 'TencentWifiSecurity' or a similar WLAN security component from Tencent
    Affected if TencentWifiSecurity or a related Tencent WLAN security app is installed on the device
  4. Inspect WLAN security component permissions
    Go to Settings > Apps > TencentWifiSecurity > Permissions and verify if the app has permission to modify system settings or network configurations
    Affected if The component has elevated permissions (like WRITE_SETTINGS or CHANGE_WIFI_STATE) that could be exploited for unauthorized modifications

A Samsung mobile device is affected if it has a security patch level earlier than SMR July-2026 Release 1 and has TencentWifiSecurity or a similar WLAN security component installed with elevated permissions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Samsung SMR July-2026 Release 1 security update or later to patch the incorrect default permissions in the WLAN security component.

Recommended fix Moderate confidence

SMR Jul-2026 Release 1 (or later Samsung security maintenance release)

  1. Identify your current Samsung device model and firmware version via Settings > About Phone > Software Information
  2. Check for and install the latest Samsung Security Maintenance Release (SMR) - specifically SMR Jul-2026 Release 1 or later via Settings > Software Update > Download and Install
  3. After update, verify the WLAN security settings have correct permissions by reviewing the device's Wi-Fi security configuration
Caveat Standard Samsung firmware update risks apply - ensure device is charged and backed up before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-21051 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