← Back
CVE-2026-40047
critical
CVSS 9.1
Vulnerability in org.apache.camel:camel-docling (CVE-2026-40047)
Summary
vulnerability in org.apache.camel:camel-docling (CVE-2026-40047). Confidential information can be exposed externally. Exploitable via ``docling``. Mitigation: upgrade to `4.18.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40047** has been found in org.apache.camel:camel-docling.
Attackers can target a specific entry point like ``docling`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade org.apache.camel:camel-docling to **4.18.3** or later.
If unsure, ask your IT team or search "org.apache.camel:camel-docling CVE-2026-40047" on the vendor's site.
CVE-2026-40047 (org.apache.camel:camel-docling) — CWE-88 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `docling` / `CamelDoclingCustomArguments`
Patched: `4.18.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-88) exists in org.apache.camel:camel-docling. Attackers reach the vulnerable code path via ``docling`` without authentication.
📍 Affected scope
org.apache.camel:camel-docling — . Attack surface: `docling` / `CamelDoclingCustomArguments`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.18.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.apache.camel:camel-docling' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.apache.camel:camel-docling' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.camel:camel-docling` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.camel:camel-docling to 4.18.3ステージング環境で 4.18.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.camel:camel-docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.3"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-40047
- web https://camel.apache.org/security/CVE-2026-40047.html
- web https://github.com/advisories/GHSA-rpv3-6645-2vqc
- web http://www.openwall.com/lists/oss-security/2026/07/05/2
- web https://github.com/apache/camel/pull/22082
- web https://github.com/apache/camel/pull/22767
- web https://github.com/apache/camel/commit/1fa56f45901f50aa79849ff2d2ca83dd57f6991c
- web https://github.com/apache/camel/commit/f86fda0442c65b9d13ce3aa8ac676233b64e3351
- web https://github.com/apache/camel/releases/tag/camel-4.18.3
- web https://github.com/apache/camel/releases/tag/camel-4.19.0
- web https://issues.apache.org/jira/browse/CAMEL-23212