CVE-2026-49097

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-49097: Apache Camel: Camel-IRC: The irc.sendTo (and other irc.*) Exchange header constants used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to redirect outgoing IRC messages to arbitrary channels or users

http://www.openwall.com/lists/oss-security/2026/07/05/22
generic

Apache Camel Security Advisory - CVE-2026-49097 - Apache Camel

https://camel.apache.org/security/CVE-2026-49097.html

Vendor Advisories for CVE-2026-49097(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 79× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 133 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 08:27 UTCEG score recompute
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 22:00 UTCEG score recompute
  6. 2026-08-27 22:00 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 13:56 UTCEG score recompute
  10. 2026-08-26 13:56 UTCGHSA enrichment
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 23:05 UTCEG score recompute
  13. 2026-08-24 23:04 UTCGHSA enrichment
  14. 2026-08-23 23:50 UTCGHSA enrichment
  15. 2026-08-23 00:37 UTCEG score recompute
  16. 2026-08-23 00:37 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 01:22 UTCEG score recompute
  19. 2026-08-22 01:22 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 02:08 UTCEG score recompute
  22. 2026-08-21 02:08 UTCGHSA enrichment
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 02:54 UTCEG score recompute
  25. 2026-08-20 02:54 UTCGHSA enrichment
Show 75 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 22:30 UTCEG score recompute
  3. 2026-08-18 22:30 UTCGHSA enrichment
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 22:42 UTCEG score recompute
  6. 2026-08-17 22:42 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 22:35 UTCEG score recompute
  9. 2026-08-16 22:35 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 23:21 UTCEG score recompute
  13. 2026-08-15 23:21 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-15 00:07 UTCGHSA enrichment
  16. 2026-08-14 00:53 UTCEG score recompute
  17. 2026-08-14 00:53 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 01:40 UTCEG score recompute
  20. 2026-08-13 01:40 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 02:26 UTCEG score recompute
  23. 2026-08-12 02:26 UTCGHSA enrichment
  24. 2026-08-11 03:13 UTCEG score recompute
  25. 2026-08-11 03:13 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 03:59 UTCEG score recompute
  28. 2026-08-10 03:59 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 04:46 UTCEG score recompute
  31. 2026-08-09 04:46 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 05:33 UTCEG score recompute
  34. 2026-08-08 05:33 UTCGHSA enrichment
  35. 2026-08-07 06:19 UTCEG score recompute
  36. 2026-08-07 06:19 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-06 07:06 UTCEG score recompute
  39. 2026-08-06 07:06 UTCGHSA enrichment
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-05 07:52 UTCEG score recompute
  42. 2026-08-05 07:52 UTCGHSA enrichment
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:39 UTCEPSS rescore
  45. 2026-08-04 08:35 UTCEG score recompute
  46. 2026-08-04 08:34 UTCGHSA enrichment
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-03 08:51 UTCGHSA enrichment
  49. 2026-08-02 09:37 UTCEG score recompute
  50. 2026-08-02 09:37 UTCGHSA enrichment
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 10:24 UTCEG score recompute
  53. 2026-08-01 10:24 UTCGHSA enrichment
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-31 11:10 UTCEG score recompute
  56. 2026-07-31 11:10 UTCGHSA enrichment
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 11:22 UTCEG score recompute
  59. 2026-07-30 11:22 UTCGHSA enrichment
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-29 12:05 UTCEG score recompute
  62. 2026-07-29 12:05 UTCGHSA enrichment
  63. 2026-07-28 15:37 UTCEPSS rescore
  64. 2026-07-28 12:51 UTCEG score recompute
  65. 2026-07-28 12:51 UTCGHSA enrichment
  66. 2026-07-27 12:02 UTCEG score recompute
  67. 2026-07-27 12:02 UTCGHSA enrichment
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 12:49 UTCEG score recompute
  70. 2026-07-26 12:49 UTCGHSA enrichment
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-24 14:18 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:18 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49097?
CVE-2026-49097 is a medium vulnerability published on July 6, 2026. 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…
When was CVE-2026-49097 disclosed?
CVE-2026-49097 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49097 actively exploited?
CVE-2026-49097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49097?
CVE-2026-49097 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49097, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49097

Explore →

Is Your Infrastructure Affected by CVE-2026-49097?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs