What is CVE-2026-46456?

CVE-2026-46456 is a critical-severity improper input validation vulnerability in org.apache.camel:camel-aws2-sqs (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2026-46456?

CVE-2026-46456 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.camel:camel-aws2-sqs are affected by CVE-2026-46456?

org.apache.camel:camel-aws2-sqs (maven) versions >= 4.0.0, < 4.14.8 is affected.

Is there a fix for CVE-2026-46456?

Yes. CVE-2026-46456 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Is CVE-2026-46456 exploitable, and should I be worried?

Whether CVE-2026-46456 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-46456 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-46456 in org.apache.camel:camel-aws2-sqs

Q: How severe is CVE-2026-46456?

CVE-2026-46456 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.camel:camel-aws2-sqs are affected by CVE-2026-46456?

org.apache.camel:camel-aws2-sqs (maven) versions >= 4.0.0, < 4.14.8 is affected.

Q: Is there a fix for CVE-2026-46456?

Yes. CVE-2026-46456 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Q: Is CVE-2026-46456 exploitable, and should I be worried?

Whether CVE-2026-46456 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-46456 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-46456?

Upgrade: org.apache.camel:camel-aws2-sqs to 4.14.8 or later, org.apache.camel:camel-aws2-sqs to 4.18.3 or later, org.apache.camel:camel-aws2-sqs to 4.21.0 or later.

Summary

Apache Camel-AWS2-SQS: Inbound message attributes are mapped into the Exchange without an inbound HeaderFilterStrategy, allowing a message sender to inject Camel control headers

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, strip the Camel control headers from inbound messages before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), and restrict who may send to the consumed SQS queue by applying least-privilege sqs:SendMessage permissions on the queue resource policy.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-46456 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.8, 4.18.3, 4.21.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.camel:camel-aws2-sqs (>= 4.0.0, < 4.14.8) org.apache.camel:camel-aws2-sqs (>= 4.15.0, < 4.18.3) org.apache.camel:camel-aws2-sqs (>= 4.19.0, < 4.21.0)

Security releases

org.apache.camel:camel-aws2-sqs → 4.14.8 (maven) org.apache.camel:camel-aws2-sqs → 4.18.3 (maven) org.apache.camel:camel-aws2-sqs → 4.21.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-aws2-sqs to 4.14.8 or later; org.apache.camel:camel-aws2-sqs to 4.18.3 or later; org.apache.camel:camel-aws2-sqs to 4.21.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-46456? CVE-2026-46456 is a critical-severity improper input validation vulnerability in org.apache.camel:camel-aws2-sqs (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2026-46456? CVE-2026-46456 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.camel:camel-aws2-sqs are affected by CVE-2026-46456? org.apache.camel:camel-aws2-sqs (maven) versions >= 4.0.0, < 4.14.8 is affected.
Is there a fix for CVE-2026-46456? Yes. CVE-2026-46456 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.
Is CVE-2026-46456 exploitable, and should I be worried? Whether CVE-2026-46456 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-46456 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-46456?
- Upgrade org.apache.camel:camel-aws2-sqs to 4.14.8 or later
- Upgrade org.apache.camel:camel-aws2-sqs to 4.18.3 or later
- Upgrade org.apache.camel:camel-aws2-sqs to 4.21.0 or later