Adobe Acrobat Reader up to 25.001.20982 untrusted search path

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Adobe Acrobat Reader up to 20.005.30793/20.005.30803/24.001.30264/24.001.30273/25.001.20982. Affected by this vulnerability is an unknown functionality. This manipulation causes untrusted search path. This vulnerability appears as CVE-2025-64785. The attack requires local access. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability has been found in Adobe Acrobat Reader up to 20.005.30793/20.005.30803/24.001.30264/24.001.30273/25.001.20982 and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a untrusted search path vulnerability. The CWE definition for the vulnerability is CWE-426. The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Acrobat Reader versions 24.001.30264, 20.005.30793, 25.001.20982, 24.001.30273, 20.005.30803 and earlier are affected by an Untrusted Search Path vulnerability that might allow attackers to execute arbitrary code in the context of the current user. If the application uses a search path to locate critical resources such as programs, an attacker could modify that search path to point to a malicious program, which the targeted application would then execute. Exploitation of this issue does not require user interaction.
The advisory is shared at helpx.adobe.com. This vulnerability is known as CVE-2025-64785 since 11/11/2025. The exploitation appears to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/13/2025). MITRE ATT&CK project uses the attack technique T1574 for this issue.
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.adobe.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.0
VulDB Temp Score: 6.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.4
NVD Vector: 🔒
CNA Base Score: 7.8
CNA Vector (adobe): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Untrusted search pathCWE: CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
11/11/2025 CVE reserved12/10/2025 Advisory disclosed
12/10/2025 VulDB entry created
12/13/2025 VulDB entry last update
Sources
Vendor: adobe.comAdvisory: apsb25-119
Status: Confirmed
CVE: CVE-2025-64785 (🔒)
GCVE (CVE): GCVE-0-2025-64785
GCVE (VulDB): GCVE-100-335533
Entry
Created: 12/10/2025 07:57Updated: 12/13/2025 12:08
Changes: 12/10/2025 07:57 (64), 12/13/2025 12:08 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.