CVE-2020-26146
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 Samsung Galaxy S3 i9305 4.4.4 devices. The WPA, WPA2, and WPA3 implementations reassemble fragments with non-consecutive packet numbers. An adversary can abuse this to exfiltrate selected fragments. This vulnerability is exploitable when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used. Note that WEP is vulnerable to this attack by design.
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 · high confidenceThe Samsung Galaxy S3 i9305 WPA/WPA2/WPA3 implementations incorrectly reassemble WiFi fragments by accepting non-consecutive packet numbers. This allows an attacker positioned to intercept or inject traffic to selectively exfiltrate specific fragments from encrypted communications, bypassing the confidentiality guarantees of CCMP, GCMP, or WEP encryption protocols.
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= 4.4.4< 10.0.1-31< 10.0.1-31< 10.0.1-31< 10.0.1-31< 11.0.0-36< 11.0.0-36< 11.0.0-36CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelDetermine if the device in question is a Samsung Galaxy S3 i9305 or an Arista C-series switch (C 250, C 260, C 230, C 235, C 200, C 120, or C 130)Affected if Device is not one of these models, then the CVE does not apply to this device
-
Check Samsung Galaxy S3 i9305 firmware versionOn the Samsung Galaxy S3 i9305, go to Settings > About Phone > Software Information to view the firmware/build versionAffected if Firmware version is exactly 4.4.4 (this specific version is vulnerable)
-
Check Arista C 250/260/230/235 firmware versionOn the affected Arista switch, run the command 'show version' or check the firmware version via the management interfaceAffected if Firmware version is earlier than 10.0.1-31 (these models are vulnerable below this version)
-
Check Arista C 200/120/130 firmware versionOn the affected Arista switch, run the command 'show version' or check the firmware version via the management interfaceAffected if Firmware version is earlier than 11.0.0-36 (these models are vulnerable below this version)
The environment is affected if the device is a Samsung Galaxy S3 i9305 running firmware 4.4.4, or an Arista C 250/260/230/235 switch running firmware below 10.0.1-31, or an Arista C 200/120/130 switch running firmware below 11.0.0-36.
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 data10.0.1-3111.0.0-36
This is a firmware-level vulnerability in an end-of-life device (Android 4.4.4). Primary mitigation is to retire the device; secondary mitigations include avoiding use on sensitive networks, using VPN tunneling as an additional encryption layer, and ensuring APs do not enable fragmentation when this device connects.
- Consultation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26146 — 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-2020-26146 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