GHSA-qqfc-m9hc-pqv3 — infinispan-core
HIGHGHSA-qqfc-m9hc-pqv3 is a high-severity (CVSS 8.8) CWE-349 vulnerability in org.infinispan:infinispan-core. A fix is available for org.infinispan:infinispan-core — see the affected versions and patch details below.
Deserialization of Untrusted Data in Infinispan
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-qqfc-m9hc-pqv3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.infinispan:infinispan-core☕org.infinispan:infinispan-core☕org.infinispan:infinispan-core☕org.infinispan:infinispan-core☕org.infinispan:infinispan-coreReal-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
Infinispan permits improper deserialization of trusted data via XML and JSON transcoders under certain server configurations. A user with authenticated access to the server could send a malicious object to a cache configured to accept certain types of objects, achieving code execution and possible further attacks. Versions 9.0.3.Final, 9.1.7.Final, 8.2.10.Final, 9.2.2.Final, 9.3.0.Alpha1 are believed to be affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.infinispan:infinispan-core | all versions | No fix |
| ☕Maven | org.infinispan:infinispan-core | all versions | No fix |
| ☕Maven | org.infinispan:infinispan-core | all versions | No fix |
| ☕Maven | org.infinispan:infinispan-core | all versions | No fix |
| ☕Maven | org.infinispan:infinispan-core | ≥ 9.3.0.Alpha1&&< 9.3.1.Final | 9.3.1.Finalorg.infinispan:infinispan-core:9.3.1.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.infinispan:infinispan-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.infinispan:infinispan-core has shipped for GHSA-qqfc-m9hc-pqv3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qqfc-m9hc-pqv3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-qqfc-m9hc-pqv3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Data Grid | infinispan | RHSA-2018:1833 |
| Red Hat Fuse 7.5.0 | camel | RHSA-2019:3892 |
Frequently Asked Questions
Is GHSA-qqfc-m9hc-pqv3 in your dependencies?
O3 Security finds GHSA-qqfc-m9hc-pqv3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.