Local data exposure and tampering via predictable files
Published Jun 26, 2025 · Updated Jul 2, 2025
Insecure temporary-file handling in pycode-browser before 1.0 allows local users to read or modify temporary data. Published records identify predictable filenames but do not disclose the file-creation call, path, or data stored there. Exploitation requires low-privileged local access and user interaction; the published assessment reports no availability impact.
Summary
What happened
Insecure temporary-file handling in pycode-browser before 1.0 allows local users to read or modify temporary data. Published records identify predictable filenames but do not disclose the file-creation call, path, or data stored there. Exploitation requires low-privileged local access and user interaction; the published assessment reports no availability impact.
The record
- CVE
- CVE-2015-0849
- Published
- Jun 26, 2025
- Updated
- Jul 2, 2025
- Vendor
- Inter-University Accelerator Centre
- Product
- pycode-browser
- Classifications
- CWE-377
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2025CVE publishedPublication date reported by the CVE source.
- Jul 2, 2025Record 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 <1.0
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