medium
5.5
CWE
125
Advisory Published
Updated

CVE-2022-35669

First published: Wed Jul 27 2022(Updated: )

Acrobat Reader versions 22.001.20142 (and earlier), 20.005.30334 (and earlier) and 20.005.30334 (and earlier) are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Credit: psirt@adobe.com

Affected SoftwareAffected VersionHow to fix
Adobe Acrobat Reader DC>=15.008.20082<=22.001.20142
Adobe Acrobat Reader>=15.008.20082<=22.001.20142
macOS
Microsoft Windows Operating System
Adobe Acrobat Reader>=20.001.30005<=20.005.30334
Adobe Acrobat Reader Notification Manager>=20.001.30005<=20.005.30334
Adobe Acrobat Reader>=20.001.30005<=20.005.30331
Adobe Acrobat Reader Notification Manager>=20.001.30005<=20.005.30331
Adobe Acrobat Reader>=17.011.30059<=17.012.30229
Adobe Acrobat Reader Notification Manager>=17.011.30059<=17.012.30229
Adobe Acrobat Reader>=17.011.30059<=17.012.30227
Adobe Acrobat Reader Notification Manager>=17.011.30059<=17.012.30227

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2022-35669?

    CVE-2022-35669 is considered a critical severity vulnerability due to its potential to disclose sensitive information.

  • How do I fix CVE-2022-35669?

    To fix CVE-2022-35669, update Adobe Acrobat Reader to version 22.001.20143 or later, or Acrobat to version 20.005.30335 or later.

  • What types of software are affected by CVE-2022-35669?

    CVE-2022-35669 affects Adobe Acrobat DC and Adobe Acrobat Reader versions prior to the specified fixed versions.

  • Can CVE-2022-35669 lead to exploitation of my system?

    Yes, CVE-2022-35669 can be exploited to bypass security mitigations like ASLR, potentially compromising system security.

  • Is there a workaround for CVE-2022-35669 until I can update?

    Currently, there is no effective workaround for CVE-2022-35669 other than applying the necessary updates to affected software.

Company

Resources

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