CVE-2021-40161
No exploitation reported by the sources we read.
- Published2021-12-23
- Fixed in2022.2 · 2022.1.2 · 2021.1.2 · 2020.1.5 · 2019.1.4
- WeaknessCWE-787
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
A Memory Corruption vulnerability may lead to code execution through maliciously crafted DLL files through PDFTron earlier than 9.0.7 version.
Timeline
dates in UTC- 2021-12-2319: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-2021-40161?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-40161?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 |
|---|---|---|---|
| 2022.x | > 2022, < 2022.2 | 2022.2 | NVD |
| 2022.x | ≥ 2022, < 2022.1.2 | 2022.1.2 | NVD |
| 2021.x | ≥ 2021, < 2021.1.2 | 2021.1.2 | NVD |
| 2020.x | ≥ 2020, < 2020.1.5 | 2020.1.5 | NVD |
| 2019.1 | < 2019.1.4 | 2019.1.4 | NVD |
| 2020.x | = 2020 | no fix published | NVD |
| 2021.x | = 2021 | no fix published | NVD |
| 2022.x | = 2022 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2022.x | ≥ 2022, < 2022.2 | 2022.2 | NVD |
| 2022.x | ≥ 2022, < 2022.1.2 | 2022.1.2 | NVD |
| 2021.x | ≥ 2021, < 2021.1.2 | 2021.1.2 | NVD |
| 2020.x | ≥ 2020, < 2020.1.5 | 2020.1.5 | NVD |
| 2019.1 | < 2019.1.4 | 2019.1.4 | NVD |
| 2020.x | = 2020 | no fix published | NVD |
| 2021.x | = 2021 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2022.x | ≥ 2022, < 2022.1.2 | 2022.1.2 | NVD |
| 2021.x | ≥ 2021, < 2021.1.2 | 2021.1.2 | NVD |
| 2020.x | ≥ 2020, < 2020.1.5 | 2020.1.5 | NVD |
| 2019.1 | < 2019.1.4 | 2019.1.4 | NVD |
10 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 Autodesk autocad to 2022.2 · 2022.1.2 · 2021.1.2 · 2020.1.5 · 2019.1.4
Advisories and patches
- www.autodesk.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
- NVDCVSS 3.17.8read 2026-10-23
- NVDCVSS 2.04.4read 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score1.5 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2021-12-23
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-40161?
Is CVE-2021-40161 actively exploited?
What is the CVSS score for CVE-2021-40161?
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.