How severe is CVE-2020-13931?

CVE-2020-13931 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-13931?

CVE-2020-13931 affects the following packages: org.apache.tomee:apache-tomee (Maven), org.apache.tomee:apache-tomee (Maven), org.apache.tomee:apache-tomee (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-13931?

Update org.apache.tomee:apache-tomee to 8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13931 is resolved across your whole dependency graph.

How do I detect CVE-2020-13931 in my Maven dependencies?

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

How do I mitigate CVE-2020-13931 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-2020-13931 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-13931 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-2020-13931?

CVE-2020-13931 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 89th 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.

When was CVE-2020-13931 published, and has it been updated?

CVE-2020-13931 was published on December 18, 2020 and was last updated on July 8, 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

CRITICAL severity

CVE-2020-13931 — apache-tomee

CRITICAL

CVE-2020-13931 is a critical-severity (CVSS 9.8) vulnerability in org.apache.tomee:apache-tomee. A fix is available for org.apache.tomee:apache-tomee — see the affected versions and patch details below.

Remote code execution in Apache TomEE

Also known asGHSA-mp28-rq7g-qx62

Published

Dec 18, 2020

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-13931 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.apache.tomee:apache-tomee☕org.apache.tomee:apache-tomee☕org.apache.tomee:apache-tomee

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

If Apache TomEE 8.0.0-M1 - 8.0.3, 7.1.0 - 7.1.3, 7.0.0-M1 - 7.0.8, 1.0.0 - 1.7.5 is configured to use the embedded ActiveMQ broker, and the broker config is misconfigured, a JMX port is opened on TCP port 1099, which does not include authentication. CVE-2020-11969 previously addressed the creation of the JMX management interface, however the incomplete fix did not cover this edge case.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomee:apache-tomee`	≥ 8.0.0&&< 8.0.4	8.0.4`org.apache.tomee:apache-tomee:8.0.4`
☕Maven	`org.apache.tomee:apache-tomee`	≥ 7.1.0&&< 7.1.4	7.1.4`org.apache.tomee:apache-tomee:7.1.4`
☕Maven	`org.apache.tomee:apache-tomee`	all versions	7.0.9`org.apache.tomee:apache-tomee:7.0.9`

Affected Products

1 product · 8 configurations

Application

tomeeapache

≥ 8.0.0 && ≤ 8.0.3

2 versions

7.0.08.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomee:apache-tomee, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomee:apache-tomee to 8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13931 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

O3 Security · Impact-Aware SCA

Is CVE-2020-13931 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works