cve.bz

CVE-2026-46456 apache camel: Improper Input Validation

9.8 criticalEPSS 0.8%Fix available

Critical (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.

On this page
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, 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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-46456

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-46456](https://cve.bz/cve/badge/CVE-2026-46456.svg)](https://cve.bz/cve/CVE-2026-46456)

HTML:

<a href="https://cve.bz/cve/CVE-2026-46456"><img src="https://cve.bz/cve/badge/CVE-2026-46456.svg" alt="CVE-2026-46456"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cmc3-hr79-8mmvMavenorg.apache.camel:camel-aws2-sqs>=4.0.0 <4.14.84.14.8
GHSA-cmc3-hr79-8mmvMavenorg.apache.camel:camel-aws2-sqs>=4.15.0 <4.18.34.18.3
GHSA-cmc3-hr79-8mmvMavenorg.apache.camel:camel-aws2-sqs>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16camelFixed 2026-09-24RHSA-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.

GitHub PoC

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.

  • oscerd/CVE-2026-46456 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-46456 — Apache Camel camel-aws2-sqs inbound message-attribute header injection (Camel control-header injection via …

Attack patterns (CAPEC)

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).

References

Check your stackJSON