Skip to main content
Vulnerability Database/CVE-2026-83531

CVE-2026-83531: Apache Camel Expression Injection RCE

CVE-2026-83531 is an expression injection remote code execution flaw in Apache Camel affecting versions 4.4.0 to 4.18.4 and 4.19.0 to 4.22.0. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-83531 Overview

CVE-2026-83531 is a code injection and expression language injection vulnerability in Apache Camel's dynamic-router-control endpoint. The flaw allows an attacker who can send messages to a transport that forwards to this endpoint to supply arbitrary expression language predicates. These predicates are compiled and evaluated with the privileges of the Camel process, resulting in arbitrary code execution. The vulnerability affects Apache Camel versions 4.4.0 through 4.18.4 and 4.19.0 through 4.22.0. The issue is tracked under CWE-94: Improper Control of Generation of Code.

Critical Impact

Remote attackers with access to a forwarded transport can execute arbitrary expressions, including the always-present simple language, leading to full code execution within the Camel JVM.

Affected Products

  • Apache Camel 4.4.0 through 4.18.4
  • Apache Camel 4.19.0 through 4.22.0
  • Apache Camel 4.14.x and earlier (end of life, no fix)

Discovery Timeline

  • 2026-10-19 - CVE-2026-83531 published to NVD
  • 2026-10-20 - Last updated in NVD database

Technical Details for CVE-2026-83531

Vulnerability Analysis

The dynamic-router-control endpoint, introduced in Apache Camel 4.4.0, lets routing participants manage Dynamic Router subscriptions through control messages. When processing a subscribe or update request, DynamicRouterControlProducer extracts both the subscription predicate and the expression language name from the incoming message. These values can arrive through the predicate and expressionLanguage fields of a DynamicRouterControlMessage body, or through the CamelDynamicRouterPredicate and CamelDynamicRouterExpressionLanguage headers.

DynamicRouterControlService then resolves the specified language from the CamelContext and compiles the attacker-supplied string into a Predicate. The service applies no allow-list and requires no opt-in. The compiled predicate joins the channel's rule base and executes against every exchange routed through the matching dynamic-router endpoint. Any expression language on the classpath is selectable, and the simple language is always available and acts as the default on the header path.

Root Cause

The root cause is the unrestricted acceptance of expression language source code from untrusted message content. The control service treats incoming message fields as a trusted configuration surface and compiles them without validating the sender or constraining the available languages. Removing optional expression languages from the classpath does not mitigate the issue because simple remains present.

Attack Vector

Exploitation requires only the ability to send a message on a transport whose route forwards to a dynamic-router-control endpoint. The component documentation describes this pattern for routing participants in other JVMs or applications, so the configuration is realistic in production deployments. No additional authentication or user interaction is needed. The attacker crafts a control message with a chosen expression language and predicate, which the Camel process compiles and evaluates with its own privileges on every subsequent exchange.

Verified exploitation code is not publicly released. Technical details are available in the Apache Camel CVE-2026-83531 Advisory and the corresponding JIRA issue CAMEL-24576.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-83531

Indicators of Compromise

  • Incoming messages containing CamelDynamicRouterPredicate or CamelDynamicRouterExpressionLanguage headers from external or shared transports.
  • DynamicRouterControlMessage payloads with populated predicate or expressionLanguage fields arriving from untrusted sources.
  • Unexpected process execution, outbound network connections, or file writes originating from the Camel JVM.

Detection Strategies

  • Inspect Camel route definitions for any route that forwards messages from a network transport into a dynamic-router-control endpoint.
  • Enable DEBUG logging on DynamicRouterControlService and alert on compiled predicates that reference simple or scripting languages such as groovy, js, or ognl.
  • Monitor for anomalous child processes or reflective class loading initiated by the Camel runtime.

Monitoring Recommendations

  • Capture and retain message headers at the ingress of control endpoints for forensic review.
  • Alert on configuration drift that introduces new routes targeting dynamic-router-control endpoints.
  • Correlate JVM behavior with inbound traffic on transports feeding control endpoints to identify abuse patterns.

How to Mitigate CVE-2026-83531

Immediate Actions Required

  • Upgrade to Apache Camel 4.23.0, which resolves the vulnerability.
  • If running the 4.22.x stream, upgrade to 4.22.1.
  • If running the 4.18.x stream, upgrade to 4.18.5.
  • Deployments on 4.14.x or earlier must migrate to a supported release because those lines are end of life.

Patch Information

After upgrading, a control message that carries a predicate expression or an expression language is rejected unless the new allowPredicateFromMessage option is enabled on the dynamic-router-control endpoint. Enable this option only when every sender of control messages is trusted. On 4.23.0 and 4.22.1, set the allowedSchemes option on the dynamic-router endpoint to restrict which endpoints a subscription's destinationUri may reference. Fix details are tracked in Apache Camel Pull Request #25992, PR #26018, PR #26019, and PR #26020.

Workarounds

  • Do not forward messages from untrusted or shared transports to a dynamic-router-control endpoint.
  • When control messages must traverse such a transport, authenticate the sender and remove the CamelDynamicRouterPredicate and CamelDynamicRouterExpressionLanguage headers before the message reaches the endpoint.
  • Clear the predicate and expressionLanguage fields of any DynamicRouterControlMessage so the route author alone defines routing logic.
  • Restrict network access to the transports that feed control endpoints as defense in depth. Removing optional expression languages from the classpath is not a sufficient workaround.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.