CVE-2026-56140
Defense-in-depth fix for Camel AWS SNS header filtering; no inbound exposure
Is CVE-2026-56140 being exploited?
Not confirmed. CVE-2026-56140 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.74% probability of exploitation in the next 30 days.
How severe is CVE-2026-56140?
CVE-2026-56140 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-56140?
Yes. A fix has been recorded for CVE-2026-56140. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56140 affect?
CVE-2026-56140 affects Apache Camel camel-aws2-sns component (aws SNS) 4.x before fixes (4.14.8/4.18.3/4.21.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56140?
Upgrade to fixed camel-aws2-sns (4.21.0+) and apply least-privilege IAM.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
No known exploit path; producer-only SNS prevents inbound header mapping; minimal risk
Monitor only
- affected>= 4.0.0 and < 4.14.8
- affected>= 4.15.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.