# CVE-2020-26147: Other in n/a

> Attackers can inject packets or exfiltrate data by exploiting Wi-Fi fragment reassembly flaws in the Linux kernel.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 May 2021
- **Updated:** 14 Apr 2026
- **Also known as:** DEBIAN-CVE-2020-26147, GHSA-f393-4p85-6h6g, UBUNTU-CVE-2020-26147

## What is CVE-2020-26147?

CVE-2020-26147 is a medium-severity vulnerability in Debian Debian Linux, published on 11 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in the Linux kernel 5.8.9. The WEP, WPA, WPA2, and WPA3 implementations reassemble fragments even though some of them were sent in plaintext. This vulnerability can be abused to inject packets and/or exfiltrate selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used.

## Which versions are affected by CVE-2020-26147?

It affects 8 products.


Products: Arista C-65 Firmware, Arista C-75 Firmware, Arista O-90 Firmware, Arista W-68 Firmware, Debian Debian Linux, Linux kernel, Siemens Scalance W1700 Ieee 802.11ac Firmware, Siemens Scalance W700 Ieee 802.11n Firmware.

## How do I fix CVE-2020-26147?

Apply the vendor's patch.

## Is CVE-2020-26147 being exploited?

There is no known exploitation of CVE-2020-26147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26147 and fix it if it is affected.

What it is: CVE-2020-26147 is a medium-severity vulnerability in Debian Debian Linux, published on 11 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26147 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26147/ (Markdown: https://insights.sbomify.com/CVE-2020-26147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26147
- OSV: https://osv.dev/vulnerability/CVE-2020-26147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26147/
Summaries are generated and may contain mistakes; the official description above is the record.