A flaw was found in camel-infinispan. This vulnerability involves unsafe deserialization in the ProtoStream remote aggregation repository. A remote attacker with low privileges could exploit this by sending specially crafted data, leading to arbitrary code execution. This allows the attacker to gain full control over the affected system, impacting its confidentiality, integrity, and availability.
CVE-2026-6857
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 28% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 47.5%
- KEV
- Not listed
Published
April 22, 2026
Last Modified
June 30, 2026
Advisory Details (4)
Auto-updated Jun 7, 20262460003 – (CVE-2026-6857) CVE-2026-6857 camel-infinispan: camel-infinispan: Remote Code Execution via Unsafe Deserialization
https://bugzilla.redhat.com/show_bug.cgi?id=2460003Vendor Advisories for CVE-2026-6857(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:22453Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 update is now available (RHBQ 3.33.1.GA)
- RHSA-2026:17668Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Build of Apache Camel 4.18.1 for Spring Boot release.
- GHSA-xfxp-ppx7-cqrpGitHub Security AdvisoriesHigh
camel-infinispan Vulnerable to Deserialization of Untrusted Data
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | patch | 2026-06-02 | redhat |
| redhat | camel-infinispan | 2026-05-14 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.apache.camel:camel-infinispan | 2.13.0 ... 4.9.0 (224 versions) | 4.20.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 49× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 112 total refreshes for this CVE.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 05:21 UTCEG score recompute
- 2026-06-15 05:21 UTCVendor advisory
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 16:56 UTCEG score recompute
- 2026-06-14 16:56 UTCVendor advisory
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 03:14 UTCEG score recompute
- 2026-06-12 03:14 UTCVendor advisory
- 2026-06-11 14:51 UTCEG score recompute
- 2026-06-11 14:51 UTCVendor advisory
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 22:19 UTCEPSS rescore
- 2026-06-10 17:08 UTCEG score recompute
- 2026-06-10 17:08 UTCVendor advisory
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 04:39 UTCEG score recompute
- 2026-06-10 04:39 UTCVendor advisory
- 2026-06-09 16:14 UTCEG score recompute
- 2026-06-09 16:14 UTCVendor advisory
- 2026-06-09 03:51 UTCEG score recompute
- 2026-06-09 03:51 UTCVendor advisory
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 13:03 UTCEG score recompute
- 2026-06-08 13:03 UTCVendor advisory
- 2026-06-08 00:40 UTCEG score recompute
- 2026-06-08 00:40 UTCVendor advisory
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 12:16 UTCEG score recompute
- 2026-06-07 12:16 UTCVendor advisory
- 2026-06-06 23:53 UTCEG score recompute
- 2026-06-06 23:53 UTCVendor advisory
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 05:45 UTCEG score recompute
- 2026-06-06 05:45 UTCVendor advisory
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 17:19 UTCEG score recompute
- 2026-06-05 17:19 UTCVendor advisory
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 03:35 UTCEG score recompute
- 2026-06-05 03:35 UTCVendor advisory
- 2026-06-04 14:08 UTCEG score recompute
- 2026-06-04 14:08 UTCVendor advisory
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 01:09 UTCEG score recompute
- 2026-06-04 01:09 UTCVendor advisory
- 2026-06-03 12:43 UTCEG score recompute
- 2026-06-03 12:43 UTCVendor advisory
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 17:22 UTCEG score recompute
- 2026-06-02 17:22 UTCVendor advisory
- 2026-06-02 04:58 UTCEG score recompute
- 2026-06-02 04:58 UTCVendor advisory
- 2026-06-01 15:15 UTCEG score recompute
- 2026-06-01 15:15 UTCVendor advisory
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-6857?
When was CVE-2026-6857 disclosed?
Is CVE-2026-6857 actively exploited?
What is the CVSS score of CVE-2026-6857?
How do I remediate CVE-2026-6857?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6857
Is Your Infrastructure Affected by CVE-2026-6857?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.