6.5

CVE-2026-49097: apache software foundation apache camel Improper Input Validation

CVSS: 6.5v3.1MediumAnalyzed
AliasesGHSA-463m-2hr2-q2j7
Published 06-07-2026Last modified 06-07-2026

Vulnerability summary

CVE-2026-49097 is a medium (CVSS 6.5) Improper Input Validation vulnerability in apache software foundation apache camel. EPSS estimates a 0.68% chance of exploitation in the next 30 days, higher than 51.3% of scored vulnerabilities.

Overall risk
26/100
0100
Medium · default modelHow is this calculated?
CVSS score
6.5/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.68%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 06-07-2026
    PublishedVulnerability first disclosed.
  2. 06-07-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.68%

Chance of exploitation in the next 30 days

Percentile

51%

Versus all other CVEs

30-day change

0.00 pp

From 0.68% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.68%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Apache1 product
  • camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Apache software foundation1 product
  • apache camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Org.apache.camel1 product
  • camel-irc≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0

3 vendors · 3 products

References

14 links
Show all 14 references