CVE-2026-49097: Apache Camel-IRC The Irc.sendTo (and Other Irc.*) Vulnerability
MODERATECVE-2026-49097 is a MODERATE (CVSS 6.5) the irc.sendto (and other irc.*) vulnerability (CWE-20: Improper Input Validation) affecting Apache Camel-IRC libraries in the Maven ecosystem. The issue involves the irc.sendto (and other irc.*) exchange header constants used non-camel-prefixed names that bypass the http header filter. Remediation is available by upgrading affected packages to version 4.14.8, 4.18.3, 4.21.0.
CVE-2026-49097 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-49097
To remediate this vulnerability, upgrade all affected Apache Camel-IRC dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-irc</artifactId>
<version>4.14.8</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-irc</artifactId>
<version>4.18.3</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-irc</artifactId>
<version>4.21.0</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.apache.camel
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-49097, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.apache.camel
Analyze the terminal output to locate any version of Apache Camel-IRC in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.14.8), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.apache.camel command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Apache Camel-IRC, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-49097 Affected Apache Camel-IRC Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.camel:camel-irc
|
Maven |
≥ 4.0.0
< 4.14.8
|
4.14.8
|
|
org.apache.camel:camel-irc
|
Maven |
≥ 4.15.0
< 4.18.3
|
4.18.3
|
|
org.apache.camel:camel-irc
|
Maven |
≥ 4.19.0
< 4.21.0
|
4.21.0
|
References
Frequently Asked Questions
What is CVE-2026-49097?
Which Apache Camel-IRC versions are affected?
What version fixes CVE-2026-49097?
Is camel-irc affected?
What is the CVSS score of CVE-2026-49097?
What CWE is associated with CVE-2026-49097?
How can I check Maven dependencies for CVE-2026-49097?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-463m-2hr2-q2j7",
"modified" : "2026-08-28T20:13:49Z",
"published" : "2026-07-06T09:30:30Z",
"aliases" : [ "CVE-2026-49097" ],
"summary" : "Apache Camel-IRC: The irc.sendTo (and other irc.*) Exchange header constants used non-Camel-prefixed names that bypass the HTTP header filter",
"details" : "Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel IRC component.\n\nThe 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.\nThis 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.\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. 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-irc"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.14.8"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-irc"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.15.0"
}, {
"fixed" : "4.18.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-irc"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.19.0"
}, {
"fixed" : "4.21.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-49097"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/23594"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/23616"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/23635"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/0be886bf433c718abe4a27498245f6898366fb0c"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/18b64b47fda68b15f4eb9f7ce8148c8b9ec819a0"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/2959633a6dd51a9736a9efaedaa843548fcd2d3e"
}, {
"type" : "WEB",
"url" : "https://camel.apache.org/security/CVE-2026-49097.html"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/camel"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/releases/tag/camel-4.14.8"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/releases/tag/camel-4.18.3"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/releases/tag/camel-4.21.0"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/CAMEL-23629"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2026/07/05/22"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T20:13:49Z",
"nvd_published_at" : "2026-07-06T09:16:38Z"
}
}