CVE-2026-56140: Apache Camel AWS SNS Component: Defense-in-depth hardening due to improper input validation
Not in the CISA KEV catalog.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
CVE-2026-56140 key facts
- CISA KEV
- Not listed (catalog checked )
- Highest advisory severity
- Critical
- Fixed releases
- Red Hat: 4.21.0, 4.14.8, 4.14, 4.18.3, 4.18
- VulniPulse record
- Published · Updated
Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-56140; bulletin-wide values are not repeated here.
Is CVE-2026-56140 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-56140 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-56140?
Upgrade to a fixed release named by the vendor:
- Red Hat: 4.21.0, 4.14.8, 4.14, 4.18.3, 4.18
- No urgent action is required as there is no known exploit path. Users who want the aligned behavior can upgrade to Apache Camel 4.21.0, 4.14.8, or 4.18.3. (Red Hat)
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Vendor advisory comparison
Apache
1 advisory- Advisory severityCritical9.8
Critical [CVE-2026-46456 +1] Improper Input Validation vulnerability in Apache Camel AWS SNS component
CVE-2026-56140Source published Source updated
This bulletin covers 2 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.
Improper Input Validation vulnerability in Apache Camel AWS SNS component. The camel-aws2-sns component filters Camel headers through a component-specific HeaderFilterStrategy, Sns2HeaderFilterStrategy. Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule. As part of the same fix (CAMEL-23506), an inbound filter rule (setInFilterStartsWith for the Camel namespace) was added to Sns2HeaderFilterStrategy so that its configuration matches the corrected Sqs2HeaderFilterStrategy and the other sibling strategies. This is a defense-in-depth alignment with no known exploit path in camel-aws2-sns. This…
- Affected products in this advisory
- Apache Camel AWS
- Source-reported affected versions
- 4.0.0 through 4.14.8
- 4.15.0 through 4.18.3
- 4.19.0 through 4.21.0.
- Source-reported fixed versions
- 4.21.0
- 4.14.8
- 4.14.x
- 4.18.3
1 more entries in the full advisory.
- Mitigation guidance
- Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule.
- Users who want the aligned behaviour can upgrade to version 4.21.0, or to 4.14.8 on the 4.14.x LTS releases stream, or to 4.18.3 on the 4.18.x releases stream, which contain the change.
- As a general best practice, operators should continue to apply least-privilege IAM permissions on their SNS topics.
Red Hat
1 advisory- Advisory severityLow0.0
Low [CVE-2026-56140] Apache Camel AWS SNS Component: Defense-in-depth hardening due to improper input validation
CVE-2026-56140Source published Source updated
Improper Input Validation vulnerability in Apache Camel AWS SNS component. The camel-aws2-sns component filters Camel headers through a component-specific HeaderFilterStrategy, Sns2HeaderFilterStrategy. Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule. As part of the same fix (CAMEL-23506), an inbound filter rule (setInFilterStartsWith for the Camel namespace) was added to Sns2HeaderFilterStrategy so that its configuration matches the corrected Sqs2HeaderFilterStrategy and the other sibling strategies. This is a defense-in-depth alignment with no known exploit path in camel-aws2-sns. This…
- Affected products in this advisory
- No product details extracted. Check the source bulletin.
- Source-reported affected versions
- < 4.0.0
- < 4.14.8
- < 4.15.0
- < 4.18.3
2 more entries in the full advisory.
- Source-reported fixed versions
- 4.21.0
- 4.14.8
- 4.14
- 4.18.3
1 more entries in the full advisory.
- Mitigation guidance
- No urgent action is required as there is no known exploit path. Users who want the aligned behavior can upgrade to Apache Camel 4.21.0, 4.14.8, or 4.18.3.
More Apache advisories
- CVE-2026-90436Nov 6, 2026** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis
- CVE-2026-85111Nov 6, 2026Apache James denial of service
- CVE-2026-85108Nov 6, 2026Apache James Mime4J Core denial of service
- CVE-2026-76168Nov 6, 2026In Apache James server prior version 3.9.1 relying on the SieveFileRepository incorect
- CVE-2026-74756Nov 6, 2026Some docker-compose shipped by the project exposes by default Webadmin REST API publically
- CVE-2026-76171Nov 6, 2026Apache James SSRF
Follow CVE-2026-56140 in the free weekly digest
Every Monday: whether it was added to CISA KEV, reported exploited, got a fix or changed severity, plus the week's critical and high advisories.
Browse the latest tracked CVEs or the CVEs listed in CISA KEV.
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.