Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') Affecting org.apache.camel:camel-salesforce package, versions [4.0.0,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-17875080
- published7 Jul 2026
- disclosed6 Jul 2026
- creditUnknown
Introduced: 6 Jul 2026
NewCVE-2026-49099 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-salesforce to version 4.14.8, 4.18.3, 4.21.0 or higher.
Overview
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') via the improper handling of HTTP headers in the process. An attacker can manipulate internal Salesforce operation parameters, such as SOQL queries, SOSL searches, SObject names and IDs, or Apex REST endpoints, by supplying specially crafted HTTP headers. This allows the attacker to override intended route behavior and perform unauthorized actions with the full permissions of the connected Salesforce integration user, potentially leading to unauthorized data access or destructive operations. This is only exploitable if an HTTP consumer is bridged directly to a Salesforce producer and the consumer is unauthenticated.
Workaround
This vulnerability can be mitigated by stripping the Salesforce control headers from any untrusted ingress before the Salesforce producer, for example by using removeHeaders('sObject*') and removeHeaders('apex*') at the start of the route, and ensuring that query, SObject, and Apex parameters are set from a trusted source.