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 3c87a46257e114e1310e3f7a3a50dcd52ed914a6 Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Oct 19 10:36:38 2026 +0200 Added CVE-2026-101259 Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-101259.md | 25 ++++++++++++++++++++ content/security/CVE-2026-101259.txt.asc | 39 ++++++++++++++++++++++++++++++++ 2 files changed, 64 insertions(+) diff --git a/content/security/CVE-2026-101259.md b/content/security/CVE-2026-101259.md new file mode 100644 index 00000000..3e557a40 --- /dev/null +++ b/content/security/CVE-2026-101259.md @@ -0,0 +1,25 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-101259" +date: 2026-10-19T10:00:00+02:00 +url: /security/CVE-2026-101259.html +draft: false +type: security-advisory +cve: CVE-2026-101259 +severity: MEDIUM +summary: "Camel-CoAP: information disclosure - when the consumer could not build its response once the route had completed, the exception's message was sent to the CoAP client as the payload of the 5.00 response, so an internal error message reached an external client" +description: "When the CoAP consumer could not build its response once the route had completed, CamelCoapResource caught the resulting exception and sent its message back to the CoAP client as the payload of a 5.00 Internal Server Error response. The typical case is a type conversion failure: the consumer converts the final message body to the byte[] payload, and the CamelCoapMaxAge and CamelCoapETag headers to their types, after the route has returned, and therefore outside the route's [...] +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 4.14.x releases stream and earlier, and 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 suppor [...] +credit: "This issue was discovered by Zhixi \"Jace\" Sun, independent security researcher" +affected: "From 4.0.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-25087 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/26994 (commit 2245feac8f4f9a85404b01d36114abdac504e7d1), and backported to camel-4.22.x in https://github.com/apache/camel/pull/27046 (commit 868d56044119a8a975f583b63aeb9666cd952a88) and to camel-4.18.x in https://github.com/apache/camel/pull/27048 (commit aaf5bbf81ede12837c9c65fa9106643fcb58b7c4). + +The fix gives the CoAP consumer a muteException option, on the coap, coaps, coap+tcp and coaps+tcp endpoints alike, which defaults to true on all three release lines. When the response cannot be built once the route has completed, the consumer still answers with 5.00 Internal Server Error, but with an empty payload, and it now reports the exception through the consumer's exception handler, so muting it does not hide it from the operator. The consumer also checks whether the exchange fail [...] + +The consumer has returned the message of such an exception to the client since camel-coap was introduced in 2.16.0, and that code was unchanged until the fix, so every 4.x release before the fixed versions is affected, including Rest DSL services exposed through camel-coap. + +This is the CoAP member of the unmuted-consumer-exception family published as CVE-2026-84180 (camel-knative), CVE-2026-85246 (camel-mina), CVE-2026-85257 (camel-cxf) and CVE-2026-85315 (camel-grpc), and the new option follows the same muteException convention. Unlike those consumers, the CoAP consumer did not return the exception of a failing route, only one raised while it built the response after the route had completed. It is classified as CWE-209 (Generation of Error Message Containi [...] diff --git a/content/security/CVE-2026-101259.txt.asc b/content/security/CVE-2026-101259.txt.asc new file mode 100644 index 00000000..b766058b --- /dev/null +++ b/content/security/CVE-2026-101259.txt.asc @@ -0,0 +1,39 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-101259" +date: 2026-10-19T10:00:00+02:00 +url: /security/CVE-2026-101259.html +draft: false +type: security-advisory +cve: CVE-2026-101259 +severity: MEDIUM +summary: "Camel-CoAP: information disclosure - when the consumer could not build its response once the route had completed, the exception's message was sent to the CoAP client as the payload of the 5.00 response, so an internal error message reached an external client" +description: "When the CoAP consumer could not build its response once the route had completed, CamelCoapResource caught the resulting exception and sent its message back to the CoAP client as the payload of a 5.00 Internal Server Error response. The typical case is a type conversion failure: the consumer converts the final message body to the byte[] payload, and the CamelCoapMaxAge and CamelCoapETag headers to their types, after the route has returned, and therefore outside the route's [...] +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 4.14.x releases stream and earlier, and 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 suppor [...] +credit: "This issue was discovered by Zhixi \"Jace\" Sun, independent security researcher" +affected: "From 4.0.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-25087 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/26994 (commit 2245feac8f4f9a85404b01d36114abdac504e7d1), and backported to camel-4.22.x in https://github.com/apache/camel/pull/27046 (commit 868d56044119a8a975f583b63aeb9666cd952a88) and to camel-4.18.x in https://github.com/apache/camel/pull/27048 (commit aaf5bbf81ede12837c9c65fa9106643fcb58b7c4). + +The fix gives the CoAP consumer a muteException option, on the coap, coaps, coap+tcp and coaps+tcp endpoints alike, which defaults to true on all three release lines. When the response cannot be built once the route has completed, the consumer still answers with 5.00 Internal Server Error, but with an empty payload, and it now reports the exception through the consumer's exception handler, so muting it does not hide it from the operator. The consumer also checks whether the exchange fail [...] + +The consumer has returned the message of such an exception to the client since camel-coap was introduced in 2.16.0, and that code was unchanged until the fix, so every 4.x release before the fixed versions is affected, including Rest DSL services exposed through camel-coap. + +This is the CoAP member of the unmuted-consumer-exception family published as CVE-2026-84180 (camel-knative), CVE-2026-85246 (camel-mina), CVE-2026-85257 (camel-cxf) and CVE-2026-85315 (camel-grpc), and the new option follows the same muteException convention. Unlike those consumers, the CoAP consumer did not return the exception of a failing route, only one raised while it built the response after the route had completed. It is classified as CWE-209 (Generation of Error Message Containi [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrV1j4ACgkQ406fOAL/ +QQAUegf+OmGMt7gRzwR2Ye7H9iQ9dkQ8n7rafb59GoF4yACu6UcvSfYkQnbjNGW5 +/kIdIEHvpukcRvd/1CEPJAunZlO11KqIDG2905rIBLm+QXaynOaL/rYMc+g23D5+ +ibK1jglvtPnZyA9GKAJMLcYROgDTxgYB8ozX7erZC5GjFGBxxSuI/RwIBhHJZTtg +TKVX/jbz1LiVN0zB4EzeY3vJYSJz5OgeOG7H4BlBFckJFLaxUnOVTSEHLsOdADy1 +RiGcsuD6JFfdbV1HIT/cLq0VPavRGESkCX1+ebNB/MGO5/T+9x+56mG04ylWMeBw +5R4gjSynJR8X1HHnniZaa2ubMSp4OA== +=/IbH +-----END PGP SIGNATURE-----
