# CVE-2026-49099: Apache Camel-Salesforce: Non-Camel-prefixed Exchange header constants bypass the HTTP header filter > Attackers can inject HTTP headers to override Salesforce operation parameters, allowing unauthorized data access or modification via the integration user's permissions. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 7 Jul 2026 - **Also known as:** CLEANSTART-2026-CV55977, CLEANSTART-2026-VC78529, GHSA-gcc7-c8mp-34qx, MINI-782h-5vp8-mg8h ## What is CVE-2026-49099? CVE-2026-49099 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. ### Official description Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel Salesforce Component. The camel-salesforce producer resolves its operation parameters - the SOQL query, the SOSL search, the target SObject name and id, the Apex REST URL and method, and the Apex query parameters - from Exchange message headers, reading the header in preference to the value configured on the endpoint (AbstractSalesforceProcessor.getParameter() reads the header first and uses the endpoint configuration only as a fallback). The control-header constants in SalesforceEndpointConfig (for example SOBJECT_QUERY = sObjectQuery, SOBJECT_SEARCH = sObjectSearch, SOBJECT_NAME = sObjectName, SOBJECT_ID = sObjectId, APEX_URL = apexUrl, APEX_METHOD = apexMethod, and the apexQueryParam. prefix) used plain, non-Camel-prefixed values. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a salesforce: producer, any HTTP client could therefore set these headers and override what the route intended - supplying its own SOQL query or SOSL search to read data from any SObject the connected Salesforce user can access, overriding the target SObject name and id for CRUD operations, or redirecting an Apex REST call to a different endpoint and HTTP method (including destructive methods) with injected query parameters. All such operations run with the full permissions of the Salesforce connected (integration) user, which is typically broad. No credentials are required from the attacker when the bridging consumer is unauthenticated. 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. After upgrading, routes that set Salesforce operation parameters via the raw header names must use the CamelSalesforce* names (for example CamelSalesforceSObjectQuery and CamelSalesforceApexUrl) instead of the old sObject* / apex* values; the endpoint-option spelling is unchanged. For deployments that cannot upgrade immediately, strip the Salesforce control headers from any untrusted ingress before the salesforce: producer (for example removeHeaders('sObject*') and removeHeaders('apex*') at the start of the route), and set the query, SObject and Apex parameters from a trusted source. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-49099? 6 open source packages ship an affected version, including org.apache.camel:camel-salesforce. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-salesforce` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-salesforce` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-salesforce` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-salesforce` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-salesforce` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-salesforce` | Maven | From 4.19.0 | 4.21.0 | Products: Apache Camel. ## How do I fix CVE-2026-49099? Upgrade org.apache.camel:camel-salesforce to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0. ## Is CVE-2026-49099 being exploited? There is no known exploitation of CVE-2026-49099 in the wild and no public exploit code. Public exploit code: - PoC reproducer for CVE-2026-49099 (Apache Camel camel-salesforce): the non-Camel-prefixed sObjectQuery header escapes the HTTP header filter and overrides the producer's configured SOQL (SOQL injection / broken access control). Fixed in 4.14.8/4.18.3/4.21.0. (github_poc): https://github.com/oscerd/CVE-2026-49099 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-49099 and fix it if it is affected. What it is: CVE-2026-49099 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. Exploitation: There is no known exploitation of CVE-2026-49099 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-salesforce (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-salesforce (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-salesforce (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-salesforce (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-salesforce (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-salesforce (Maven): affected from 4.19.0; fixed in 4.21.0 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-49099/ (Markdown: https://insights.sbomify.com/CVE-2026-49099/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49099 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49099 - OSV: https://osv.dev/vulnerability/CVE-2026-49099 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-49099/ Summaries are generated and may contain mistakes; the official description above is the record.