How severe is GHSA-v6fq-q792-j46j?

GHSA-v6fq-q792-j46j has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v6fq-q792-j46j?

GHSA-v6fq-q792-j46j affects the following packages: org.apache.unomi:unomi (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v6fq-q792-j46j?

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 GHSA-v6fq-q792-j46j is resolved across your whole dependency graph.

How do I detect GHSA-v6fq-q792-j46j in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.unomi:unomi. 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 GHSA-v6fq-q792-j46j 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 GHSA-v6fq-q792-j46j?

O3 pinpoints whether GHSA-v6fq-q792-j46j 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 GHSA-v6fq-q792-j46j actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-v6fq-q792-j46j, 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.

Is there exploit tooling available for GHSA-v6fq-q792-j46j?

A Nuclei detection template exists for GHSA-v6fq-q792-j46j, 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 GHSA-v6fq-q792-j46j published, and has it been updated?

GHSA-v6fq-q792-j46j was published on February 9, 2022 and was last updated on November 8, 2023. 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

GHSA-v6fq-q792-j46j

CRITICAL

GHSA-v6fq-q792-j46j is a critical-severity (CVSS 9.8) vulnerability in org.apache.unomi:unomi. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-v6fq-q792-j46j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Input Validation in Apache Unomi

Also known asCVE-2020-11975

Published

Feb 9, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

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

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

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. 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.unomi:unomi to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6fq-q792-j46j 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 GHSA-v6fq-q792-j46j 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 GHSA-v6fq-q792-j46j. 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 GHSA-v6fq-q792-j46j in your dependencies?

O3 detects GHSA-v6fq-q792-j46j 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