How severe is CVE-2020-11972?

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

Which packages are affected by CVE-2020-11972?

CVE-2020-11972 affects the following packages: org.apache.camel:camel-rabbitmq (Maven), org.apache.camel:camel-rabbitmq (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-11972?

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

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

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

How do I mitigate CVE-2020-11972 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2020-11972 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-11972 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2020-11972 has an EPSS (Exploit Prediction Scoring System) score of 5.7%, placing it in the 93th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-11972?

CVE-2020-11972 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2020-11972 was published on May 14, 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-11972 — camel-rabbitmq

CRITICAL

CVE-2020-11972 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.camel:camel-rabbitmq. A fix is available for org.apache.camel:camel-rabbitmq — see the affected versions and patch details below.

Deserialization of Untrusted Data in Apache Camel RabbitMQ

Also known asGHSA-2x6r-7427-95cm

Published

May 14, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

5.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-11972 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

2 pkgs affected

☕org.apache.camel:camel-rabbitmq☕org.apache.camel:camel-rabbitmq

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 Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-rabbitmq`	all versions	2.25.1`org.apache.camel:camel-rabbitmq:2.25.1`
☕Maven	`org.apache.camel:camel-rabbitmq`	≥ 3.0.0&&< 3.2.0	3.2.0`org.apache.camel:camel-rabbitmq:3.2.0`

Affected Products

4 products · 7 configurations

Application

camelapache

≥ 3.0.0 && ≤ 3.1.0

range

Application

communications diameter signaling routeroracle

≥ 8.0.0 && ≤ 8.2.2

range

Application

enterprise manager base platformoracle

2 versions

13.3.0.013.4.0.0

Application

flexcube private bankingoracle

2 versions

12.0.012.1.0

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.camel:camel-rabbitmq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-rabbitmq to 2.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11972 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Fuse 7.8.0	`camel-rabbitmq`	RHSA-2020:5568

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-11972 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

May 14, 2020

Last updated

Jul 8, 2026

Identifiers

CVE-2020-11972

GHSA-2x6r-7427-95cm

References

Advisoryopenwall.com Advisoryopenwall.com Advisorycamel.apache.org Advisoryoracle.com Advisoryoracle.com Advisorynvd.nist.gov

Related vulnerabilities

This CVE is critical severity; 4 of 8 other CVEs with CWE-502 are rated as high or higher (top: critical).

CVE-2025-66455CVE-2025-59953CVE-2026-49400CVE-2026-50646CVE-2026-78683CVE-2026-79657GHSA-gqvg-gmmx-x4hmCVE-2026-55175Browse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2020-11972 — camel-rabbitmq

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-11972 in your dependencies?