Limited unauthorized writes via improper signature verification
Published Dec 9, 2025 · Updated Apr 28, 2026
Improper signature verification in Adobe Acrobat Reader 25.001.20982 and earlier allows attackers to gain limited unauthorized write access. Adobe has not disclosed the signature-processing locus or the specific validation error that accepts an improperly verified cryptographic signature. Exploitation requires local user interaction with a cryptographic signature and affects integrity only, without reported data disclosure or service interruption.
Summary
What happened
Improper signature verification in Adobe Acrobat Reader 25.001.20982 and earlier allows attackers to gain limited unauthorized write access. Adobe has not disclosed the signature-processing locus or the specific validation error that accepts an improperly verified cryptographic signature. Exploitation requires local user interaction with a cryptographic signature and affects integrity only, without reported data disclosure or service interruption.
The record
- CVE
- CVE-2025-64787
- Published
- Dec 9, 2025
- Updated
- Apr 28, 2026
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-347, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=20.005.30803
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo