Improper Neutralization of Special Elements Used in a Template Engine Affecting org.apache.camel:camel-netty-http package, versions [4.0.0,4.18.5)[4.19.0,4.22.1)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.45% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGAPACHECAMEL-21429513
  • published22 Oct 2026
  • disclosed19 Oct 2026
  • credit1428265354@qq.com

Introduced: 19 Oct 2026

NewCVE-2026-78164  (opens in a new tab)
CWE-1336  (opens in a new tab)

How to fix?

Upgrade org.apache.camel:camel-netty-http to version 4.18.5, 4.22.1 or higher.

Overview

org.apache.camel:camel-netty-http is a versatile open-source integration framework based on known Enterprise Integration Patterns.

Affected versions of this package are vulnerable to Improper Neutralization of Special Elements Used in a Template Engine via the HTTP producer URI helpers in the camel-http-common, camel-http, camel-netty-http, camel-undertow, and camel-vertx-http components. An attacker can supply {{...}} placeholders in a CamelHttpUri or CamelRestHttpUri override, causing HttpHelper, HttpMethodHelper, NettyHttpHelper, UndertowHelper, or VertxHttpHelper to evaluate them against application properties, environment variables, registered property functions, and Camel beans; this can expose secrets in outbound requests and invoke no-argument bean methods. A static producer URI is sufficient, and an exposed HTTP consumer may populate CamelHttpUri directly from the incoming request line, so the attack does not always require injecting a Camel header.

Notes

  • On the header-to-producer step, bridgeEndpoint=true does not reliably block placeholder evaluation: createMethod still resolves CamelHttpUri, and CamelRestHttpUri is consumed before bridge checks. Only camel-http offers the skipControlHeaders opt-out, which defaults to false.

Workarounds

  • Before the producer, remove CamelHttpUri and CamelRestHttpUri with removeHeader("CamelHttpUri") and removeHeader("CamelRestHttpUri") at the trust boundary to prevent message-supplied URI values from reaching placeholder evaluation.
  • For camel-http endpoints, set skipControlHeaders=true to prevent control headers from supplying URI overrides.
  • On consumers exposed to untrusted senders, apply a strict inbound HeaderFilterStrategy over the Camel namespace to block attacker-supplied Camel headers from reaching producers.
  • Resolve secrets through a vault rather than environment variables or JVM system properties, limiting disclosure of secrets through placeholder evaluation.

CVSS Base Scores

version 4.0
version 3.1