{"metadata": {"vulnerability": "CVE-2026-85257", "count": 15, "kinds": {"milestone": 4, "sighting": 3, "kev": 0, "other": 8}}, "data": [{"timestamp": "2026-09-03T16:34:33.777Z", "date_only": false, "value": "2026-09-03T16:34:33.777Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-10-19T10:37:14.792Z", "date_only": false, "value": "2026-10-19T10:37:14.792Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T10:37:14.792Z", "date_only": false, "value": "2026-10-19T10:37:14.792Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / apache", "record": "CVE-2026-85257", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-19T10:52:21.724Z", "date_only": false, "value": "2026-10-19T10:52:21.724912Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117467194367665958", "record": "CVE-2026-85257", "field": "creation_timestamp", "uuid": "e6af3dd4-35e0-4ceb-89ef-ca7895edd7cd", "content": "CVE-2026-85257 Apache Camel: Camel-CXF Information Disclosure via Unmuted Consumer Exceptions Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF component.\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\nWhen a route behind a CXF SOAP consumer failed with an exception the service contract does not declare, the exception was described back to the SOAP client in the fault: CXF copies the message into the SOAP faultstring, and can be configured to place the stack trace in the fault detail. An external caller able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever the exception message carries. Declared faults, annotated @WebFault, are a different matter: those are part of the published contract that clients are written against, and suppressing them would break the service rather than protect anything.\nUpgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, replaces an undeclared route failure with a generic fault carrying no class name, message or stack trace. Faults the contract declares are reported exactly as before. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, declare the exceptions the service is allowed to report and map every other failure onto one of them in an onException handler, so no undeclared exception reaches the fault.\nhttps://www.cve.org/CVERecord?id=CVE-2026-85257https://camel.apache.org/security/CVE-2026-85257.htmlhttps://issues.apache.org/jira/browse/CAMEL-24477https://github.com/apache/camel/pull/25742https://github.com/apache/camel/pull/25934https://github.com/apache/camel/pull/25935#apache #ApacheSoftwareFoundation #ApacheCamel#CVE_2026_85257#bot", "url": "https://infosec.exchange/users/cve/statuses/117467194367665958"}, {"timestamp": "2026-10-19T11:17:23Z", "date_only": false, "value": "2026-10-19T11:17:23Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-G4W9-7494-9R66", "record": "GHSA-G4W9-7494-9R66", "field": "database_specific.nvd_published_at"}, {"timestamp": "2026-10-19T11:17:23.690Z", "date_only": false, "value": "2026-10-19T11:17:23.690", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-85257", "record": "FKIE_CVE-2026-85257", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T12:32:51Z", "date_only": false, "value": "2026-10-19T12:32:51Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-G4W9-7494-9R66", "record": "GHSA-G4W9-7494-9R66", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T12:32:51Z", "date_only": false, "value": "2026-10-19T12:32:51Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-G4W9-7494-9R66", "record": "GHSA-G4W9-7494-9R66", "field": "modified"}, {"timestamp": "2026-10-19T16:47:36.190Z", "date_only": false, "value": "2026-10-19T16:47:36.190817Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-85257", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2026-10-19T16:47:36.190Z", "date_only": false, "value": "2026-10-19T16:47:36.190817Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-85257", "record": "FKIE_CVE-2026-85257", "field": "metrics.ssvcV203.0.ssvcData.timestamp"}, {"timestamp": "2026-10-19T16:47:59.389Z", "date_only": false, "value": "2026-10-19T16:47:59.389Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-10-19T16:47:59.389Z", "date_only": false, "value": "2026-10-19T16:47:59.389Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-85257", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-19T20:45:51.597Z", "date_only": false, "value": "2026-10-19T20:45:51.597", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-85257", "record": "FKIE_CVE-2026-85257", "field": "lastModified"}, {"timestamp": "2026-10-20T09:00:04Z", "date_only": false, "value": "2026-10-20T09:00:04.000000Z", "kind": "sighting", "label": "Seen", "source": "Telegram/XQ44nJIS1y3VwXCLwTpA_EDVRw0SXiZheBrhtKuaC-KdRLk", "record": "CVE-2026-85257", "field": "creation_timestamp", "uuid": "b48eefa5-1e6f-465a-bb83-867f284007ef"}, {"timestamp": "2026-10-26T09:00:55.100Z", "date_only": false, "value": "2026-10-26T09:00:55.100340Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117506392349782290", "record": "CVE-2026-85257", "field": "creation_timestamp", "uuid": "409339e5-4fa7-4c7b-bf87-9668befbc8e6", "content": "CVE-2026-101259 Apache Camel: Camel-CoAP Information Disclosure via Unmuted Consumer Exceptions Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CoAP component.\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.2.\nWhen 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. Reaching the disclosure therefore requires a route whose completed response a remote client can make unconvertible, which depends on how the route is written.\nUsers 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 supported release. The upgrade is enough on its own: the new muteException consumer option defaults to true on all three fixed release lines, so the error response carries no payload without any configuration change. For deployments that cannot upgrade immediately, make sure the response can always be built once the route has completed: convert the body to byte[] or String as the last step of each route that consumes from a coap endpoint, for example with convertBodyTo, give the CamelCoapMaxAge and CamelCoapETag headers only values of their own types, and add an onException handler that marks the failure as handled and sets the response body explicitly, so that a conversion failure is raised and replaced inside the route rather than in the consumer.\nhttps://www.cve.org/CVERecord?id=CVE-2026-101259https://camel.apache.org/security/CVE-2026-101259.htmlhttps://issues.apache.org/jira/browse/CAMEL-25087https://github.com/apache/camel/pull/26994https://github.com/apache/camel/pull/27046https://github.com/apache/camel/pull/27048https://camel.apache.org/security/CVE-2026-84180.htmlhttps://camel.apache.org/security/CVE-2026-85246.htmlhttps://camel.apache.org/security/CVE-2026-85257.htmlhttps://camel.apache.org/security/CVE-2026-85315.html#apache #ApacheSoftwareFoundation #ApacheCamel#CVE_2026_101259#bot", "url": "https://infosec.exchange/users/cve/statuses/117506392349782290"}], "metrics": {"as_of": "2026-10-29T17:07:38.930Z", "anchors": {"origin": {"timestamp": "2026-10-19T10:37:14.792Z", "date_only": false, "value": "2026-10-19T10:37:14.792Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-10-19T10:37:14.792Z", "date_only": false, "value": "2026-10-19T10:37:14.792Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 887424.138852, "hours": 246.50670523666668, "days": 10.271112718194445, "min_seconds": 887424.138852, "max_seconds": 887424.138852, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-10-19T10:37:14.792Z", "date_only": false, "value": "2026-10-19T10:37:14.792Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-85257", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-10-29T17:07:38.930Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}