| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in DSPy. This vulnerability affects unknown code. The manipulation leads to improper isolation or compartmentalization. This vulnerability is traded as CVE-2025-12695. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in DSPy (version now known) and classified as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a improper isolation or compartmentalization vulnerability. Using CWE to declare the problem leads to CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. Impacted is confidentiality. The summary by CVE is:
The overly permissive sandbox configuration in DSPy allows attackers to steal sensitive files in cases when users build an AI agent which consumes user input and uses the “PythonInterpreter” class.
The advisory is shared at research.jfrog.com. The identification of this vulnerability is CVE-2025-12695 since 11/04/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (JFROG): 🔒
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: Improper isolation or compartmentalizationCWE: CWE-653
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/04/2025 Advisory disclosed11/04/2025 CVE reserved
11/04/2025 VulDB entry created
11/04/2025 VulDB entry last update
Sources
Advisory: jfsa-2025-001495Status: Not defined
CVE: CVE-2025-12695 (🔒)
GCVE (CVE): GCVE-0-2025-12695
GCVE (VulDB): GCVE-100-331169
Entry
Created: 11/04/2025 16:54Changes: 11/04/2025 16:54 (59)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.