Adobe Acrobat Reader
CVE-2025-64786
LOW
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Lifecycle Timeline
1DescriptionCVE.org
Acrobat Reader versions 24.001.30264, 20.005.30793, 25.001.20982, 24.001.30273, 20.005.30803 and earlier are affected by an Improper Verification of Cryptographic Signature vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to gain limited unauthorized write access. Exploitation of this issue requires user interaction with a cryptographic signature.
AnalysisAI
Improper verification of cryptographic signatures in Adobe Acrobat Reader and Acrobat DC versions up to 24.001.30273, 25.001.20982, and 20.005.30803 allows local attackers to bypass security features and gain limited unauthorized write access to PDF documents. Exploitation requires user interaction with a malicious or specially crafted cryptographic signature embedded in a PDF file. No active exploitation has been confirmed at the time of analysis.
Technical ContextAI
The vulnerability stems from inadequate validation of cryptographic signatures (CWE-347: Improper Verification of Cryptographic Signature) within Adobe's PDF signature verification subsystem. PDFs employ digital signatures to authenticate document origin and integrity; this flaw allows an attacker to craft a signature that fails proper cryptographic verification but is incorrectly accepted by the application. The affected products span Adobe Acrobat (classic track), Acrobat DC (continuous track), Acrobat Reader (classic track), and Acrobat Reader DC (continuous track), as identified by the CPE strings. The signature verification bypass enables unauthorized modification of PDF content despite the presence of a signature field, undermining the document authentication mechanism.
RemediationAI
Apply the security patch released by Adobe in bulletin APSB25-119 immediately. The exact patched versions depend on the product track: for classic track Acrobat and Reader, upgrade to versions after 24.001.30273 or 25.001.20982 (consult APSB25-119 for exact patched version numbers); for continuous track Acrobat DC and Reader DC, update to the latest release. As an interim compensating control, organizations should disable signature verification features if the functionality is not critical to workflows, though this may reduce document authenticity assurance. Users should also avoid opening PDF files from untrusted sources and disable the automatic signature validation prompt to prevent user interaction with malicious signatures. These mitigations reduce functionality and are temporary; patch deployment is the definitive fix. Refer to https://helpx.adobe.com/security/products/acrobat/apsb25-119.html for specific version numbers and deployment guidance.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
cosign is a container signing and verification utility. Rated critical severity (CVSS 9.8), this vulnerability is remote
Biscuit is an authentication and authorization token for microservices architectures. Rated critical severity (CVSS 9.8)
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today