CWE
416
Advisory Published
Updated

CVE-2016-1052: Use After Free

First published: Wed May 11 2016(Updated: )

Use-after-free vulnerability in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2016-1045, CVE-2016-1046, CVE-2016-1047, CVE-2016-1048, CVE-2016-1049, CVE-2016-1050, CVE-2016-1051, CVE-2016-1053, CVE-2016-1054, CVE-2016-1055, CVE-2016-1056, CVE-2016-1057, CVE-2016-1058, CVE-2016-1059, CVE-2016-1060, CVE-2016-1061, CVE-2016-1065, CVE-2016-1066, CVE-2016-1067, CVE-2016-1068, CVE-2016-1069, CVE-2016-1070, CVE-2016-1075, CVE-2016-1094, CVE-2016-1121, CVE-2016-1122, CVE-2016-4102, and CVE-2016-4107.

Credit: psirt@adobe.com

Affected SoftwareAffected VersionHow to fix
Apple iOS and macOS
Microsoft Windows Operating System
Adobe Acrobat Reader<=11.0.15
Adobe Acrobat Reader DC<=15.006.30121
Adobe Acrobat Reader DC<=15.010.20060
Adobe Acrobat Reader<=15.006.30121
Adobe Acrobat Reader<=15.010.20060
Adobe Acrobat Reader<=11.0.15

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-1052?

    CVE-2016-1052 is classified as a critical vulnerability that can allow attackers to execute arbitrary code.

  • How do I fix CVE-2016-1052?

    To fix CVE-2016-1052, update Adobe Reader and Acrobat to the latest version 11.0.16 or higher, or 15.006.30172 or higher for Acrobat DC.

  • What software is affected by CVE-2016-1052?

    CVE-2016-1052 affects Adobe Reader and Acrobat versions prior to 11.0.16 and various Acrobat DC versions before 15.016.20039.

  • Can CVE-2016-1052 affect my Mac or Windows system?

    Yes, CVE-2016-1052 can impact users on both Windows and macOS systems using vulnerable versions of Adobe software.

  • Is there a workaround for CVE-2016-1052 if I can't update?

    There is no official workaround for CVE-2016-1052; it is recommended to update to a secure version to mitigate the risk.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203