Skip to content
Medium 5.3

Apache Camel: Camel-CoAP Information Disclosure via Unmuted Consumer Exceptions

CVE-2026-101259 First seen on SecPulse

Affected packages

EcosystemPackageAffectedFixed
Apache Software Foundation Apache Camel
≥ 4.0.0, < 4.18.5
≥ 4.19.0, < 4.22.2
4.18.5
4.22.2
Original description The description as published by the source.

Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CoAP component.

This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.2.

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 error handler. On the affected releases the message of such a failure names the class of the value being converted, carries the value's string form, and ends with the class name and message of the underlying cause, so a remote CoAP client could read internal detail about the deployment: class and package names, the string form of the value, such as the path of a file body, and whatever the cause carries, which in practice can include paths, host names and connection detail of a backend. The consumer had no option to suppress this, unlike the HTTP consumers, which offer a muteException option for that purpose. The exception raised by a failing route was not sent: the consumer did not check whether the exchange had failed, and answered a route failure with 2.05 Content and whatever body the message held at that point.…

Source: oss-security (Openwall) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details