CVE-2025-12695 json
Insecure configuration in DSPy lead to arbitrary file read when running untrusted code inside the sandbox
published last yr. modified 6d ago also GHSA-vvw2-h478-xwr3 , PYSEC-2026-1318 , EUVD-2025-37741
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-12695 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | dspy | <=3.0.3 |
no fix listed |
Classification
- Weakness
-
- CWE-653 Improper Isolation or Compartmentalization
References
-
research.jfrog.com
/vulnerabilities/dspy-sandbox-escape-arbitrary-file-read-jfsa-2025-001495652/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-12695
advisory
-
github.com
/stanfordnlp/dspy
package
-
research.jfrog.com
/vulnerabilities/dspy-sandbox-escape-arbitrary-file-read-jfsa-2025-001495652
web
-
pypi.org
/project/dspy
package
-
github.com
/advisories/GHSA-vvw2-h478-xwr3
advisory
Sources
- CVE List CVE-2025-12695
- GitHub Advisory GHSA-vvw2-h478-xwr3
- NVD CVE-2025-12695
- OSV PYSEC-2026-1318
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.