This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 4e9408cdb1a4de01af26df79b8b85f6df1cf05cd Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Oct 12 17:47:31 2026 +0200 Restore quoting and correct the mitigation in CVE-2026-78163 A later edit dropped the quotation marks around "convert whatever text arrives in the body", which left the sentence hard to parse; they are restored. The mitigation said the 4.14.x line and earlier would not receive a fix, but camel-docling first shipped in 4.15.0, so those releases are not affected at all. It now names the end-of-life lines inside the affected ranges, 4.15.x to 4.17.x and 4.19.x to 4.21.x. The same statement is dropped from the closing paragraph, where it would repeat the mitigation. Both fields feed the CVE record, so the .txt.asc is re-signed. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-78163.md | 6 +++--- content/security/CVE-2026-78163.txt.asc | 22 +++++++++++----------- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/security/CVE-2026-78163.md b/content/security/CVE-2026-78163.md index b1d2b74b..41604431 100644 --- a/content/security/CVE-2026-78163.md +++ b/content/security/CVE-2026-78163.md @@ -7,8 +7,8 @@ type: security-advisory cve: CVE-2026-78163 severity: MEDIUM summary: "Camel-Docling: Unvalidated message body input source enables server-side request forgery and local file disclosure in DoclingProducer" -description: "DoclingProducer decided what a String message body meant by inspecting its prefix. A body starting with http:// or https:// was handed to Docling as a remote URL to fetch, a body starting with / or containing a backslash was read from the local filesystem, and anything else was written to a temporary file and converted as document content. The mode was chosen implicitly and no endpoint option allowed a route author to pin the component to a single interpretation, so a route [...] -mitigation: "Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immedi [...] +description: "DoclingProducer decided what a String message body meant by inspecting its prefix. A body starting with http:// or https:// was handed to Docling as a remote URL to fetch, a body starting with / or containing a backslash was read from the local filesystem, and anything else was written to a temporary file and converted as document content. The mode was chosen implicitly and no endpoint option allowed a route author to pin the component to a single interpretation, so a route [...] +mitigation: "Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgr [...] credit: "This issue was discovered by Li Zhiyao (BUPT)" affected: "From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1." fixed: 4.18.5, 4.22.1 and 4.23.0 @@ -20,6 +20,6 @@ The fix was merged on main in https://github.com/apache/camel/pull/25596 (commit A String message body is now treated as the document itself by default. The two location readings became opt-in through two new endpoint options, allowUrlSource and allowFilePathSource, both defaulting to false; a body that looks like a URL or a path is otherwise rejected with an IllegalArgumentException naming the option that would enable it. A further inputBaseDirectory option, unset by default, confines every local input path to a configured directory, normalizing lexically and compar [...] -The local file disclosure has been present since camel-docling was introduced in 4.15.0. The remote URL sink was added later, in 4.16.0, when docling-serve support was introduced, so releases in the 4.15.x line are affected by the file disclosure only. The 4.15.x to 4.17.x and 4.19.x to 4.21.x lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. +The local file disclosure has been present since camel-docling was introduced in 4.15.0. The remote URL sink was added later, in 4.16.0, when docling-serve support was introduced, so releases in the 4.15.x line are affected by the file disclosure only. This advisory is distinct from CVE-2026-40047, which concerned insufficient validation of the CamelDoclingCustomArguments header in the same component and was fixed in 4.18.3 and 4.19.0. That fix was scoped to the custom-argument allowlist and did not touch the body-derived input path described here. Reaching this issue is also easier, because the Camel header namespace is filtered at consumer boundaries by the default HeaderFilterStrategy whereas the message body never is. It is classif [...] diff --git a/content/security/CVE-2026-78163.txt.asc b/content/security/CVE-2026-78163.txt.asc index a5301b42..7d8f564d 100644 --- a/content/security/CVE-2026-78163.txt.asc +++ b/content/security/CVE-2026-78163.txt.asc @@ -10,8 +10,8 @@ type: security-advisory cve: CVE-2026-78163 severity: MEDIUM summary: "Camel-Docling: Unvalidated message body input source enables server-side request forgery and local file disclosure in DoclingProducer" -description: "DoclingProducer decided what a String message body meant by inspecting its prefix. A body starting with http:// or https:// was handed to Docling as a remote URL to fetch, a body starting with / or containing a backslash was read from the local filesystem, and anything else was written to a temporary file and converted as document content. The mode was chosen implicitly and no endpoint option allowed a route author to pin the component to a single interpretation, so a route [...] -mitigation: "Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immedi [...] +description: "DoclingProducer decided what a String message body meant by inspecting its prefix. A body starting with http:// or https:// was handed to Docling as a remote URL to fetch, a body starting with / or containing a backslash was read from the local filesystem, and anything else was written to a temporary file and converted as document content. The mode was chosen implicitly and no endpoint option allowed a route author to pin the component to a single interpretation, so a route [...] +mitigation: "Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgr [...] credit: "This issue was discovered by Li Zhiyao (BUPT)" affected: "From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1." fixed: 4.18.5, 4.22.1 and 4.23.0 @@ -23,17 +23,17 @@ The fix was merged on main in https://github.com/apache/camel/pull/25596 (commit A String message body is now treated as the document itself by default. The two location readings became opt-in through two new endpoint options, allowUrlSource and allowFilePathSource, both defaulting to false; a body that looks like a URL or a path is otherwise rejected with an IllegalArgumentException naming the option that would enable it. A further inputBaseDirectory option, unset by default, confines every local input path to a configured directory, normalizing lexically and compar [...] -The local file disclosure has been present since camel-docling was introduced in 4.15.0. The remote URL sink was added later, in 4.16.0, when docling-serve support was introduced, so releases in the 4.15.x line are affected by the file disclosure only. The 4.15.x to 4.17.x and 4.19.x to 4.21.x lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. +The local file disclosure has been present since camel-docling was introduced in 4.15.0. The remote URL sink was added later, in 4.16.0, when docling-serve support was introduced, so releases in the 4.15.x line are affected by the file disclosure only. This advisory is distinct from CVE-2026-40047, which concerned insufficient validation of the CamelDoclingCustomArguments header in the same component and was fixed in 4.18.3 and 4.19.0. That fix was scoped to the custom-argument allowlist and did not touch the body-derived input path described here. Reaching this issue is also easier, because the Camel header namespace is filtered at consumer boundaries by the default HeaderFilterStrategy whereas the message body never is. It is classif [...] -----BEGIN PGP SIGNATURE----- -iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrM1+EACgkQ406fOAL/ -QQATnAf/Z3GRQcU04gAHc8/vfOtqbjoQ+lGgee4qmEA+rp0WCSlVtkXXduY4z3so -oovRm+sV/HrNVKowLJKTafxG+zBcgyFRjehX5VeHE7P8VxEykl5oH0t9XX59pptX -D8PVYMTZ8vzpOYZvwASXwYfnMsJHjxSThSnQ4bUkO3ZvXQCv05VI4+ZLC/XWJSel -zLAA1mkJ/JAGiGq4ra3t3Jglfz4dNHbjnrS9tgScaCBnQU3tYr8LPmRqvUlx7iUv -23FN6cnt9+Ob28ulTUde4y5Ig4/TXen43kvmxhr10F+FpStYZ9a/5lrapncfvY7W -8Ugs0IeW225oonk0mCTHRSHTmbzIBA== -=wqNB +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrNAQAACgkQ406fOAL/ +QQApBQgAkO5qHX0Tqk0KHvpkr5Wafjj/FLUFarsLr/y6MkSgqvsumJsfdtp3pUap +11lwN3vakVhUPy+HbfZ7xEWXs2t5qUvWrHQV4bc+MA6u7BRT3s+GnCe4COBX3wdW +qeG0/qLyxvmreDN0AqCdsFZ6XdQTnT7W17raD4vCoR7LyZCUl1eIHOUJRPo5QBZO +OcbogUZEE+u+D02LgUcNomHXm5RDEbpImMkFVSeyci1Qu+tqZ/Vk7TgqYbXYx5hZ +RAr8HS77uZlwZ8KUhDSxuS/fZyTnr9DfWYSetmYxjRnzEnn+xXd2K5kzo75pNqfe +HpPBNfsKoaIDNlMX2oFr+eQOON9xXg== +=tLix -----END PGP SIGNATURE-----
