CVE-2016-4093: Buffer Overflow

Published May 11, 2016
·
Updated

Adobe Reader and Acrobat before 11.0.16, Acrobat and Acrobat Reader DC Classic before 15.006.30172, and Acrobat and Acrobat Reader DC Continuous before 15.016.20039 on Windows and OS X allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2016-1037, CVE-2016-1063, CVE-2016-1064, CVE-2016-1071, CVE-2016-1072, CVE-2016-1073, CVE-2016-1074, CVE-2016-1076, CVE-2016-1077, CVE-2016-1078, CVE-2016-1080, CVE-2016-1081, CVE-2016-1082, CVE-2016-1083, CVE-2016-1084, CVE-2016-1085, CVE-2016-1086, CVE-2016-1088, CVE-2016-1093, CVE-2016-1095, CVE-2016-1116, CVE-2016-1118, CVE-2016-1119, CVE-2016-1120, CVE-2016-1123, CVE-2016-1124, CVE-2016-1125, CVE-2016-1126, CVE-2016-1127, CVE-2016-1128, CVE-2016-1129, CVE-2016-1130, CVE-2016-4088, CVE-2016-4089, CVE-2016-4090, CVE-2016-4094, CVE-2016-4096, CVE-2016-4097, CVE-2016-4098, CVE-2016-4099, CVE-2016-4100, CVE-2016-4101, CVE-2016-4103, CVE-2016-4104, and CVE-2016-4105.

Affected Software

8 affected components
Apple iOS and macOS
Microsoft Windows
Adobe Acrobat<=11.0.15
Adobe Acrobat DC<=15.006.30121
Adobe Acrobat DC<=15.010.20060
Adobe Acrobat Reader DC<=15.006.30121
Adobe Acrobat Reader DC<=15.010.20060
Adobe Reader<=11.0.15

Event History

May 11, 2016
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-4093?

CVE-2016-4093 has a critical severity rating, allowing potential arbitrary code execution or denial of service.

2

How do I fix CVE-2016-4093?

To fix CVE-2016-4093, update Adobe Acrobat and Reader to version 11.0.16 or higher, and Acrobat and Reader DC to version 15.006.30172 or higher.

3

Which Adobe products are affected by CVE-2016-4093?

CVE-2016-4093 affects Adobe Reader and Acrobat versions before 11.0.16, as well as Acrobat and Acrobat Reader DC Classic and Continuous versions before specified updates.

4

Can CVE-2016-4093 lead to data breaches?

Yes, exploiting CVE-2016-4093 can allow attackers to execute arbitrary code, potentially leading to data breaches.

5

Is there a workaround for CVE-2016-4093?

There are no known workarounds for CVE-2016-4093; the best solution is to apply the latest updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203