CVE-2026-33454

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.4Exploit: None knownExposed: 0

A fix is available — apply it.

The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\"imap://...\") or from(\"pop3://...\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).

This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.

Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
58(Track)
EG Risk 58/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
Severity94% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

April 27, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Aug 23, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33454.json
redhat Patch Available

2463181 – (CVE-2026-33454) CVE-2026-33454 Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection

https://bugzilla.redhat.com/show_bug.cgi?id=2463181
redhat Patch Available

CVE-2026-33454 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-33454
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19835
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:17668
generic

Apache Camel Security Advisory - CVE-2026-33454 - Apache Camel

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

Vendor Advisories for CVE-2026-33454(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcamel-mail2026-05-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-mail4.15.0, 4.16.0, 4.17.0, 4.18.04.18.1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 93× 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 268 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-33454?
CVE-2026-33454 is a critical vulnerability published on April 27, 2026. The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a…
When was CVE-2026-33454 disclosed?
CVE-2026-33454 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33454 actively exploited?
CVE-2026-33454 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 52.9% of all scored CVEs.
What is the CVSS score of CVE-2026-33454?
CVE-2026-33454 has a CVSS v3.1 base score of 9.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-33454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33454, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33454

Explore →

Is Your Infrastructure Affected by CVE-2026-33454?

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

Start Free Scan →Browse All CVEs