CVE-2025-14307 json
Insecure Temporary File Creation in Robocode's AutoExtract Component
published 11mo ago modified 27d ago also EUVD-2025-201885 , GHSA-2mxr-rc97-xrj2
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
An insecure temporary file creation vulnerability exists in the AutoExtract component of Robocode version 1.9.3.6. The createTempFile method fails to securely create temporary files, allowing attackers to exploit race conditions and potentially execute arbitrary code or overwrite critical files. This vulnerability can be exploited by manipulating the temporary file creation process, leading to potential unauthorized actions.
Patch / fix
- maven net.sf.robocode:robocode.battle 1.9.5.6
- robocode Ubuntu Pro 16.04 LTS 1.9.2.5-2ubuntu0.1~esm1
- robocode Ubuntu Pro 18.04 LTS 1.9.3.1-1ubuntu0.1~esm1
- robocode Ubuntu Pro 20.04 LTS 1.9.3.7-1ubuntu0.1~esm1
- robocode Ubuntu Pro 22.04 LTS 1.9.3.9-2ubuntu0.1~esm1
- robocode Ubuntu Pro 24.04 LTS 1.9.3.9-3ubuntu0.1~esm1
- robocode Ubuntu Pro 26.04 LTS 1.9.3.9-4ubuntu0.26.04.1~esm1
ubuntu advisories UBUNTU-CVE-2025-14307
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/robo-code/robocode@9f882bb commit
- github.com/robo-code/robocode#68 pull request
Is CVE-2025-14307 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
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/AU:Y/R:U/V:D/RE:M/U:Red |
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:M/U:Red |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | net.sf.robocode:robocode.battle | <1.9.5.6 |
1.9.5.6 |
Affected products
- Robocode Project Robocode
Classification
- Weakness
-
- CWE-377 DEPRECATED: Insecure Temporary File
References
-
github.com
/robo-code/robocode/pull/68
web, issue-tracking, vendor-advisory
-
github.com
/robo-code/robocode/commit/9f882bba2a9cd91da57c16b98699f8cc9b354f3a
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-14307
advisory
-
github.com
/robo-code/robocode
package
Sources
- CVE List CVE-2025-14307
- GitHub Advisory GHSA-2mxr-rc97-xrj2
- NVD CVE-2025-14307
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.