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 06574fbcc43648fa7d507940bcbeb012aa944c58 Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Oct 19 10:36:37 2026 +0200 Added CVE-2026-95629 Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-95629.md | 25 +++++++++++++++++++++ content/security/CVE-2026-95629.txt.asc | 39 +++++++++++++++++++++++++++++++++ 2 files changed, 64 insertions(+) diff --git a/content/security/CVE-2026-95629.md b/content/security/CVE-2026-95629.md new file mode 100644 index 00000000..4ca84bcb --- /dev/null +++ b/content/security/CVE-2026-95629.md @@ -0,0 +1,25 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-95629" +date: 2026-10-19T10:00:00+02:00 +url: /security/CVE-2026-95629.html +draft: false +type: security-advisory +cve: CVE-2026-95629 +severity: MEDIUM +summary: "Camel-Docling: Unvalidated output path header enables writing conversion output to an arbitrary directory in DoclingProducer" +description: "DoclingProducer runs the external docling tool in CLI mode, the default, and tells it where to write the converted document through the --output flag. When the CamelDoclingOutputFilePath header was set, addOutputDirectoryArguments handed its value to that flag verbatim: the value was not normalized, an absolute path or a path containing .. segments was accepted as given, and no endpoint option could confine it to a directory. The custom-argument validation added by the fix [...] +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.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The fix adds an outputBaseDirectory endpoint option that is unset by default, so after upgrading, set it on every docling endpoint whose CamelDoclingOutputFilePath header can carry a value influenced from outside the deploym [...] +credit: "This issue was discovered by Zhixi \"Jace\" Sun, independent security researcher" +affected: "From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.2." +fixed: 4.18.5, 4.22.2 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24894 refers to the commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/26737 (commit 48485d408f190c46ef408ba4ba75e45b4e8ffb04), and backported to camel-4.22.x in https://github.com/apache/camel/pull/27365 (commit 4f8eb14999163523af6b77d08bfd1b9e79ee49c0) and to camel-4.18.x in https://github.com/apache/camel/pull/27362 (commit 54552df4b9e512cb2025fad22b88429ef0e0169c). + +The CamelDoclingOutputFilePath header is now normalized lexically before it is passed to docling, and a new outputBaseDirectory endpoint option confines it: when the option is set, a relative header value is resolved against that directory, and a value that resolves outside it, including an absolute path, is rejected with an IOException before docling is started. The containment is lexical and does not resolve symbolic links, as with inputBaseDirectory. The option is unset by default so [...] + +The header has reached the docling output flag unchanged since camel-docling was introduced in 4.15.0, so every release of the 4.15.x to 4.22.x lines before the fixed versions is affected, whether or not it carries the CVE-2026-40047 fix. + +This issue is related to CVE-2026-40047, which concerned insufficient validation of the CamelDoclingCustomArguments header in the same component: the validation that fix put in place refuses the output flags among the custom arguments and names this header as the way to choose the output directory, but the header itself was left unchecked. The outputBaseDirectory option is the output-side counterpart of the inputBaseDirectory option introduced by the fix for CVE-2026-78163, which concern [...] diff --git a/content/security/CVE-2026-95629.txt.asc b/content/security/CVE-2026-95629.txt.asc new file mode 100644 index 00000000..5fc81b76 --- /dev/null +++ b/content/security/CVE-2026-95629.txt.asc @@ -0,0 +1,39 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-95629" +date: 2026-10-19T10:00:00+02:00 +url: /security/CVE-2026-95629.html +draft: false +type: security-advisory +cve: CVE-2026-95629 +severity: MEDIUM +summary: "Camel-Docling: Unvalidated output path header enables writing conversion output to an arbitrary directory in DoclingProducer" +description: "DoclingProducer runs the external docling tool in CLI mode, the default, and tells it where to write the converted document through the --output flag. When the CamelDoclingOutputFilePath header was set, addOutputDirectoryArguments handed its value to that flag verbatim: the value was not normalized, an absolute path or a path containing .. segments was accepted as given, and no endpoint option could confine it to a directory. The custom-argument validation added by the fix [...] +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.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The fix adds an outputBaseDirectory endpoint option that is unset by default, so after upgrading, set it on every docling endpoint whose CamelDoclingOutputFilePath header can carry a value influenced from outside the deploym [...] +credit: "This issue was discovered by Zhixi \"Jace\" Sun, independent security researcher" +affected: "From 4.15.0 before 4.18.5, from 4.19.0 before 4.22.2." +fixed: 4.18.5, 4.22.2 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24894 refers to the commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/26737 (commit 48485d408f190c46ef408ba4ba75e45b4e8ffb04), and backported to camel-4.22.x in https://github.com/apache/camel/pull/27365 (commit 4f8eb14999163523af6b77d08bfd1b9e79ee49c0) and to camel-4.18.x in https://github.com/apache/camel/pull/27362 (commit 54552df4b9e512cb2025fad22b88429ef0e0169c). + +The CamelDoclingOutputFilePath header is now normalized lexically before it is passed to docling, and a new outputBaseDirectory endpoint option confines it: when the option is set, a relative header value is resolved against that directory, and a value that resolves outside it, including an absolute path, is rejected with an IOException before docling is started. The containment is lexical and does not resolve symbolic links, as with inputBaseDirectory. The option is unset by default so [...] + +The header has reached the docling output flag unchanged since camel-docling was introduced in 4.15.0, so every release of the 4.15.x to 4.22.x lines before the fixed versions is affected, whether or not it carries the CVE-2026-40047 fix. + +This issue is related to CVE-2026-40047, which concerned insufficient validation of the CamelDoclingCustomArguments header in the same component: the validation that fix put in place refuses the output flags among the custom arguments and names this header as the way to choose the output directory, but the header itself was left unchecked. The outputBaseDirectory option is the output-side counterpart of the inputBaseDirectory option introduced by the fix for CVE-2026-78163, which concern [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrV1j4ACgkQ406fOAL/ +QQBWuggAl/9gyftY4P5TDrfkpTd+CdiKQFc/lmVFEdqZvtAJicsjRpgOIl/Vub2f +C1PH1/IlUH/p2pd3QWzwjnp4LpHQdgRYWvC7KYFUAV0uBKRx2eduv3/0OZEN2fII +TuWgQsnAkFwiYYGZdZZVQtGaByXunWhYmxjITtW4gYvDe9nEv/aT3tN7JtTLaIGh +ePJ6JC1zP/NRQnTPceflerSkr42ga40Vjn1SEB90d8qM7lHDNqR+snYhkWggmftS +623iYWlaOgguw0DB2sGXNU5ShT19JSPYO286MEETmBp7hsDgzx99iaeRQB8XIntA +DdlSeOAWyVAfzLD33S4bTwlsYSU5PA== +=zcFr +-----END PGP SIGNATURE-----
