Vulnerability Database · Maven · Package report

org.python:jython-standalone: vulnerability history, versions and safety

org.python:jython-standalone is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 20 releases, first recorded in May 2022. 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
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.python:jython-standalone 2.7.5b1 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.7.5b1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 1,549 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 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 org.python:jython-standalone, 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
2.7.5b1 18 Aug 2026 none non-standard — Details →
2.7.4 18 Aug 2024 none non-standard — Details →
2.7.4rc1 31 Jul 2024 none non-standard — Details →
2.7.4b2 05 May 2024 none non-standard — Details →
2.7.4b1 02 Apr 2024 none non-standard — Details →
2.7.3 11 Sep 2022 none non-standard — Details →
2.7.3rc1 28 Aug 2022 none non-standard — Details →
2.7.3b1 09 Jul 2022 none non-standard — Details →
2.7.2 21 Mar 2020 none non-standard — Details →
2.7.2rc1 01 Mar 2020 none non-standard — Details →
2.7.2b3 02 Feb 2020 none non-standard — Details →
2.7.2b2 01 Nov 2019 M1 non-standard Yes Details →
2.7.1 30 Jun 2017 M1 non-standard Yes Details →
2.7.1-rc3 17 Jun 2017 C1 M1 non-standard Yes Details →
2.7.1-rc2 29 May 2017 C1 M1 non-standard Yes Details →
2.7.1b3 03 Feb 2016 C1 M1 non-standard Yes Details →
2.7.1b2 12 Oct 2015 C1 M1 non-standard Yes Details →
2.7.1b1 11 Sep 2015 C1 M1 non-standard Yes Details →
2.7.0 29 Apr 2015 C1 M1 non-standard Yes Details →
2.7-rc3 21 Apr 2015 C1 M1 non-standard Yes Details →
2.7-rc2 03 Apr 2015 C1 M1 non-standard Yes Details →
2.7-rc1 25 Mar 2015 C1 M1 non-standard Yes Details →
2.7-b4 13 Feb 2015 C1 M1 non-standard Yes Details →
2.7-b3 04 Aug 2014 C1 M1 non-standard Yes Details →
2.7-b2 23 Apr 2014 C1 M1 non-standard Yes Details →
2.7-b1 09 Feb 2013 C1 M1 non-standard Yes Details →
2.5.4-rc1 08 Feb 2013 C1 M1 non-standard Yes Details →
2.5.3 13 Aug 2012 C1 M1 non-standard Yes Details →
2.5.3-rc1 07 Aug 2012 C1 M1 non-standard Yes Details →
2.5.2 26 Jun 2011 C1 M1 non-standard Yes Details →
2.5.1 23 Jun 2011 C1 M1 non-standard Yes Details →

All 31 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.python:jython-standalone

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 org.python:jython-standalone

Is org.python:jython-standalone safe to use?

Vulert records 2 vulnerabilities for org.python:jython-standalone 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 org.python:jython-standalone's Vulert package health score?

Vulert scores org.python:jython-standalone 71/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 org.python:jython-standalone affected?

No. 2.7.5b1, 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 org.python:jython-standalone should I use?

2.7.5b1 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 org.python:jython-standalone have?

2 vulnerabilities are recorded for org.python:jython-standalone 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 org.python:jython-standalone vulnerabilities disclosed?

0 vulnerabilities were recorded for org.python:jython-standalone in the last 12 months, and the oldest entry in this database dates to 13 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 org.python:jython-standalone 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 org.python:jython-standalone for upcoming vulnerabilities?

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