CVE-2026-40473: Apache Camel Mina: Unsafe Deserialization in MinaConverter.toObjectInput() via TCP/UDP

Published Apr 26, 2026
·
Updated

The camel-mina component's MinaConverter.toObjectInput(IoBuffer) type converter wraps an IoBuffer in a java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. When a Camel route uses camel-mina as a TCP or UDP consumer and requests conversion to ObjectInput (for example via getBody(ObjectInput.class) or @Body ObjectInput), an attacker sending a crafted serialized Java object over the network to the MINA consumer port can trigger arbitrary code execution in the context of the application during readObject().

This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0.

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

Affected Software

4 affected components
Apache Apache Camel (camel-mina)>=3.0.0<4.14.6, >=4.15.0<4.18.2, >=4.19.0<4.20.0
Apache Camel>=3.0.0<4.14.6
Apache Camel>=4.15.0<4.18.2
Apache Camel=4.19.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Camel (camel-mina component) to a version that resolves this vulnerability.

    Fixed in 4.14.6
  2. Upgrade

    Upgrade Apache Camel (camel-mina component) to a version that resolves this vulnerability.

    Fixed in 4.18.2
  3. Upgrade

    Upgrade Apache Camel (camel-mina component) to a version that resolves this vulnerability.

    Fixed in 4.20.0
  4. Compensating control

    If upgrading is not immediately possible, mitigate exposure by restricting network access to the MINA consumer port(s) used by camel-mina TCP/UDP routes so only trusted clients can reach them.

Event History

Apr 27, 2026
CVE Published
via MITRE·07:51 AM
Data Sourced
via MITRE·07:51 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·10:02 AM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40473?

CVE-2026-40473 has a high severity due to the potential for remote code execution through unsafe deserialization.

2

How do I fix CVE-2026-40473?

To fix CVE-2026-40473, upgrade to Apache Camel versions 4.14.7, 4.18.3, or 4.20.1 or later, which address the vulnerability.

3

What versions of Apache Camel are affected by CVE-2026-40473?

Apache Camel versions 3.0.0 to 4.14.6, 4.15.0 to 4.18.2, and 4.19.0 are affected by CVE-2026-40473.

4

What are the risks associated with CVE-2026-40473?

The risks associated with CVE-2026-40473 include unauthorized remote access and the execution of malicious code.

5

Is the MinaConverter.toObjectInput() method safe to use in Apache Camel?

No, the MinaConverter.toObjectInput() method is not safe to use in vulnerable versions of Apache Camel due to unsafe deserialization.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203