CVE-2026-43866

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2026-41855 (ENISA EUVD) · GHSA-f755-xp6r-8q84 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component.

JmsBinding.extractBodyFromJms() in camel-jms - and the equivalent JmsBinding in camel-sjms - deserializes the payload of an incoming JMS ObjectMessage via jakarta.jms.ObjectMessage.getObject() whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer. The CVE-2026-40860 hardening added a post-deserialization class check that rejects classes outside the default allow-list java.;javax.;org.apache.camel.;!*. However org.apache.camel.support.DefaultExchangeHolder itself lives in the allow-listed org.apache.camel. namespace, so an ObjectMessage whose top-level object is a DefaultExchangeHolder passes the check. The receiving side then calls DefaultExchangeHolder.unmarshal() on it without requiring the transferExchange option to be enabled - an asymmetric trust boundary, since the sending side gates ObjectMessage and transferExchange handling but the receiving side did not - writing every non-null field of the holder into the Exchange: the message body, the IN and OUT headers, the exchange properties, the variables, the exchange id and the exception. An attacker who can publish an ObjectMessage to a queue or topic consumed by an affected Camel application can therefore inject arbitrary Exchange state using only universally-trusted java.lang and java.util types, with no deserialization gadget chain required, to manipulate routing and headers, exchange properties and error handling. The same handling applies to camel-sjms and camel-sjms2, and to the JMS-family components built on JmsComponent and JmsBinding: camel-amqp, camel-activemq and camel-activemq6. This is a bypass of the CVE-2026-40860 fix rather than a flaw in it. This issue affects Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0; Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.

Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, JMS ObjectMessage handling is disabled by default in camel-jms, camel-sjms and the JMS-family components (a new objectMessageEnabled option defaults to false at the component and endpoint level), so an incoming ObjectMessage - including a DefaultExchangeHolder payload - is no longer deserialized unless the option is explicitly enabled; only set objectMessageEnabled=true when the consumed JMS destination is fed exclusively by trusted producers. For deployments that cannot upgrade immediately, restrict publish access to the queues and topics consumed by Camel to trusted producers via JMS broker authorization, and do not expose JMS consumers that map ObjectMessage bodies to untrusted networks; a JMS-provider deserialization allow-list does not mitigate this specific bypass because the crafted payload uses only universally-trusted classes.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 6, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
Patch available.
Web page

Apache Camel Security Advisory - CVE-2026-43866 - Apache Camel

https://camel.apache.org/security/CVE-2026-43866.html

Vendor Advisories for CVE-2026-43866(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcamel-jms2026-08-13redhat
mavenorg.apache.camel:camel-activemq @ 4.14.8 (fixes >= 3.0.0, < 4.14.8)—ghsa
mavenorg.apache.camel:camel-activemq @ 4.21.0 (fixes >= 4.19.0, < 4.21.0)—ghsa
mavenorg.apache.camel:camel-activemq @ 4.18.3 (fixes >= 4.15.0, < 4.18.3)—ghsa

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

(6 across 1 ecosystem)
Maven(6)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-activemq4.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—
org.apache.camel:camel-activemq64.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—
org.apache.camel:camel-amqp4.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—
org.apache.camel:camel-jms4.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—
org.apache.camel:camel-sjms4.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—
org.apache.camel:camel-sjms24.19.0, 4.20.0
  • 3.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 278 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 178 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 00:39 UTCEG score recompute
  2. 2026-11-02 00:39 UTCVendor advisory
  3. 2026-11-02 00:39 UTCGHSA enrichmentGHSA-f755-xp6r-8q84 · GitHub severity HIGH · GitHub CVSS 7.3
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-25 15:28 UTCVendor advisory
  13. 2026-10-25 14:28 UTCEG score recompute
  14. 2026-10-24 23:19 UTCEG score recompute
  15. 2026-10-24 23:19 UTCVendor advisory
  16. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-18 03:39 UTCEG score recompute
  24. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-17 14:08 UTCEG score recompute
Show 75 more
  1. 2026-10-17 14:08 UTCVendor advisory
  2. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-10-13 13:54 UTCOSV refresh
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  8. 2026-10-12 16:05 UTCEG score recompute
  9. 2026-10-11 19:47 UTCEG score recompute
  10. 2026-10-11 17:02 UTCEG score recompute
  11. 2026-10-11 14:28 UTCEG score recompute
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  15. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  17. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  26. 2026-09-23 06:25 UTCEG score recompute
  27. 2026-09-23 06:25 UTCVendor advisory
  28. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  29. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  30. 2026-09-18 06:02 UTCEG score recompute
  31. 2026-09-18 06:02 UTCVendor advisory
  32. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  33. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  34. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  35. 2026-09-13 23:57 UTCEG score recompute
  36. 2026-09-13 23:57 UTCVendor advisory
  37. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  38. 2026-09-13 08:45 UTCEG score recompute
  39. 2026-09-13 08:45 UTCVendor advisory
  40. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-09-12 13:39 UTCEG score recompute
  42. 2026-09-12 13:39 UTCVendor advisory
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  45. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-09-06 14:11 UTCEG score recompute
  49. 2026-09-06 14:11 UTCVendor advisory
  50. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  51. 2026-09-05 23:13 UTCEG score recompute
  52. 2026-09-05 23:13 UTCVendor advisory
  53. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  54. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  55. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  56. 2026-08-30 20:58 UTCEG score recompute
  57. 2026-08-30 20:58 UTCVendor advisory
  58. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  59. 2026-08-30 08:26 UTCEG score recompute
  60. 2026-08-30 08:26 UTCVendor advisory
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  62. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  63. 2026-08-27 21:59 UTCEG score recompute
  64. 2026-08-27 21:59 UTCVendor advisory
  65. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  66. 2026-08-27 02:27 UTCEG score recompute
  67. 2026-08-27 02:27 UTCVendor advisory
  68. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  69. 2026-08-26 13:56 UTCEG score recompute
  70. 2026-08-26 13:56 UTCVendor advisory
  71. 2026-08-26 13:56 UTCGHSA enrichmentGHSA-f755-xp6r-8q84 · GitHub severity HIGH · GitHub CVSS 7.3
  72. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  73. 2026-08-25 12:02 UTCVendor advisory
  74. 2026-08-25 12:02 UTCGHSA enrichmentGHSA-f755-xp6r-8q84 · GitHub severity HIGH · GitHub CVSS 7.3
  75. 2026-08-24 22:35 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

3 shown

Maven:org.apache.camel:camel-activemq · Maven:org.apache.camel:camel-amqp · Maven:org.apache.camel:camel-jms

Frequently asked(5)

What is CVE-2026-43866?
CVE-2026-43866 is a high-severity vulnerability; its CVE record was published on July 6, 2026. Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component. JmsBinding.extractBodyFromJms() in camel-jms - and the equivalent JmsBinding in camel-sjms - deserializes the payload of an incoming JMS ObjectMessage via jakarta.jms.ObjectMessage.getObject() whenever the…
When was the CVE record for CVE-2026-43866 published?
The CVE record for CVE-2026-43866 was published on July 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-43866 actively exploited?
CVE-2026-43866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43866?
CVE-2026-43866 has a CVSS v3.1 base score of 7.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-43866?
A fix for CVE-2026-43866 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43866 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43866

Explore →

Is Your Infrastructure Affected by CVE-2026-43866?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs