CVE-2026-78163

Description

A flaw was found in the Apache Camel Docling component. This issue can lead to sensitive information disclosure because the component automatically determines whether to treat input text as document content, a local file path, or an external web address based solely on its prefix. A remote attacker who can supply crafted message bodies to a Docling endpoint can exploit this behavior to read arbitrary local files or trigger Server-Side Request Forgery (SSRF) against internal services.

Statement

Red Hat Product Security rates this vulnerability as Moderate because exploitation requires a specific application routing design where untrusted remote input is forwarded directly as a plain string payload into the Docling component without prior validation. In standard Camel deployments, Docling is an optional integration component utilized only when explicitly configured within document processing routes. Although unauthorized access to local files or internal network endpoints is possible if an untrusted string prefix is processed, the flaw does not allow system modification or remote code execution.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A5.9
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactNoneN/ANone
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data

Integrity

Technical Impact: Execute Unauthorized Code or Commands

Access Control

Technical Impact: Bypass Protection Mechanism

By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.

Frequently Asked Questions

Want to get errata notifications? Sign up here.