Security Digest · Vulnerability record

CVE-2025-14307: Robocode has an insecure temporary file creation vulnerability in the AutoExtract component

An insecure temporary file creation vulnerability exists in the AutoExtract component of Robocode version 1.9.3.6.

CVSS 9.3 Critical EPSS 0.3% · p25

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.3%, percentile 25: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 25% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.
  • Only applies if your dependency tree includes net.sf.robocode:robocode.battle (Maven) < 1.9.5.6, fixed in 1.9.5.6. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.

Weakness type: CWE-377.

Product: net.sf.robocode:robocode.battle (Maven) · Assigned by: GovTech CSG · Published: 2025-12-09

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Mavennet.sf.robocode:robocode.battle< 1.9.5.61.9.5.6
VendorProductAffected versions (per CVE record)
Robocode ProjectRobocode1.9.3.6

Severity scores

Scored byCVSSScoreVector
GovTech CSG4.09.3 CriticalCVSS: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
GitHub4.09.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
  • Attack vector: local access needed
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: low (any account)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.33% probability of exploitation activity in the next 30 days; percentile 25.

Timeline

  • — CVE record last updated
  • — CVE record published by GovTech CSG
  • — GitHub-reviewed advisory GHSA-2mxr-rc97-xrj2 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-2mxr-rc97-xrj2 github.com
  2. CVE.org record CVE-2025-14307 cve.org
  3. NVD entry CVE-2025-14307 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com

Critical Maven advisories · Today’s Security Digest