Medium [CVE-2026-49099] Apache Camel: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), Authorization…
This medium-severity Apache Software Foundation advisory covers CVE-2026-49099 affecting Apache Camel Salesforce.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
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.
Is CVE-2026-49099 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-49099 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-49099?
Upgrade to a fixed release named by Apache:
- 4.21.0
- 4.14.8
- 4.18.3
Confirm against the vendor advisory before you patch.
- 4.0.0 through 4.14.8
- 4.15.0 through 4.18.3
- 4.19.0 through 4.21.0.
Official advisory · high-confidence parse· fetched 4 months ago·verify at source
- 4.21.0
- 4.14.8
- 4.18.3
Official advisory · high-confidence parse· fetched 4 months ago·verify at source
Mitigation checklist
- 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.
- 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.
Official advisory · high-confidence parse· fetched 4 months ago·verify at source
Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.
See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Apache Software Foundation advisories
- CVE-2026-90436Nov 6, 2026** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis
- CVE-2026-85111Nov 6, 2026Apache James denial of service
- CVE-2026-85108Nov 6, 2026Apache James Mime4J Core denial of service
- CVE-2026-76168Nov 6, 2026In Apache James server prior version 3.9.1 relying on the SieveFileRepository incorect
- CVE-2026-74756Nov 6, 2026Some docker-compose shipped by the project exposes by default Webadmin REST API publically
- CVE-2026-76171Nov 6, 2026Apache James SSRF
iPhone and Android apps · New on the App Store
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.