How severe is CVE-2013-2027?

No CVSS score has been assigned to CVE-2013-2027 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-2027?

CVE-2013-2027 affects the following packages: org.python:jython-standalone (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-2027?

Update org.python:jython-standalone to 2.7.2b3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2027 is resolved across your whole dependency graph.

How do I detect CVE-2013-2027 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.python:jython-standalone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2027 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-2027 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-2027 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-2027?

CVE-2013-2027 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-2027?

CVE-2013-2027 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-2027 published, and has it been updated?

CVE-2013-2027 was published on February 13, 2015 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-2027 — jython-standalone

Fix: jython/frozen-mirror@053949e

CVE-2013-2027 is a CWE-264 vulnerability in org.python:jython-standalone. A fix is available for org.python:jython-standalone — see the affected versions and patch details below.

Jython Improper Access Restrictions vulnerability

Also known asGHSA-9347-9w64-q5wp

Published

Feb 13, 2015

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.python:jython-standalone

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

Jython before 2.7.2b3 uses the current umask to set the privileges of the class cache files, which allows local users to bypass intended access restrictions via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.python:jython-standalone`	all versions	2.7.2b3`org.python:jython-standalone:2.7.2b3`

Affected Products

2 products · 3 configurations

Application

jythonjython_project

1 version

2.2.1

opensuseopensuse

2 versions

13.113.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.python:jython-standalone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.python:jython-standalone to 2.7.2b3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2027 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Jython before 2.7.2b3 uses the current umask to set the privileges of the class cache files, which allows local users to bypass intended access restrictions via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2013-2027 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works