CVE-2026-49097

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel IRC component. The camel-irc producer chooses the destination of an outgoing IRC message from the irc.sendTo Exchange header (the constant IrcConstants.IRC_SEND_TO, value irc.sendTo); when that header is present it overrides the channel list configured on the endpoint, and the message is sent only to the specified destination. This and the component's other control headers (irc.target, irc.messageType, irc.user.*, irc.num, irc.value) 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 an irc: producer, any HTTP client could therefore set the irc.sendTo header and redirect a message that the route intended for a configured channel to an arbitrary IRC channel or user - exfiltrating the message content to an attacker-chosen nickname, leaking it into a public channel, or delivering messages that appear to come from the bot. No credentials are required 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 IRC headers via the raw header names must use the CamelIrc* names (for example CamelIrcSendTo) instead of the old irc.* values. For deployments that cannot upgrade immediately, strip the irc.* headers from any untrusted ingress before the irc: producer (for example removeHeaders('irc.*') at the start of the route), and set the IRC destination from a trusted source.

• CWE-20
• CWE-74

• https://camel.apache.org/security/CVE-2026-49097.htmlMitigation, Vendor Advisory
• http://www.openwall.com/lists/oss-security/2026/07/05/22Mailing List, Third Party Advisory

Published

Jul 6, 2026

Last Modified

Jul 8, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-49090Uncontrolled Resource Consumption (CWE-400) in Elasticsearch…6.5
• CVE-2026-49091Improper Output Neutralization for Logs (CWE-117) in Kibana …8
• CVE-2026-49092Unintended Proxy or Intermediary ('Confused Deputy') (CWE-44…4.3
• CVE-2026-49093Server-Side Request Forgery (CWE-918) in Kibana can allow an…7.7
• CVE-2026-49094Uncontrolled Resource Consumption (CWE-400) in Kibana can le…6.5
• CVE-2026-49095Improper Input Validation (CWE-20) in the Kibana Fleet agent…6.5
• CVE-2026-49098Improper Input Validation, Improper Neutralization of Specia…5.3
• CVE-2026-49099Improper Neutralization of Special Elements in Output Used b…5.3
• CVE-2026-4910A security vulnerability has been detected in Shenzhen Ruimi…7.3
• CVE-2026-49102Webmin before 2.640 allows mailboxes/detach.cgi XSS via an S…6.1
• CVE-2026-49103Webmin before 2.640 does not safely construct a filename for…9.4
• CVE-2026-49104Unauthenticated PHP Object Injection in Integration for Keap…9.8