{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-aws2-sqs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46456 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-aws2-sqs to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0.","what":"CVE-2026-46456 is a critical vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46456 and fix it if it is affected.\n\nWhat it is: CVE-2026-46456 is a critical vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46456 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-aws2-sqs (Maven): affected from 4.19.0; fixed in 4.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46456/ (Markdown: https://insights.sbomify.com/CVE-2026-46456/index.md)","id":"CVE-2026-46456","markdown":"https://insights.sbomify.com/CVE-2026-46456/index.md","name":"CVE-2026-46456","record":{"aliases":["GHSA-cmc3-hr79-8mmv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel AWS2-SQS","requires_auth":"none","summary":"Attackers sending SQS messages can inject Camel control headers to manipulate downstream route behavior, potentially causing code execution or data modification.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation vulnerability in Apache Camel AWS2-SQS Component.\n\nThe 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.\n\nThis 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.\n\nUsers 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-07-13","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-13T19:01:42Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-46456","stars":0,"title":"Reproducer for CVE-2026-46456 — Apache Camel camel-aws2-sqs inbound message-attribute header injection (Camel control-header injection via sqs:SendMessage → downstream producer steering / RCE)"}],"tier":"poc_unverified"},"has_fix":true,"headline":"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","id":"CVE-2026-46456","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"other","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Apache Camel-NATS: Inbound NATS message headers are mapped into the Exchange without a configured HeaderFilterStrategy, allowing a client that can publish to the subject to inject Camel control headers","id":"CVE-2026-46457"},"packages":[{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":null,"source":"GHSA-cmc3-hr79-8mmv"},{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":"pkg:maven/org.apache.camel/camel-aws2-sqs","source":"GHSA-cmc3-hr79-8mmv"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":null,"source":"GHSA-cmc3-hr79-8mmv"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":"pkg:maven/org.apache.camel/camel-aws2-sqs","source":"GHSA-cmc3-hr79-8mmv"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":null,"source":"GHSA-cmc3-hr79-8mmv"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-aws2-sqs","purl":"pkg:maven/org.apache.camel/camel-aws2-sqs","source":"GHSA-cmc3-hr79-8mmv"}],"prev":{"headline":"Apache Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted","id":"CVE-2026-46455"},"products":["Apache Camel"],"published":"2026-07-06","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["Apache Software Foundation"]},"summary":"Attackers sending SQS messages can inject Camel control headers to manipulate downstream route behavior, potentially causing code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-46456/"}