CVE-2016-6960: Buffer Overflow

Published Oct 13, 2016
·
Updated

Adobe Reader and Acrobat before 11.0.18, Acrobat and Acrobat Reader DC Classic before 15.006.30243, and Acrobat and Acrobat Reader DC Continuous before 15.020.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-6940, CVE-2016-6941, CVE-2016-6942, CVE-2016-6943, CVE-2016-6947, CVE-2016-6948, CVE-2016-6950, CVE-2016-6951, CVE-2016-6954, CVE-2016-6955, CVE-2016-6956, CVE-2016-6959, CVE-2016-6966, CVE-2016-6970, CVE-2016-6972, CVE-2016-6973, CVE-2016-6974, CVE-2016-6975, CVE-2016-6976, CVE-2016-6977, CVE-2016-6978, CVE-2016-6995, CVE-2016-6996, CVE-2016-6997, CVE-2016-6998, CVE-2016-7000, CVE-2016-7001, CVE-2016-7002, CVE-2016-7003, CVE-2016-7004, CVE-2016-7005, CVE-2016-7006, CVE-2016-7007, CVE-2016-7008, CVE-2016-7009, CVE-2016-7010, CVE-2016-7011, CVE-2016-7012, CVE-2016-7013, CVE-2016-7014, CVE-2016-7015, CVE-2016-7016, CVE-2016-7017, CVE-2016-7018, and CVE-2016-7019.

Affected Software

8 affected components
Apple iOS and macOS
Microsoft Windows
Adobe Acrobat<=11.0.17
Adobe Acrobat DC<=15.006.30201
Adobe Acrobat DC<=15.017.20053
Adobe Acrobat Reader DC<=15.006.30201
Adobe Acrobat Reader DC<=15.017.20053
Adobe Reader<=11.0.17

Event History

Oct 13, 2016
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-6960?

CVE-2016-6960 has been assigned a critical severity rating due to its potential for remote code execution and denial of service.

2

How do I fix CVE-2016-6960?

To resolve CVE-2016-6960, update Adobe Reader and Acrobat to version 11.0.18 or later, and to version 15.006.30243 or later for Acrobat and Acrobat Reader DC.

3

What products are affected by CVE-2016-6960?

CVE-2016-6960 affects Adobe Reader and Acrobat versions prior to 11.0.18 and versions of Acrobat and Acrobat Reader DC prior to 15.006.30243.

4

Can CVE-2016-6960 lead to data loss?

Yes, an exploit of CVE-2016-6960 could result in memory corruption, leading to possible data loss or corruption.

5

Is there a workaround for CVE-2016-6960 until I can apply the patch?

While there are no official workarounds for CVE-2016-6960, avoiding the use of the vulnerable versions until an update is applied is the safest approach.

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