Skip to main content
EPSS 0.7%top 49%

CVE-2026-59230: CWE-20 Improper input validation in Apache Software Foundation Apache Camel

0
Medium
Published: 08/24/2026 (08/24/2026, 16:09:44 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Camel

Description

Apache Camel contains an improper input validation vulnerability in its camel-mail component's MimeMultipart data format when configured with headersInline set to true. This flaw allows untrusted MIME headers to be copied as Camel message headers without filtering, potentially enabling an attacker to inject headers in the Camel-internal namespace. Such injected headers can alter the behavior of downstream route steps, depending on the route configuration. The issue affects versions from 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, and from 4.19.0 before 4.22.0. The vulnerability is fixed in Apache Camel 4.22.0, 4.14.9, and 4.18.4. Users unable to upgrade immediately should keep headersInline disabled or strip Camel-internal headers after unmarshalling.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected software

Apache Software Foundation

Apache Camel

Affected versions
>=2.17.0 <4.14.9>=4.15.0 <4.18.4>=4.19.0 <4.22.0
Apache Software Foundation/org.apache.camel:camel-mail
pkg:maven/Apache Software Foundation/org.apache.camel:camel-mail
Affected versions
>=2.17.0 <4.14.9>=4.15.0 <4.18.4>=4.19.0 <4.22.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/10/2026, 21:32:34 UTC

Technical Analysis

CVE-2026-59230 is an improper input validation vulnerability in Apache Camel's camel-mail component. When the MimeMultipart data format is used with headersInline=true, MIME headers from incoming messages are copied directly onto Camel message headers without applying a header filter strategy. This allows an attacker controlling the MIME message to inject headers in the Camel-internal namespace, which can override configured behavior in downstream components such as camel-sql. The vulnerability has existed since version 2.17.0 and affects multiple release streams until fixed in 4.14.9, 4.18.4, and 4.22.0. The default configuration (headersInline=false) is not affected. Mitigation includes upgrading to fixed versions or disabling headersInline and removing Camel-internal headers after unmarshalling.

Potential Impact

An attacker able to influence MIME messages processed by the camel-mail component with headersInline enabled can inject headers that alter the behavior of downstream route steps. This can lead to unintended execution of commands or queries if the route uses these headers for control, potentially causing information disclosure or unauthorized actions. The impact depends on the specific route configuration and which sinks are reachable after the unmarshal step. The CVSS score is 6.5 (medium severity) reflecting limited confidentiality and integrity impact without availability impact.

Mitigation Recommendations

A fix is available in Apache Camel versions 4.22.0, 4.14.9, and 4.18.4. Users are strongly recommended to upgrade to these versions. For those unable to upgrade immediately, keep the headersInline option set to false (the default) to avoid the vulnerable code path. If headersInline must be enabled, immediately remove Camel-internal headers after unmarshalling (e.g., using removeHeaders("Camel*")) before any processor or producer that reads control headers. Avoid unmarshalling MIME content from untrusted senders into routes that dispatch on header values. Treat all MIME header names from outside the trust boundary as untrusted input.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-07-03T10:47:39.960Z
State
PUBLISHED

Threat ID: 6a8c7117acd9273b49d27d9f

Added to database: 08/24/2026, 16:28:07 UTC

Last enriched: 09/10/2026, 21:32:34 UTC

Last updated: 10/08/2026, 06:48:18 UTC

Views: 64

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses