{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-elasticsearch-rest-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46453 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-elasticsearch-rest-client to a fixed version for your release line: 4.18.3, 4.21.0 or 4.14.8.","what":"CVE-2026-46453 is a medium-severity missing authorization 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-46453 and fix it if it is affected.\n\nWhat it is: CVE-2026-46453 is a medium-severity missing authorization 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-46453 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.3.0; fixed in 4.14.8\n- org.apache.camel:camel-elasticsearch-rest-client (Maven): affected from 4.3.0; fixed in 4.14.8\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-46453/ (Markdown: https://insights.sbomify.com/CVE-2026-46453/index.md)","id":"CVE-2026-46453","markdown":"https://insights.sbomify.com/CVE-2026-46453/index.md","name":"CVE-2026-46453","record":{"aliases":["GHSA-rp9m-hfv5-pfvr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Camel Elasticsearch component","requires_auth":"none","summary":"Untrusted HTTP clients can override Elasticsearch query and operation headers in Apache Camel routes, allowing unauthorized data access or modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client.\n\nThe camel-elasticsearch-rest-client component reads several Exchange headers to control its behaviour - SEARCH_QUERY (an advanced query body), OPERATION (which Elasticsearch operation to run), INDEX_NAME, INDEX_SETTINGS and ID. The string values of these header constants, defined in ElasticSearchRestClientConstant, are plain unprefixed names ('SEARCH_QUERY', 'OPERATION', 'INDEX_NAME', 'INDEX_SETTINGS', 'ID') rather than the 'Camel'-prefixed names used by every other Camel component (for example CamelSqlQuery, CamelMongoDbCriteria, CamelCqlQuery). Camel's inbound HTTP header filter, HttpHeaderFilterStrategy, blocks only header names that begin with 'Camel' or 'camel'. Because the Elasticsearch header names do not carry that prefix, they pass through the inbound filter unchanged. When a Camel route exposes an HTTP entry point (for example platform-http) in front of an elasticsearch-rest-client producer, an untrusted HTTP client can set these headers directly on its request and override the query and operation that the route author configured: reading every document in the index (SEARCH_QUERY with a match_all query), deleting documents (OPERATION set to Delete together with ID), or exfiltrating selected fields. No credentials are required and the producer reads the headers unconditionally.\nThis issue affects Apache Camel: from 4.3.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 renames the camel-elasticsearch-rest-client Exchange header constant string values (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) to carry the Camel prefix (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation) so that they are blocked by the inbound HttpHeaderFilterStrategy; the Java field names are unchanged. For deployments that cannot upgrade immediately, strip the affected headers from untrusted inbound messages before they reach the producer (for example removeHeader('SEARCH_QUERY'), removeHeader('OPERATION'), removeHeader('INDEX_NAME'), removeHeader('INDEX_SETTINGS') and removeHeader('ID') in front of the elasticsearch-rest-client endpoint), or apply a custom HeaderFilterStrategy that blocks these names.","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-13T12:30:14Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-46453","stars":0,"title":"Reproducer for CVE-2026-46453 — Apache Camel camel-elasticsearch-rest-client unprefixed-header injection (operation/query override via inbound HTTP headers)"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Camel-Elasticsearch-Rest-Client: Exchange header constants without the Camel prefix bypass inbound HTTP header filtering, allowing untrusted clients to override the Elasticsearch query and operation","id":"CVE-2026-46453","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"missing_authorization","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Apache Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to inject Camel control headers","id":"CVE-2026-46454"},"packages":[{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":null,"source":"GHSA-rp9m-hfv5-pfvr"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":"pkg:maven/org.apache.camel/camel-elasticsearch-rest-client","source":"GHSA-rp9m-hfv5-pfvr"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":null,"source":"GHSA-rp9m-hfv5-pfvr"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":"pkg:maven/org.apache.camel/camel-elasticsearch-rest-client","source":"GHSA-rp9m-hfv5-pfvr"},{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.3.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":null,"source":"GHSA-rp9m-hfv5-pfvr"},{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.3.0"],"last_affected":[],"package":"org.apache.camel:camel-elasticsearch-rest-client","purl":"pkg:maven/org.apache.camel/camel-elasticsearch-rest-client","source":"GHSA-rp9m-hfv5-pfvr"}],"prev":{"headline":"Apache NimBLE: Mesh Proxy SAR reassembly unbounded append and unchecked failure","id":"CVE-2026-46452"},"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":"partial"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["Apache Software Foundation"]},"summary":"Untrusted HTTP clients can override Elasticsearch query and operation headers in Apache Camel routes, allowing unauthorized data access or modification.","url":"https://insights.sbomify.com/CVE-2026-46453/"}