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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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.

How does O3 Security protect against CVE-2020-13931?

O3 pinpoints whether CVE-2020-13931 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

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

CRITICAL

CVE-2020-13931 is a critical-severity (CVSS 9.8) vulnerability in org.apache.tomee:apache-tomee. O3 Security confirms whether CVE-2020-13931 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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 Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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
☕Maven	`org.apache.tomee:apache-tomee`	≥ 7.1.0&&< 7.1.4	7.1.4
☕Maven	`org.apache.tomee:apache-tomee`	all versions	7.0.9

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether CVE-2020-13931 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-13931. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-13931 in your dependencies?

O3 detects CVE-2020-13931 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works