Apache Camel CVE-2026-46456

Requires that the target route consumes from an SQS queue via the camel-aws2-sqs component on a vulnerable version (4.0.0-4.14.7, 4.15.0-4.18.2, or 4.19.0-4.20.x) AND that the route contains a downstream producer whose behaviour is steered by a Camel control header - for example an HTTP producer honoring CamelHttpUri, a file producer honoring CamelFileName, or a SQL producer honoring CamelSqlQuery. The attacker must possess AWS sqs:SendMessage permission on that specific consumed queue (cross-account sender or lower-privileged in-account component). Exploitation is LIMITED by: the need for a header-sensitive producer in the route (routes without such producers see no concrete impact), the requirement to be an authorized SQS sender on the exact queue, and the fact that impact is bounded by what those downstream producers can do. No end-user interaction is required, and injected headers persist across direct/seda/vm hops.

The published CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but that rating overstates real-world risk for this design flaw. Exploitation is not truly unauthenticated in practice: the attacker must already hold AWS sqs:SendMessage permission on the specific queue Camel consumes, and the concrete impact is entirely contingent on which downstream producers the route uses - a route with only benign producers may be unaffected, while one with HTTP, file, or SQL producers is at material risk. That conditionality argues for higher attack complexity (AC:H) and some required privilege (PR:L), and the impact is dominated by integrity rather than uniform C/I/A High. Corroborating signals point to lower urgency: EPSS is 0.16% (6th percentile), the CVE is not in CISA KEV, and no POC is referenced. Note a discrepancy in the input - one third-party advisory link references CVE-2026-56140 rather than CVE-2026-46456; verify the correct advisory with the vendor.

An attacker with cross-account or lower-privileged in-account sqs:SendMessage rights posts a message to the consumed SQS queue with a MessageAttribute named CamelHttpUri set to an attacker-controlled URL. When Sqs2Consumer maps the attribute into the Exchange, a downstream HTTP producer in the route uses the injected value and sends the request (and any accompanying data) to the attacker's endpoint. No public POC is referenced, and success depends on the route containing a header-sensitive producer.