Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-33454 critical CVSS 9.4

Unsafe Deserialization in org.apache.camel:camel-mail (CVE-2026-33454)

Summary

Vulnerability in org.apache.camel:camel-mail (CVE-2026-33454). Confidential information can be exposed externally. Mitigation: upgrade to 4.18.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-33454 has been found in org.apache.camel:camel-mail.
Confidential information can be exposed externally. CVSS score: 9.4/10.
What to do: upgrade org.apache.camel:camel-mail to 4.18.1 or later.
If unsure, ask your IT team or search "org.apache.camel:camel-mail CVE-2026-33454" on the vendor's site.

CVE-2026-33454 (org.apache.camel:camel-mail) — CWE-502 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.18.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Unsafe deserialization (CWE-502) exists in org.apache.camel:camel-mail.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.camel:camel-mail.

🔥 Severity

Severity: Critical (CVSS 9.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.18.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.camel:camel-mail を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.camel:camel-mail to 4.18.1

    ステージング環境で 4.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.camel:camel-mail
[{"type":"ECOSYSTEM","events":[{"introduced":"4.15.0"},{"fixed":"4.18.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details