Skip to content
major vulnerability· requires attention

RCE via insecure deserialization in a widely used integration library (Apache Camel PQC).

Applications

CVE-2026-43867

9.8
Critical
EPSS 0.93%Patch availableJul 7, 2026

CRITICAL: Camel PQC deserialization leads to remote code execution.

common questions

Is CVE-2026-43867 being exploited?

Not confirmed. CVE-2026-43867 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.93% probability of exploitation in the next 30 days.

How severe is CVE-2026-43867?

CVE-2026-43867 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-43867?

Yes. A fix has been recorded for CVE-2026-43867. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43867 affect?

CVE-2026-43867 affects Apache Camel PQC Component. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43867?

Upgrade to 4.21.0; enforce least-privilege on Secrets Manager.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Camel PQC Component
impact

Remote code execution via deserializing crafted AWS Secrets Manager metadata during key lifecycle.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Camel
  • affected>= 4.18.0 and < 4.18.3
  • affected>= 4.19.0 and < 4.21.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free