How severe is CVE-2020-11975?

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

Which packages are affected by CVE-2020-11975?

CVE-2020-11975 affects the following packages: org.apache.unomi:unomi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-11975?

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

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

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

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

Yes. There are 3 known exploit references for CVE-2020-11975, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-11975?

CVE-2020-11975 has an EPSS (Exploit Prediction Scoring System) score of 30.6%, placing it in the 98th 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 warrants monitoring and prompt remediation.

Is there exploit tooling available for CVE-2020-11975?

A Nuclei detection template exists for CVE-2020-11975, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2020-11975 was published on June 5, 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-11975 — unomi

CRITICAL

CVE-2020-11975 is a critical-severity (CVSS 9.8) vulnerability in org.apache.unomi:unomi. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.unomi:unomi — see the affected versions and patch details below.

Improper Input Validation in Apache Unomi

Also known asGHSA-v6fq-q792-j46j

Published

Jun 5, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

30.6%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

1 pkg affected

☕org.apache.unomi:unomi

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

Apache Unomi allows conditions to use OGNL scripting which offers the possibility to call static Java classes from the JDK that could execute code with the permission level of the running Java process.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.unomi:unomi`	all versions	1.5.4`org.apache.unomi:unomi:1.5.4`

Affected Products

1 product · 1 configurations

Application

unomiapache

< 1.5.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Apache Unomi allows conditions to use OGNL scripting which offers the po…

github.comGithubNov 2020

Apache Unomi allows conditions to use OGNL scripting which offers the po…

github.comAPIDec 2020

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.unomi:unomi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.unomi:unomi to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11975 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 to detect CVE-2020-11975

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-11975 -u https://target

Template: Apache Unomi - Remote Code Execution
Severity: critical
Impact: Successful exploitation allows an attacker to execute arbitrary code on the server with the privileges of the Java process, potentially leading to complete system compromise.
Remediation: Update Apache Unomi to version 1.5.2 or later. Disable OGNL scripting in conditions if not required.

Template by ProjectDiscovery nuclei-templates (Sourabh-Sahu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-11975 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works