# CVE-2025-14306: robocode.core — Fixed in 1.9.5.6

☕ Maven

Not in CISA KEV

# CVE-2025-14306 — robocode.core

[Fix: robo-code/robocode@26b6ba8](https://github.com/robo-code/robocode/commit/26b6ba8ed5b2a11a646ce2d5da8d42cd53574b1f)

CVE-2025-14306 is a Path Traversal vulnerability in net.sf.robocode:robocode.core. A fix is available for net.sf.robocode:robocode.core — see the affected versions and patch details below.

Directory Traversal in Robocode's CacheCleaner Component

Also known as[GHSA-j8r2-47rx-qhw4](/vulnerability/GHSA-j8r2-47rx-qhw4)

Published

Dec 9, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   A successful exploit gives an attacker total control of the affected component, not partial access.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-14306.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

1.1%probability of exploitation in next 30 days

Lower Risk\-0.01%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

0.14%0.62%1.10%1.57%0.7%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

☕`net.sf.robocode:robocode.core`

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

## Description

A directory traversal vulnerability exists in the CacheCleaner component of Robocode version 1.9.3.6. The recursivelyDelete method fails to properly sanitize file paths, allowing attackers to traverse directories and delete arbitrary files on the system. This vulnerability can be exploited by submitting specially crafted inputs that manipulate the file path, leading to potential unauthorized file deletions. [https://robo-code.blogspot.com/](https://robo-code.blogspot.com/)

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

☕Maven

`net.sf.robocode:robocode.core` 

all versions

1.9.5.6`net.sf.robocode:robocode.core:1.9.5.6`

## Affected Products

1 product · 1 configurations

Application

`robocode`robocode

1 version

1.9.3.6

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.robocode:robocode.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update net.sf.robocode:robocode.core to 1.9.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14306 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
    

## Frequently Asked Questions

A directory traversal vulnerability exists in the CacheCleaner component of Robocode version 1.9.3.6. The recursivelyDelete method fails to properly sanitize file paths, allowing attackers to traverse directories and delete arbitrary files on the system. This vulnerability can be exploited by submitting specially crafted inputs that manipulate the file path, leading to potential unauthorized file deletions. https://robo-code.blogspot.com/

O3 Security · Impact-Aware SCA

### Is CVE-2025-14306 in your dependencies?

Find it across Maven, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)