LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache Camel Mina can deserialize untrusted Java objects received over TCP or UDP in certain routes. If an affected application exposes a MINA consumer and converts incoming data to ObjectInput, an attacker could execute code inside that application. This is high risk for internet- or partner-facing integrations.

Executive priority

Prioritize remediation for externally reachable or partner-facing Camel integrations. This is a high-severity remote code execution risk, but urgency depends on whether affected MINA routes and ObjectInput conversion are present.

Technical view

The camel-mina MinaConverter.toObjectInput(IoBuffer) creates ObjectInputStream without ObjectInputFilter or class-loading restrictions. Routes using camel-mina consumers and ObjectInput conversion may trigger unsafe readObject() deserialization. Affected ranges are 3.0.0 before 4.14.6, 4.15.0 before 4.18.2, and 4.19.0 before 4.20.0.

Likely exposure

Exposure is likely limited to Java applications using org.apache.camel:camel-mina as a TCP or UDP consumer and requesting ObjectInput conversion. Systems not using camel-mina, not exposing MINA consumer ports, or not converting to ObjectInput are less likely affected.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. The vulnerability is network-reachable in affected route designs, has low attack complexity, requires no user interaction, and can impact confidentiality, integrity, and availability.

Researcher notes

This is CWE-502 unsafe deserialization. The key condition is the combination of camel-mina consumer input and conversion to ObjectInput. Public sources identify fixed versions but do not provide evidence of exploitation in the supplied bundle.

Mitigation direction

  • Upgrade Apache Camel to 4.20.0 where possible.
  • Use 4.14.6 for the 4.14.x LTS stream.
  • Use 4.18.2 for the 4.18.x release stream.
  • Restrict access to MINA TCP or UDP consumer ports while upgrading.
  • Avoid ObjectInput conversion for untrusted MINA traffic.
  • Check Apache and Red Hat guidance for downstream package status.

Validation and detection

  • Inventory dependencies for org.apache.camel:camel-mina and affected Camel versions.
  • Review routes using camel-mina TCP or UDP consumers.
  • Search code for getBody(ObjectInput.class) and @Body ObjectInput usage.
  • Verify runtime artifacts include the upgraded Camel version.
  • Confirm exposed MINA ports are firewall-restricted or removed.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2026-40473 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

2CVSS vectors
5Timeline events
3ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-40473Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPApache Camel: camel-mina: Apache Camel camel-mina: Arbitrary code execution via insecure deserialization
other:Red Hat severity ratingcvssV3_1
  • 2026-04-27T10:01:38.722Z: Reported to Red Hat.
  • 2026-04-27T07:51:59.134Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Camel Minaorg.apache.camel:camel-mina, 3.0.0, 4.15.0, 4.19.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

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.