Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2020-11969 — tomee

CRITICAL

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

Missing Authentication for Critical Function in Apache TomEE

Also known asGHSA-836g-5fr5-fgcr
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
0.21%1.81%3.41%5.02%1.1%4.1%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

4 pkgs affected
☕org.apache.tomee:tomee☕org.apache.tomee:tomee☕org.apache.tomee:tomee☕org.apache.tomee: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 is configured to use the embedded ActiveMQ broker, and the broker URI includes the useJMX=true parameter, a JMX port is opened on TCP port 1099, which does not include authentication. This affects Apache TomEE 8.0.0-M1 - 8.0.1, Apache TomEE 7.1.0 - 7.1.2, Apache TomEE 7.0.0-M1 - 7.0.7, Apache TomEE 1.0.0 - 1.7.5.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomee:tomee≥ 8.0.0-M1&&< 8.0.28.0.2org.apache.tomee:tomee:8.0.2
☕Mavenorg.apache.tomee:tomee≥ 7.1.0&&< 7.1.37.1.3org.apache.tomee:tomee:7.1.3
☕Mavenorg.apache.tomee:tomee≥ 7.0.0-M1&&< 7.0.87.0.8org.apache.tomee:tomee:7.0.8
☕Mavenorg.apache.tomee:tomee≥ 1.0.0&&< 1.7.61.7.6org.apache.tomee:tomee:1.7.6

Affected Products

1 product · 8 configurations
Application
tomeeapache
≥ 8.0.0 && ≤ 8.0.1
2 versions
7.0.08.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

If Apache TomEE is configured to use the embedded ActiveMQ broker, and the broker URI includes the useJMX=true parameter, a JMX port is opened on TCP port 1099, which does not include authentication. This affects Apache TomEE 8.0.0-M1 - 8.0.1, Apache TomEE 7.1.0 - 7.1.2, Apache TomEE 7.0.0-M1 - 7.0.7, Apache TomEE 1.0.0 - 1.7.5.
O3 Security · Impact-Aware SCA

Is CVE-2020-11969 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-11969: tomee — Fixed in 8.0.2