Acrobat Reader DC for macOS Signature Validation Bypass

published 2020-11-05 6y ago modified 2026-06-17 4mo ago also EUVD-2020-17159

cvss: 2.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

Acrobat Reader DC for macOS versions 2020.012.20048 (and earlier), 2020.001.30005 (and earlier) and 2017.011.30175 (and earlier) are affected by a security feature bypass. While the practical security impact is minimal, a defense-in-depth fix has been implemented to further harden the Adobe Reader update process.

Patch / fix

links 1

helpx.adobe.com/security/products/acrobat/apsb20-67.html advisory

Is CVE-2020-24439 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	2.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
NVD	3.1	2.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
NVD	2.0	1.2	AV:L/AC:H/Au:N/C:N/I:P/A:N

Affected products

Adobe Acrobat Reader

Classification

Weakness

CWE-347 Improper Verification of Cryptographic Signature

References

helpx.adobe.com /security/products/acrobat/apsb20-67.html
patch, vendor-advisory

Sources

CVE List CVE-2020-24439
NVD CVE-2020-24439

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.