CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in apache camel. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-aws2-sqs 4.14.8, 4.18.3, 4.21.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Horg.apache.camel:camel-aws2-sqs (Maven): fixed in 4.14.8, 4.18.3, 4.21.0Explain CVE-2026-46456 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46456?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46456?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46456 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.14.8 |
| Apache Software Foundation Apache Camel | from 4.15.0 before 4.18.3 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.21.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-cmc3-hr79-8mmv | Maven | org.apache.camel:camel-aws2-sqs | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-cmc3-hr79-8mmv | Maven | org.apache.camel:camel-aws2-sqs | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-cmc3-hr79-8mmv | Maven | org.apache.camel:camel-aws2-sqs | >=4.19.0 <4.21.0 | 4.21.0 |
Red Hat rates this Moderate.
This is a Critical improper input validation vulnerability in the `camel-aws2-sqs` component of Red Hat build of Apache Camel. A remote attacker with `sqs:SendMessage` permissions to a consumed SQS queue can inject arbitrary Camel control headers into the message exchange. This allows for manipulation of downstream producer behavior, potentially leading to data redirection, file modification, or query alteration, without requiring authentication to the Camel application itself.
To mitigate this issue, configure your Camel routes to strip Camel control headers from inbound messages before they reach any downstream producer. Additionally, restrict who can send messages to the consumed SQS queue by applying least-privilege `sqs:SendMessage` permissions on the queue resource policy. For example, add `removeHeaders('Camel*')` and `removeHeaders('camel*')` at the start of the route. Ensure that any changes to route configurations are properly deployed and services are reloaded or restarted if necessary for the changes to take effect.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16 | camel | Fixed 2026-09-24 | RHSA-2026:71675 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46456.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).