External risk intelligence

Apache Camel Docling Argument Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-40047

This vulnerability exists in the Apache Camel Docling component, which is a library used by developers to build integration routes. While it processes data that could originate from external sources, the component itself is an internal application library rather than a standalone internet-facing service, appliance, or gateway.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a vulnerability in the Apache Camel Docling component. The issue could allow for improper handling of command arguments, potentially leading to unintended command execution or directory traversal when processing external data. The main concern is confirming relevance and exposure within your specific implementations.

Component misuses external command arguments.
Unsanitized input could alter command execution.
Confirm if Docling component is used.

Attack Path

How an attacker could exploit the issue

An attacker could inject malicious arguments into the `docling` command by manipulating data sent through Apache Camel routes. This is possible because the `camel-docling` component did not sufficiently validate custom arguments before passing them to the external `docling` command-line tool. This could lead to the execution of unintended commands or directory traversal.

Requires exposure to Camel integration routes.
Triggered by supplying crafted arguments to `CamelDoclingCustomArguments`.
Risk of command injection and directory traversal.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, the `docling` command-line tool could be manipulated by specially crafted arguments passed through the `CamelDoclingCustomArguments` header. This could allow unintended command-line flags or path-like arguments to be passed to the external `docling` subprocess, potentially affecting its behavior or allowing directory traversal.

External command execution.
Malicious arguments supplied to producer.
Unintended command execution and file access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Apache Camel team is responsible for addressing this vulnerability in the Docling component. The first practical step is to identify all Camel instances utilizing the Docling component, determine their exposure and criticality, and then plan remediation based on these findings.

Camel application owners should own the issue.
Verify Camel Docling component usage and external data flow.
Plan upgrade or apply vendor-provided fixes.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Apache Camel Docling component?

Apache Camel is a framework used to build integration routes that connect different software systems. The Docling component specifically acts as an interface between these Camel routes and the external 'docling' command-line tool, allowing developers to automate document processing tasks directly within their data pipelines.

How does this CVE-2026-40047 vulnerability work?

This vulnerability is classified as CWE-88, or Argument Injection. It occurs when a program builds a command by combining user input with system commands without sufficient validation. Because the Docling component failed to strictly verify custom arguments, an attacker could supply crafted data that the component incorrectly passes as flags or path configurations to the underlying tool, rather than treating them as simple data.

Does any input trigger this flaw?

No, it is not triggered by all data. The vulnerability specifically relies on the Camel route forwarding externally-influenced content into the 'CamelDoclingCustomArguments' header. If a route does not accept input from untrusted sources or does not utilize this specific header, the flaw cannot be triggered.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that while the Apache Camel Docling component is an internal library, it processes data that could originate from external sources. Because it is not a standalone internet-facing service or gateway, the risk level depends on whether your integration routes act as an entry point for untrusted data from the internet.

What is the first step to remediate this?

First, conduct an inventory to identify all applications using the affected Apache Camel versions (4.15.0 through 4.18.2). Once identified, verify if those applications utilize the Docling component and process external data. The primary fix is to upgrade your Apache Camel dependency to a patched version, such as 4.18.3 or 4.19.0, which implements strict input validation.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.