CVE-2026-33454

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 44% 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: epss, nvd
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.4Exploit: NoneExposed: 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)
EPSS
45.5%
KEV
Not listed

Published

April 27, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Apr 28, 2026
No patch confirmed yet.
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 9× in last 7d / 58× 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 220 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 June 29, 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 45.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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