CVE-2020-5939
No exploitation reported by the sources we read.
- Published2020-11-05
- Fixed in16.0.1 · 15.1.0.4 · 14.1.2.7
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In versions 16.0.0-16.0.0.1, 15.1.0-15.1.0.3, 15.0.0-15.0.1.3, 14.1.0-14.1.2.6, and 13.1.0-13.1.3.4, BIG-IP Virtual Edition (VE) systems on VMware, with an Intel-based 85299 Network Interface Controller (NIC) card and Single Root I/O Virtualization (SR-IOV) enabled on vSphere, may fail and leave the Traffic Management Microkernel (TMM) in a state where it cannot transmit traffic.
Timeline
dates in UTC- 2020-11-0520:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-5939?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-5939?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | ≥ 16.0.0, < 16.0.1 | 16.0.1 | NVD |
| 15.1 | ≥ 15.1.0, < 15.1.0.4 | 15.1.0.4 | NVD |
| 14.1 | ≥ 14.1.0, < 14.1.2.7 | 14.1.2.7 | NVD |
| 13.1 | ≥ 13.1.0, ≤ 13.1.3 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | ≥ 16.0.0, < 16.0.1 | 16.0.1 | NVD |
| 15.1 | ≥ 15.1.0, < 15.1.0.4 | 15.1.0.4 | NVD |
| 14.1 | ≥ 14.1.0, < 14.1.2.7 | 14.1.2.7 | NVD |
| 13.1 | ≥ 13.1.0, ≤ 13.1.3 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | ≥ 16.0.0, < 16.0.1 | 16.0.1 | NVD |
| 15.1 | > 15.1.0, < 15.1.0.4 | 15.1.0.4 | NVD |
| 14.1 | ≥ 14.1.0, < 14.1.2.7 | 14.1.2.7 | NVD |
| 13.1 | ≥ 13.1.0, ≤ 13.1.3 | no fix published | NVD |
11 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update F5 big-ip access policy manager to 16.0.1 · 15.1.0.4 · 14.1.2.7
Advisories and patches
- support.f5.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.04.3read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2020-11-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-5939?
Is CVE-2020-5939 actively exploited?
What is the CVSS score for CVE-2020-5939?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.