CVE-2026-21003
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 · uneditedImproper input validation in data related to network restrictions prior to SMR Apr-2026 Release 1 allows physical attackers to bypass the restrictions.
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 confidenceImproper input validation in network restriction data allows physical attackers to bypass those restrictions. The vulnerability exists in Samsung mobile devices prior to the April 2026 SMR (Samsung Maintenance Release) update.
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= 14.0= 15.0= 16.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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 the Android version on the Samsung deviceGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version displays as 14.0, 15.0, or 16.0 exactly
-
Confirm the device is a Samsung mobile deviceCheck Settings > About Phone > Model number, or run 'getprop ro.product.brand' via ADB shell - it should return 'Samsung'Affected if The device is not made by Samsung (this CVE only affects Samsung mobile devices)
-
Check the Samsung Maintenance Release (SMR) patch levelGo to Settings > About Phone > Software information > Build number, or run 'getprop ro.build.version.sem' via ADB shellAffected if The SMR patch level is earlier than the April 2026 release (the vulnerability exists in versions prior to the Apr-2026 SMR update)
-
Verify if network restriction features are configuredCheck Settings > Network & Internet > Mobile Network > Preferred Network Type or similar network restriction settings depending on the One UI versionAffected if Network restriction data is present and configured (the vulnerability allows bypassing these restrictions)
A Samsung Android device running version 14.0, 15.0, or 16.0 that has not received the April 2026 SMR update is affected by this vulnerability.
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.
dbcve · scopedApply the Samsung SMR Apr-2026 Release 1 or later security update to affected devices to remediate this vulnerability.
SMR Apr-2026 Release 1
- Check your Samsung device for the April 2026 security update (SMR Apr-2026 Release 1) by going to Settings > Security and privacy > Security update
- If the update is available, download and install it immediately
- After updating, verify the security patch level in Settings > About phone > Software information matches the April 2026 security patch level
- Ensure network restrictions settings remain enabled and functioning properly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21003 — 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-21003 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