{"answers":{"affected":"4 open source packages ship an affected version, including org.apache.camel:camel-mail. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33454 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-mail to a fixed version for your release line: 4.14.6 or 4.18.1.","what":"CVE-2026-33454 is a critical code injection vulnerability in Apache Camel, published on 27 Apr 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-33454 and fix it if it is affected.\n\nWhat it is: CVE-2026-33454 is a critical code injection vulnerability in Apache Camel, published on 27 Apr 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-33454 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-mail (Maven): affected from 3.0.0; fixed in 4.14.6\n- org.apache.camel:camel-mail (Maven): affected from 3.0.0; fixed in 4.14.6\n- org.apache.camel:camel-mail (Maven): affected from 4.15.0; fixed in 4.18.1\n- org.apache.camel:camel-mail (Maven): affected from 4.15.0; fixed in 4.18.1\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-33454/ (Markdown: https://insights.sbomify.com/CVE-2026-33454/index.md)","id":"CVE-2026-33454","markdown":"https://insights.sbomify.com/CVE-2026-33454/index.md","name":"CVE-2026-33454","record":{"aliases":["GHSA-2vqf-x7g4-7c2g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel library","requires_auth":"none","summary":"Attackers can inject Camel headers via email to trigger remote code execution in downstream components like camel-exec or camel-sql.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":9.4,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-1173","name":"Improper Use of Validation Framework"},{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\\\"imap://...\\\") or from(\\\"pop3://...\\\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).\n\nThis issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.\n\nUsers are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-07-06","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-06T12:56:08Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-33454","stars":1,"title":"Reproducer for CVE-2026-33454: Apache Camel camel-mail header injection to RCE via camel-exec"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Camel's Camel-Mail component is vulnerable to Camel message header injection","id":"CVE-2026-33454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Livestatus injection in monitoring quicksearch","id":"CVE-2026-33455"},"packages":[{"ecosystem":"Maven","fixed":["4.14.6"],"introduced":["3.0.0"],"last_affected":[],"package":"org.apache.camel:camel-mail","purl":null,"source":"GHSA-2vqf-x7g4-7c2g"},{"ecosystem":"Maven","fixed":["4.14.6"],"introduced":["3.0.0"],"last_affected":[],"package":"org.apache.camel:camel-mail","purl":"pkg:maven/org.apache.camel/camel-mail","source":"GHSA-2vqf-x7g4-7c2g"},{"ecosystem":"Maven","fixed":["4.18.1"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-mail","purl":null,"source":"GHSA-2vqf-x7g4-7c2g"},{"ecosystem":"Maven","fixed":["4.18.1"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-mail","purl":"pkg:maven/org.apache.camel/camel-mail","source":"GHSA-2vqf-x7g4-7c2g"}],"prev":{"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453"},"products":["Apache Camel"],"published":"2026-04-27","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":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject Camel headers via email to trigger remote code execution in downstream components like camel-exec or camel-sql.","url":"https://insights.sbomify.com/CVE-2026-33454/"}