Answer in brief
CVE-2026-56140 records a Critical severity (CVSS 9.8) vulnerability in Apache Camel-AWS2-SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy. The current sources do not mark it as known exploited. The current feed maps org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven), org.apache.camel:camel-aws2-sns (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.camel:camel-aws2-snsmaven | >=4.0.0,<4.14.8 | 4.14.8 |
| org.apache.camel:camel-aws2-snsmaven | >=4.15.0,<4.18.3 | 4.18.3 |
| org.apache.camel:camel-aws2-snsmaven | >=4.19.0,<4.21.0 | 4.21.0 |
| org.apache.camel:camel-aws2-snsmaven | >=4.0.0 <4.14.8 | 4.14.8 |
| org.apache.camel:camel-aws2-snsmaven | >=4.15.0 <4.18.3 | 4.18.3 |
| org.apache.camel:camel-aws2-snsmaven | >=4.19.0 <4.21.0 | 4.21.0 |
Published upstream
Jul 6, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jul 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.