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

CVE-2016-11024 — odata4j-core

CRITICAL

CVE-2016-11024 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in org.odata4j:odata4j-core. No vendor fix is recorded yet; mitigation options are listed below.

SQL Injection in odata4j

Also known asGHSA-f96g-24cg-f24w
Published
Updated
Affected
3 pkgs
Patched
See advisory
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.64%1.27%1.91%0.3%1.4%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2016-11024 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.odata4j:odata4j-core☕org.odata4j:odata4j-dist☕org.odata4j:odata4j-parent

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

odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.

Affected Packages

3 total
EcosystemPackageVulnerable rangeFix
☕Mavenorg.odata4j:odata4j-coreall versionsNo fix
☕Mavenorg.odata4j:odata4j-distall versionsNo fix
☕Mavenorg.odata4j:odata4j-parentall versionsNo fix

Affected Products

1 product · 1 configurations
Application
odata4jodata4j_project
1 version
0.7

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.odata4j:odata4j-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of org.odata4j:odata4j-core has shipped for CVE-2016-11024 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.
O3 Security · Impact-Aware SCA

Is CVE-2016-11024 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2016-11024: odata4j-core: SQL Injection in odata4j