CVE-2026-46456

published 2026-07-06

CVE-2026-46456: Improper Input Validation vulnerability in Apache Camel AWS2-SQS Component. The camel-aws2-sqs component map inbound message attributes into the Camel Exchange…

Priority P2 62 critical 9.8 CVSS 3.1

AV N AC L PR N UI N S U C H I H A H

Improper Input Validation vulnerability in Apache Camel AWS2-SQS Component.

The camel-aws2-sqs component map inbound message attributes into the Camel Exchange through a component-specific HeaderFilterStrategy. Sqs2HeaderFilterStrategy configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers being written to the broker) but did not configure an inbound filter. As a result, when Sqs2Consumer copies each SQS MessageAttribute into the Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, DefaultHeaderFilterStrategy applied no inbound rule and treated every header name as not filtered - including Camel-internal control headers such as CamelHttpUri, CamelFileName or CamelSqlQuery - copying them unmodified onto the Camel message. Any principal able to send messages to the consumed SQS queue (for example a cross-account sender or a lower-privileged in-account component holding sqs:SendMessage) could therefore set arbitrary Camel control headers that influence the behaviour of downstream producers in the route (for example redirecting an HTTP producer, changing a file name, or overriding a query); the injected headers also persist across internal direct, seda and vm hops. The concrete downstream impact depends on which producers the route uses.

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.

Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix adds an inbound HeaderFilterStrategy rule to Sqs2HeaderFilterStrategy that filters the Camel header namespace case-insensitively on inbound mapping, so sender-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, st

Affected

6 ranges

Vendor	Product	Version range	Fixed in
apache	camel	>= 4.0.0 < 4.14.8	4.14.8
apache	camel	>= 4.15.0 < 4.18.3	4.18.3
apache	camel	>= 4.19.0 < 4.21.0	4.21.0
apache_software_foundation	apache_camel_aws2_sns	>= 4.0.0 < 4.14.8	4.14.8
apache_software_foundation	apache_camel_aws2_sns	>= 4.15.0 < 4.18.3	4.18.3
apache_software_foundation	apache_camel_aws2_sns	>= 4.19.0 < 4.21.0	4.21.0

Detection & IOCs extracted from sources · hover to see the quote

other CamelHttpUri↗

other CamelFileName↗

other CamelSqlQuery↗

• → Monitor SQS messages arriving at Camel-consumed queues for MessageAttributes whose names match the pattern Camel* or camel* (case-insensitive). Presence of such attributes from external or cross-account senders is a strong indicator of header-injection exploitation attempts. ↗
• → Alert on Camel Exchange headers CamelHttpUri, CamelFileName, or CamelSqlQuery being set from SQS inbound message attributes, which would indicate an attacker is attempting to redirect HTTP producers, change file names, or override SQL queries downstream. ↗
• → Injected Camel control headers persist across internal direct, seda, and vm hops — detection should cover the full route, not just the SQS consumer endpoint. ↗
• → Audit SQS queue resource policies for any principal holding sqs:SendMessage that is cross-account or lower-privileged; such principals are the threat actors for this CVE. ↗
• → Vulnerable component is camel-aws2-sqs (Sqs2Consumer / Sqs2HeaderFilterStrategy). Identify all Camel routes using this component in versions 4.0.0–4.14.7, 4.15.0–4.18.2, or 4.19.0–4.20.x as high-priority targets for patching or workaround. ↗

• · The vulnerability exists because Sqs2HeaderFilterStrategy configured only an outbound filter (setOutFilterPattern) and no inbound filter, allowing all SQS MessageAttributes — including Camel control headers — to be copied into the Exchange unfiltered. ↗
• · The fix (CAMEL-23506) adds an inbound HeaderFilterStrategy rule (setInFilterStartsWith for the Camel namespace) to Sqs2HeaderFilterStrategy, filtering Camel*/camel* headers case-insensitively on inbound mapping. Verify this rule is active after upgrading. ↗
• · camel-aws2-sns (Sns2HeaderFilterStrategy) had the same missing inbound filter configuration but is NOT exploitable because Sns2Endpoint is producer-only and never maps inbound message attributes into a Camel Exchange. ↗
• · Interim workaround for deployments that cannot upgrade: add removeHeaders('Camel*') and removeHeaders('camel*') at the start of every route consuming from SQS, and apply least-privilege sqs:SendMessage permissions on the queue resource policy. ↗

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.

CWE-20