CVE-2020-16949
No exploitation reported by the sources we read.
- Published2020-10-16
- WeaknessCWE-401
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
<p>A denial of service vulnerability exists in Microsoft Outlook software when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could cause a remote denial of service against a system.</p> <p>Exploitation of the vulnerability requires that a specially crafted email be sent to a vulnerable Outlook server.</p> <p>The security update addresses the vulnerability by correcting how Microsoft Outlook handles objects in memory.</p>
Timeline
dates in UTC- 2020-10-1623: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-16949?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-16949?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 |
|---|---|---|---|
| — | all versions | no fix published | NVD |
| 1607.x | = 1607 | no fix published | NVD |
| 1709.x | = 1709 | no fix published | NVD |
| 1803.x | = 1803 | no fix published | NVD |
| 1809.x | = 1809 | no fix published | NVD |
| 1903.x | = 1903 | no fix published | NVD |
| 1909.x | = 1909 | no fix published | NVD |
| 2004.x | = 2004 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
| 1903.x | = 1903 | no fix published | NVD |
| 1909.x | = 1909 | no fix published | NVD |
| 2004.x | = 2004 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2010.x | = 2010 | no fix published | NVD |
| 2013.x | = 2013 | no fix published | NVD |
| 2016.x | = 2016 | no fix published | NVD |
8 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
Advisories and patches
- portal.msrc.microsoft.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CNACVSS 3.14.7read 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-401read 2026-10-23
- FIRST EPSSEPSS score3.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-10-16
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-16949?
Is CVE-2020-16949 actively exploited?
What is the CVSS score for CVE-2020-16949?
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.