VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

net.sf.robocode:robocode.core: vulnerability history, versions and safety

net.sf.robocode:robocode.core is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 14 releases, from May 2022 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 09 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all net.sf.robocode:robocode.core vulnerabilities

Vulert verdict on net.sf.robocode:robocode.core 1.11.1 i

Updated on 23 Oct 2026

Good news: 1.11.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 1.11.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.11.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.11.1 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 09 Dec 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 6 packages i
  • Stars 816 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for net.sf.robocode:robocode.core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.11.1 13 Jul 2026 none non-standard — Details →
1.10.3 18 May 2026 none non-standard — Details →
1.10.1 09 Dec 2025 none non-standard — Details →
1.10.0 04 Jun 2025 none non-standard — Details →
1.9.5.6 30 May 2025 none non-standard — Details →
1.9.5.5 29 Mar 2025 C1 non-standard Yes Details →
1.9.5.4 30 Sep 2024 C1 non-standard Yes Details →
1.9.5.3 11 Sep 2024 C1 non-standard Yes Details →
1.9.5.2 24 Oct 2023 C1 non-standard Yes Details →
1.9.5.1 30 Jul 2023 C1 non-standard Yes Details →
1.9.5.0 26 Feb 2023 C1 non-standard Yes Details →
1.9.4.8 29 Nov 2022 C1 non-standard Yes Details →
1.9.4.7 06 Aug 2022 C1 non-standard Yes Details →
1.9.4.6 15 Jun 2022 C1 non-standard Yes Details →
1.9.4.5 22 Mar 2022 C1 non-standard Yes Details →
1.9.4.3 05 Sep 2021 C1 non-standard Yes Details →
1.9.4.2 10 May 2021 C1 non-standard Yes Details →
1.9.4.1 09 Apr 2021 C1 non-standard Yes Details →
1.9.4.0 28 Feb 2021 C1 non-standard Yes Details →

All 19 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for net.sf.robocode:robocode.core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-14306: Directory Traversal Vulnerability in Robocode Core Package 10.0 critical 1.9.5.6 09 Dec 2025
CVE-2007-6382: Robocode Arbitrary Code Execution N/A medium 1.5.1 01 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About net.sf.robocode:robocode.core

Is net.sf.robocode:robocode.core safe to use?

Vulert records 2 vulnerabilities for net.sf.robocode:robocode.core in Maven: 1 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is net.sf.robocode:robocode.core's Vulert package health score?

Vulert scores net.sf.robocode:robocode.core 72/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of net.sf.robocode:robocode.core affected?

No. 1.11.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of net.sf.robocode:robocode.core should I use?

1.11.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does net.sf.robocode:robocode.core have?

2 vulnerabilities are recorded for net.sf.robocode:robocode.core in the Maven ecosystem: 1 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new net.sf.robocode:robocode.core vulnerabilities disclosed?

1 vulnerability was recorded for net.sf.robocode:robocode.core in the last 12 months, and the oldest entry in this database dates to 01 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of net.sf.robocode:robocode.core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor net.sf.robocode:robocode.core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the net.sf.robocode:robocode.core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.