Security readout for executives and security teams
Plain-English summary
Apache Camel applications that read email through camel-mail may accept attacker-controlled Camel headers from incoming messages. If those headers reach sensitive downstream route components, they can change route behavior and may enable remote code execution. This is critical where monitored mailboxes accept untrusted email.
Executive priority
Treat this as urgent for any business process that ingests external email into Camel workflows. The vulnerability is critical, network reachable through email delivery, needs no user interaction, and can affect confidentiality, integrity, and availability depending on route design.
Technical view
MailHeaderFilterStrategy filters outbound headers but lacks equivalent inbound filtering. Camel-prefixed MIME headers can be mapped into the Exchange when mail is consumed through camel-mail. Routes using components that act on Camel headers may be affected. Sources list Apache Camel 3.0.0 before 4.14.6 and 4.15.0 before 4.18.1.
Likely exposure
Exposure is likely limited to Apache Camel deployments using org.apache.camel:camel-mail to consume mail from IMAP, POP3, or similar monitored mailboxes. Risk increases when routes pass inbound mail exchanges to components that act on Camel headers.
Exploitation context
The provided data does not show active exploitation, and KEV is false. Exploitation requires the ability to deliver email to a mailbox consumed by a vulnerable Camel route and a downstream route design where injected Camel headers can affect behavior.
Researcher notes
This appears to follow the same incoming-header filtering pattern as prior Camel header injection issues. The key research question is whether inbound mail headers can reach header-sensitive downstream components in a specific route. Do not assume impact without route-level validation.
Mitigation direction
- Upgrade Apache Camel to 4.19.0 where possible.
- For 4.18.x LTS, upgrade to 4.18.1.
- For 4.14.x LTS, upgrade to 4.14.6.
- Check Apache and Red Hat advisories for distribution-specific packages.
- Prioritize routes consuming untrusted mail before lower-risk internal-only routes.
Validation and detection
- Inventory applications using org.apache.camel:camel-mail.
- Identify routes beginning with mail consumers such as IMAP or POP3.
- Confirm deployed Camel versions are not in affected ranges.
- Review downstream route components that act on Camel headers.
- Verify applicable Apache or Red Hat fixed packages are installed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1173: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-33454 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-27T10:01:41.829Z: Reported to Red Hat.
- 2026-04-27T09:42:39.799Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://camel.apache.org/security/CVE-2026-33454.htmlCVE reference, apache · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-33454CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2463181CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33454.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:19835CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:17668CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Use of Validation Framework
Improper Use of Validation Framework represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.