CVE-2026-56140 json
Apache Camel AWS2 SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy to align it with sibling components
published 2026-07-06 4 mo ago modified 2026-08-26 2 mo ago also EUVD-2026-41852 , GHSA-w2v8-8q6c-3rhr
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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. For the related camel-aws2-sqs component this inbound gap was exploitable, because the Sqs2Consumer maps inbound SQS message attributes into the Camel Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, allowing a message sender to inject Camel control headers (tracked as CVE-2026-46456). camel-aws2-sns, by contrast, is producer-only: Sns2Endpoint does not support consumers (createConsumer throws UnsupportedOperationException, 'You cannot receive messages from this endpoint'), so no externally-supplied message attributes are ever mapped inbound into a Camel Exchange through SNS, and the missing inbound filter rule on Sns2HeaderFilterStrategy was therefore not reachable by an attacker. 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 issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
This is a defense-in-depth hardening change with no known exploit path in camel-aws2-sns, which is producer-only, so no urgent action or workaround is required. 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.
Patch / fix
- maven org.apache.camel:camel-aws2-sns 4.14.8, 4.18.3, 4.21.0
- Apache Software Foundation Apache Camel AWS2 SNS 4.14.8, 4.18.3, 4.21.0
- github.com/apache/camel@5f57258 commit
- github.com/apache/camel@7b334be commit
- github.com/apache/camel@b7f7829 commit
- github.com/apache/camel#23221 pull request
- github.com/apache/camel#23357 pull request
- github.com/apache/camel#23373 pull request
- github.com/apache/camel/releases/tag/camel-4.14.8 release
- github.com/apache/camel/releases/tag/camel-4.18.3 release
- github.com/apache/camel/releases/tag/camel-4.21.0 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-56140 updated cvss 0.0
org.apache.camel/camel-aws2-sns: Apache Camel AWS SNS Component: Defense-in-depth hardening due to improper input validation
-
Red Hat OpenShift Serverless openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 Red Hat build of Apache Camel 4 for Quarkus 3 camel-aws2-sns 4.18.1.redhat-00026 Red Hat build of Apache Camel for Spring Boot 4 camel-aws2-sns 4.18.1.redhat-00026 Red Hat JBoss Enterprise Application Platform Expansion Pack camel-aws2-sns 4.18.1.redhat-00026not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.camel:camel-aws2-sns | >=4.0.0, <4.14.8 >=4.15.0, <4.18.3 >=4.19.0, <4.21.0 |
4.14.8 4.18.3 4.21.0 |
Affected products
- Apache Software Foundation Apache Camel AWS2 SNS
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/apache/camel/pull/23221
web
-
github.com
/apache/camel/pull/23357
web
-
github.com
/apache/camel/pull/23373
web
-
github.com
/apache/camel/commit/5f57258fb33d33ef99df10594f8fe9f11d7c2b7e
web
-
github.com
/apache/camel/commit/7b334be0419839097a132d4ff3427fc4083e695e
web
-
github.com
/apache/camel/commit/b7f78292e747a28dbf5da444265557b5f9f3c1a1
web
-
camel.apache.org
/security/CVE-2026-56140.html
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-56140
advisory
-
github.com
/apache/camel
package
-
github.com
/apache/camel/releases/tag/camel-4.14.8
web
-
github.com
/apache/camel/releases/tag/camel-4.18.3
web
-
github.com
/apache/camel/releases/tag/camel-4.21.0
web
-
issues.apache.org
/jira/browse/CAMEL-23506
web
Sources
- CVE List CVE-2026-56140
- GitHub Advisory GHSA-w2v8-8q6c-3rhr
- NVD CVE-2026-56140
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.