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

CVE-2025-14307 · Severity: high · CVSS 8.1 · Published 2025-12-09

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.

Technologies: Robocode. Vendors: Maven, Robocode.

Quick answers

Is CVE-2025-14307 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-14307 being exploited in the wild.
How severe is CVE-2025-14307?
High severity, with a CVSS score of 8.1, published 9 December 2025.
Which products and versions are affected?
net.sf.robocode:robocode.battle (Maven) ECOSYSTEM:introduced=0,fixed=1.9.5.6.
Is there a fix for CVE-2025-14307?
Yes. net.sf.robocode:robocode.battle (Maven): upgrade to 1.9.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-14307?
Check whether you run net.sf.robocode:robocode.battle (Maven) or Robocode at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • net.sf.robocode:robocode.battle (Maven): upgrade to 1.9.5.6 or later
    # set net.sf.robocode:robocode.battle to 1.9.5.6 in your pom.xml or build.gradle

Affected products

  • net.sf.robocode:robocode.battle (Maven) ECOSYSTEM:introduced=0,fixed=1.9.5.6
  • Robocode

Identifiers

  • CVE-2025-14307
  • GHSA-2mxr-rc97-xrj2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.