{"metadata": {"vulnerability": "CVE-2026-78164", "count": 16, "kinds": {"milestone": 4, "sighting": 4, "kev": 0, "other": 8}}, "data": [{"timestamp": "2026-08-23T12:51:36.176Z", "date_only": false, "value": "2026-08-23T12:51:36.176Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-10-16T15:00:16Z", "date_only": false, "value": "2026-10-16T15:00:16.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "Telegram/oa5k6kBfthQUe5_2xq482d0JhIx-P9f36xq_0Zd47RbfMV0", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "26aad2b7-abae-4883-85d7-a8dfa51aac7f", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, {"timestamp": "2026-10-16T15:00:16Z", "date_only": false, "value": "2026-10-16T15:00:16.000000Z", "kind": "sighting", "label": "Seen", "source": "Telegram/oa5k6kBfthQUe5_2xq482d0JhIx-P9f36xq_0Zd47RbfMV0", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "7f140818-5de0-4fe5-a478-a3f9153fdeaa"}, {"timestamp": "2026-10-19T10:07:40.078Z", "date_only": false, "value": "2026-10-19T10:07:40.078Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T10:22:40.879Z", "date_only": false, "value": "2026-10-19T10:22:40.879238Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117467077694029333", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "97c00f62-066f-4e77-a386-932f9a62b1e5", "content": "CVE-2026-78164 Apache Camel: HTTP producers resolve property placeholders in message-supplied URI override headers Improper Neutralization of Special Elements Used in a Template Engine and Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP, Netty HTTP, Undertow and Vert.x HTTP components.\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\nThe Camel HTTP producer families let an inbound message override the endpoint URI through the CamelHttpUri and CamelRestHttpUri headers, and then passed that message-supplied string through CamelContext.resolvePropertyPlaceholders() before using it. Property-placeholder resolution is a configuration-resolution facility, not a URI-parsing step: it reaches operating-system environment variables, JVM system properties, every PropertiesFunction registered on the classpath - including the AWS, Azure, GCP, HashiCorp, IBM, CyberArk and Kubernetes secret functions - and, through camel-bean, the invocation of a no-argument method on any bean in the registry. Applying it to Exchange content therefore turned a URI string into a configuration- and bean-evaluation context. A route author opted into none of this: a plain static to(\"http://backend/api\") was sufficient. Seven call sites were affected: HttpHelper.createURL and HttpHelper.createMethod in camel-http-common, HttpMethodHelper.createMethod in camel-http, VertxHttpHelper.resolveHttpURI in camel-vertx-http, UndertowHelper.createURL and UndertowHelper.createMethod in camel-undertow, and NettyHttpHelper.createURL in camel-netty-http. The bridgeEndpoint option did not bound the exposure: it suppresses the CamelHttpUri override in the createURL family but not in the createMethod family, so a route using the documented bridging configuration still resolved placeholders taken from the header, and CamelRestHttpUri was consumed before any bridgeEndpoint check in all four components. Only camel-http offered an opt-out, skipControlHeaders, which defaults to false. Reaching the headers did not always require header injection, because several Camel HTTP consumers populate CamelHttpUri from the request line themselves as a documented reverse-proxy feature. An unresolvable placeholder additionally produced a RuntimeExchangeException whose message echoed the URI, which distinguishes a set from an unset configuration key even where no outbound request is made. The behaviour predates the 4.x line; it dates back to the camel-http4 and camel-netty4 components. This advisory continues the alignment CAMEL-24282 applied to the toD and enrich dynamic-URI EIPs in 4.22.0, extending the same build-time-resolution contract to the HTTP producer components.\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.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 immediately, strip the override headers at the trust boundary before the producer with removeHeader(\"CamelHttpUri\") and removeHeader(\"CamelRestHttpUri\"), or set skipControlHeaders=true on camel-http endpoints, which is the only component offering that option. Note that bridgeEndpoint=true is not a workaround: it suppresses the header override when the outbound URL is built but not when the header is re-parsed for the query string. Percent-encoding the placeholder delimiters is likewise not a mitigation for camel-netty-http, whose binding decodes the request path before the value reaches the header, so proxy or WAF rules written against the raw delimiters do not help there. As defence in depth, ensure consumers exposed to untrusted senders apply a strict inbound HeaderFilterStrategy over the Camel namespace, and resolve secrets through a vault rather than through environment variables or system properties that a placeholder can name.\nhttps://www.cve.org/CVERecord?id=CVE-2026-78164https://camel.apache.org/security/CVE-2026-78164.htmlhttps://issues.apache.org/jira/browse/CAMEL-24418https://github.com/apache/camel/pull/25571https://github.com/apache/camel/commit/ba5aced7f6a1c38a963020575676ad4c76b492cfhttps://github.com/apache/camel/commit/9f8a185e315ce9e120889c4106be3dbf4688e507https://github.com/apache/camel/commit/7cec534c66969015d85e56631143174dd150ed94#apache #ApacheSoftwareFoundation #ApacheCamel#CVE_2026_78164#bot", "url": "https://infosec.exchange/users/cve/statuses/117467077694029333"}, {"timestamp": "2026-10-19T11:17:19Z", "date_only": false, "value": "2026-10-19T11:17:19Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-394J-CC2X-W9WM", "record": "GHSA-394J-CC2X-W9WM", "field": "database_specific.nvd_published_at"}, {"timestamp": "2026-10-19T11:17:19.403Z", "date_only": false, "value": "2026-10-19T11:17:19.403", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-78164", "record": "FKIE_CVE-2026-78164", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T12:03:40.078Z", "date_only": false, "value": "2026-10-19T12:03:40.078Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / apache", "record": "CVE-2026-78164", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-19T12:32:49Z", "date_only": false, "value": "2026-10-19T12:32:49Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-394J-CC2X-W9WM", "record": "GHSA-394J-CC2X-W9WM", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-19T12:32:49Z", "date_only": false, "value": "2026-10-19T12:32:49Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-394J-CC2X-W9WM", "record": "GHSA-394J-CC2X-W9WM", "field": "modified"}, {"timestamp": "2026-10-19T18:45:34.527Z", "date_only": false, "value": "2026-10-19T18:45:34.527963Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-78164", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2026-10-19T18:45:34.527Z", "date_only": false, "value": "2026-10-19T18:45:34.527963Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-78164", "record": "FKIE_CVE-2026-78164", "field": "metrics.ssvcV203.0.ssvcData.timestamp"}, {"timestamp": "2026-10-19T18:46:16.020Z", "date_only": false, "value": "2026-10-19T18:46:16.020Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-10-19T18:46:16.020Z", "date_only": false, "value": "2026-10-19T18:46:16.020Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-78164", "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-78164", "record": "FKIE_CVE-2026-78164", "field": "lastModified"}, {"timestamp": "2026-10-26T09:09:40.725Z", "date_only": false, "value": "2026-10-26T09:09:40.725591Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117506426807598933", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "d6ad5892-132f-402f-ba47-99fca8ce66c9", "content": "CVE-2026-95664 Apache Camel: Camel-AWS2-S3 Producer Evaluates Untrusted S3 Object Keys From the CamelAwsS3Key Header as Simple Expressions Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') vulnerability in Apache Camel AWS2-s3 component.\nThis issue affects Apache Camel: from 4.8.0 before 4.18.5, from 4.19.0 before 4.22.2.\nFor the object it uploads, reads or deletes, the camel-aws2-s3 producer takes the key from the CamelAwsS3Key message header and falls back to the keyName option configured on the endpoint only when that header is absent. Since 4.8.0, AWS2S3Utils.determineKey() also passed the resulting value to the Simple language whenever it contained ${ or $simple{, so that a route could use a dynamic key, and the evaluation applied to a value taken from the header as well as to the configured option. The header is not route configuration, however: the aws2-s3 consumer sets CamelAwsS3Key on the exchanges it creates to the key of the object it read, that is, the name of the object in the bucket. In a route that does nothing more than consume from one aws2-s3 endpoint and produce to another, the name of each consumed object therefore reached the producer, and a name containing either marker was evaluated as an expression, although the route author never asked for any evaluation, and configuring keyName on the producer did not prevent it, because the header took precedence. A key that a route copied into the header from other message content was evaluated in the same way. Anyone able to choose the name of an object in a bucket that such a route consumes, typically a principal allowed to upload to that bucket, could therefore have Simple expressions of their choosing evaluated in the Camel process. The Simple language can read JVM system properties, environment variables and configuration properties, which commonly carry credentials, and, where camel-bean is on the classpath, invoke methods on beans in the registry. The evaluated result became the key the producer used, so reading a value back additionally required the ability to see object names in the destination bucket, while a method invocation took effect without it; together with the need to name an object in a consumed bucket, this is why the severity is assessed medium. The bucket name went through the same evaluation, but the consumer only ever places the bucket configured on its own endpoint in a bucket header, never a value derived from a remote object, so the bucket name was not reachable in this way. Releases before 4.8.0 used the key from the header as given and are not affected.\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.8.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. After upgrading, a key or bucket name supplied through a message header is used literally, so a route that put an unevaluated Simple expression in the CamelAwsS3Key or CamelAwsS3OverrideBucketName header must evaluate it in the route instead, for example with setHeader and simple(), or configure it as the keyName or bucketName option of the endpoint. For deployments that cannot upgrade immediately, do not let a key derived from an object name or from other untrusted message content reach an aws2-s3 producer unchecked: in routes that pass exchanges from an aws2-s3 consumer to an aws2-s3 producer, either remove the CamelAwsS3Key header before the producer with removeHeader(\u201cCamelAwsS3Key\u201d), so that the keyName configured on the endpoint is used, or reject exchanges whose CamelAwsS3Key header contains ${ or $simple{. Configuring keyName alone is not a workaround, because the header takes precedence over it. As defence in depth, allow only trusted principals to write to buckets that Camel routes consume.\nhttps://www.cve.org/CVERecord?id=CVE-2026-95664https://camel.apache.org/security/CVE-2026-95664.htmlhttps://issues.apache.org/jira/browse/CAMEL-24901https://github.com/apache/camel/pull/26746https://github.com/apache/camel/pull/26840https://github.com/apache/camel/pull/26842https://github.com/apache/camel/pull/26841https://github.com/apache/camel/pull/26889https://issues.apache.org/jira/browse/CAMEL-20971https://camel.apache.org/security/CVE-2026-78164.htmlhttps://camel.apache.org/security/CVE-2026-83531.htmlhttps://camel.apache.org/security/CVE-2025-27636.html#apache #ApacheSoftwareFoundation #ApacheCamel#CVE_2026_95664#bot", "url": "https://infosec.exchange/users/cve/statuses/117506426807598933"}], "metrics": {"as_of": "2026-11-02T05:23:52.842Z", "anchors": {"origin": {"timestamp": "2026-10-19T10:07:40.078Z", "date_only": false, "value": "2026-10-19T10:07:40.078Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-10-19T10:07:40.078Z", "date_only": false, "value": "2026-10-19T10:07:40.078Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": {"timestamp": "2026-10-16T15:00:16Z", "date_only": false, "value": "2026-10-16T15:00:16.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "Telegram/oa5k6kBfthQUe5_2xq482d0JhIx-P9f36xq_0Zd47RbfMV0", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "26aad2b7-abae-4883-85d7-a8dfa51aac7f", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "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": true, "seconds": -241644.078, "hours": -67.123355, "days": -2.7968064583333336, "min_seconds": -241644.078, "max_seconds": -241644.078, "approximate": false, "ongoing": false, "order_known": true, "batch_listing": false, "end_before_start": true, "start": {"timestamp": "2026-10-19T10:07:40.078Z", "date_only": false, "value": "2026-10-19T10:07:40.078Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-10-16T15:00:16Z", "date_only": false, "value": "2026-10-16T15:00:16.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "Telegram/oa5k6kBfthQUe5_2xq482d0JhIx-P9f36xq_0Zd47RbfMV0", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "26aad2b7-abae-4883-85d7-a8dfa51aac7f", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}}, "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": 1192572.764746, "hours": 331.2702124294445, "days": 13.802925517893518, "min_seconds": 1192572.764746, "max_seconds": 1192572.764746, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-10-19T10:07:40.078Z", "date_only": false, "value": "2026-10-19T10:07:40.078Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-78164", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-02T05:23:52.842Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": true, "seconds": 1434216.842746, "hours": 398.39356742944443, "days": 16.599731976226852, "min_seconds": 1434216.842746, "max_seconds": 1434216.842746, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-10-16T15:00:16Z", "date_only": false, "value": "2026-10-16T15:00:16.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "Telegram/oa5k6kBfthQUe5_2xq482d0JhIx-P9f36xq_0Zd47RbfMV0", "record": "CVE-2026-78164", "field": "creation_timestamp", "uuid": "26aad2b7-abae-4883-85d7-a8dfa51aac7f", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "end": {"timestamp": "2026-11-02T05:23:52.842Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}}}