Search: camel.server.path
17 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 5.3 | EPSS 0.6% | Medium5.3EPSS 0.6%CVE Database V5CVE-2026-101259 CVE-2026-101259 is a vulnerability in the Apache Camel CoAP component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.2. It allows generation of error messages containing sensitive information such as class names, file paths, hostnames, and connection details in the payload of 5.00 Internal Server Error responses. This occurs when the CoAP consumer fails to build its response after route completion, exposing internal deployment details to remote clients. The issue is fixed in Apache Camel versions 4.18.5, 4.22.2, and 4.23.0. Users are advised to upgrade to these versions or apply recommended mitigations if immediate upgrade is not possible. | CVE Database V5 | ||
| Low | 3.7 | EPSS 0.3% | CVE-2026-114370Red Hat build of Apache Camel for Spring Boot 4 · Improper Limitation of a Pathname to a Restricted Directory Low3.7EPSS 0.3%CVE Database V5CVE-2026-114370 CVE-2026-114370 is a low-severity vulnerability in the PathResourceManager component of the Undertow web server used in Red Hat build of Apache Camel for Spring Boot 4. The flaw arises from improper pathname validation when handling symbolic links, allowing an attacker to read files from sibling directories if their names share a prefix with an authorized safe directory. Exploitation requires specific symbolic link configurations and directory naming patterns. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| High | 7.4 | EPSS 1.0% | CVE-2026-79986camel-core · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in High7.4EPSS 1.0%GCVE DatabaseCVE-2026-79986 CVE-2026-79986 is a path traversal vulnerability in the Apache Camel Azure Files component and other remote-file consumers. It allows an attacker controlling the remote server or on-path to craft directory listing entries that cause Camel to access files outside the configured polling directory. This can lead to unauthorized reading, deletion, or renaming of files on the remote server using the endpoint's credentials. The flaw arises from improper normalization and containment checks on concatenated remote file paths. The issue affects Apache Camel versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1. Fixed versions are 4.18.5, 4.22.1, and 4.23.0. | GCVE Database | ||
| Medium | 5.3 | EPSS 0.5% | Medium5.3EPSS 0.5%CVE Database V5CVE-2026-85315 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it. Upgrade 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, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description. | CVE Database V5 | ||
| High | 7.5 | EPSS 0.7% | CVE-2026-85251Apache Camel · Information Exposure High7.5EPSS 0.7%CVE Database V5CVE-2026-85251 Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. Two paths handed credentials to a redirect target, which is a host chosen by the remote server rather than by the route, once followRedirects=true. OAuth2ClientConfigurer registers its interceptor with addRequestInterceptorFirst, and HttpClient runs protocol-level request interceptors inside ProtocolExec, which sits below RedirectExec in the exec chain; the interceptor therefore ran again for every redirect hop and re-attached Authorization: Bearer to whatever host the Location header named. Separately, credentials were registered against an AuthScope matching any host, so basic and digest credentials were presented to a redirect target as well. A remote endpoint - or anyone who can influence its responses - could therefore collect the bearer token or the configured credentials simply by answering with a redirect to a host it controls. Upgrade 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. Credentials are now sent only to the authority the endpoint was configured with, and are not re-attached when a redirect crosses to another host. For deployments that cannot upgrade immediately, set followRedirects=false on endpoints that carry credentials, and handle any redirect explicitly in the route so that the destination is chosen by the route rather than by the remote server. | CVE Database V5 | ||
| High | 7.4 | EPSS 0.7% | CVE-2026-79985Apache Camel · Path Traversal High7.4EPSS 0.7%CVE Database V5CVE-2026-79985 CVE-2026-79985 is a path traversal vulnerability in the Apache Camel SMB component affecting versions from 4.2.0 before 4.18.5 and from 4.19.0 before 4.22.1. The flaw allows an attacker controlling the remote server or an on-path attacker to manipulate directory listings to cause Apache Camel to access files outside the intended polling directory. This can lead to unauthorized file retrieval, deletion, or renaming using the endpoint's credentials. The vulnerability arises because Apache Camel does not properly normalize or validate remote file paths before performing operations. The issue is fixed in Apache Camel versions 4.18.5 and 4.22.1. | CVE Database V5 | ||
| High | 7.4 | EPSS 0.7% | CVE-2026-79984Apache Camel · Path Traversal High7.4EPSS 0.7%CVE Database V5CVE-2026-79984 CVE-2026-79984 is a path traversal vulnerability in the Apache Camel Mina SFTP component affecting versions from 4.18.0 before 4.18.5 and from 4.19.0 before 4.22.1. The vulnerability arises because the component concatenates directory paths with file names from the remote server without proper normalization or containment checks, allowing an attacker to access files outside the intended directory. This can lead to unauthorized reading, deletion, or renaming of files on the remote server. The issue is fixed in Apache Camel versions 4.18.5 and 4.22.1. | CVE Database V5 | ||
| High | 7.4 | EPSS 1.0% | CVE-2026-79983Apache Camel · Path Traversal High7.4EPSS 1.0%CVE Database V5CVE-2026-79983 CVE-2026-79983 is a path traversal vulnerability in the Apache Camel FTP component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1. The vulnerability allows an attacker controlling the FTP server or an on-path attacker to craft directory listings with file names that escape the configured polling directory. This leads to unauthorized read, delete, or rename operations on files outside the intended directory using the endpoint's credentials. The issue affects ftp, ftps, and sftp schemes. The vulnerability is fixed in Apache Camel versions 4.18.5 and 4.22.1. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.5% | CVE-2026-63621Apache Camel · Improper Input Validation Medium5.3EPSS 0.5%CVE Database V5CVE-2026-63621 CVE-2026-63621 is an improper input validation vulnerability in the Apache Camel Knative component. It allows unauthenticated attackers to inject internal Camel headers via structured-mode CloudEvent requests, potentially enabling server-side request forgery, path traversal, or message dispatch redirection. This issue affects multiple Apache Camel versions and is fixed in later releases. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.4% | CVE-2026-19879Red Hat build of Apache Camel for Spring Boot 4 · Incorrect Conversion Between Numeric Types Medium5.3EPSS 0.4%CVE Database V5CVE-2026-19879 CVE-2026-19879 is a moderate severity vulnerability in the Undertow HTTP server used by Red Hat build of Apache Camel for Spring Boot 4. It involves a silent narrowing cast from 16-bit Unicode characters to 8-bit bytes in the HTTP response header writing path. This can cause truncation of certain Unicode characters into ASCII control characters or special symbols, potentially leading to limited integrity impact or information disclosure if user input is not properly sanitized before being placed in response headers. EPSS 0.4%Vulnerability | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.6% | Medium5.3EPSS 0.6%CVE Database V5CVE-2026-56139 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Undertow Component. The camel-undertow HTTP server consumer exposes a muteException option that controls what is returned to the client when a route processing error occurs. This option defaulted to false, whereas the other Camel HTTP server components (camel-http / camel-jetty / camel-servlet and camel-platform-http) default it to true. With muteException=false, when a request triggers an exception during route processing the consumer writes the full Throwable stack trace into the HTTP response body as text/plain instead of returning an empty body. Any unauthenticated client that can reach the endpoint and cause a processing error - for example by sending a malformed request body, an invalid parameter, or otherwise triggering a route-internal failure - therefore receives a complete Java stack trace. Such a stack trace can disclose sensitive internal information, including credentials embedded in exception messages, internal host names and IP addresses, filesystem paths, dependency and version details, database and class names, and the application's internal structure, which an attacker can use to plan further attacks. In addition, for Rest DSL consumers the muteException option was not honoured at all: the RestUndertowHttpBinding was created with a hard-coded false, so the stack trace was returned even when muteException=true had been configured. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-undertow consumer (for example undertow: http://0.0.0.0:8080/api?muteException=true , or globally via the camel.component.undertow.mute-exception=true property), so that processing errors no longer return the stack trace to the client; note that on affected releases this workaround does not cover Rest DSL consumers, whose binding ignores the option until the fix is applied. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.6% | Medium5.3EPSS 0.6%CVE Database V5CVE-2026-49365 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Netty HTTP component. The camel-netty-http HTTP server consumer exposes a muteException option that controls what is returned to the client when a route processing error occurs. This option defaulted to false because the backing field was an uninitialised primitive boolean (Java's default of false), whereas the other Camel HTTP server components (camel-http / camel-jetty / camel-servlet and camel-platform-http) default it to true. With muteException=false, when a request triggers an exception during route processing the consumer writes the full Throwable stack trace into the HTTP response body as text/plain (via DefaultNettyHttpBinding) instead of returning an empty body. Any unauthenticated client that can reach the endpoint and cause a processing error - for example by sending a malformed request body, an invalid parameter, or otherwise triggering a route-internal failure - therefore receives a complete Java stack trace. Such a stack trace can disclose sensitive internal information, including credentials embedded in exception messages, internal host names and IP addresses, filesystem paths, dependency and version details, database and class names, and the application's internal structure, which an attacker can use to plan further attacks. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-netty-http consumer (for example netty-http: http://0.0.0.0:8080/api?muteException=true , or globally via the camel.component.netty-http.configuration.mute-exception=true property), so that processing errors no longer return the stack trace to the client. | CVE Database V5 | ||
| High | 7.5 | EPSS 0.9% | CVE-2026-46726Apache Camel Vertx Websocket · Improper Input Validation High7.5EPSS 0.9%CVE Database V5CVE-2026-46726 Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Vertx Websocket component. The camel-vertx-websocket consumer mapped inbound WebSocket query and path parameters into the Camel Exchange header map without applying any HeaderFilterStrategy (VertxWebsocketConsumer.populateExchangeHeaders()). Because nothing blocked the Camel header namespace, a client connecting to the WebSocket endpoint could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as query parameters. In a route where the WebSocket consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values and sent to the attacker, disclosing environment variables, application properties and vault secrets. When the WebSocket endpoint is exposed without authentication, this is reachable by an unauthenticated remote attacker. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes the affected consumers apply a HeaderFilterStrategy that filters the Camel header namespace case-insensitively on inbound mapping, so externally-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from the inbound message before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), require authentication on the WebSocket endpoint, and avoid bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers. | CVE Database V5 | ||
| Low | 3.7 | EPSS 0.6% | CVE-2026-46584Apache Camel Mail · Improper Input Validation Low3.7EPSS 0.6%CVE Database V5CVE-2026-46584 Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel Mail Component. The camel-mail producer (MailProducer.getSender) scanned the outgoing Exchange for message headers in the mail.smtp. / mail.smtps. namespace and, when any were present, built a per-message JavaMail sender with those values applied as JavaMail session properties, overriding the endpoint configuration. This namespace is Camel-internal - only MailProducer interprets it - and was not blocked by any HeaderFilterStrategy, so the values could originate from any inbound protocol (for example platform-http query parameters or request headers, or JMS / Kafka messages from untrusted producers) that feeds a route ending in an smtp / smtps producer without an intervening removeHeaders. The maximal impact is version-dependent: on releases before 4.19.0, setting mail.smtp.host redirects the SMTP connection to a server under the attacker's control, and because the producer then authenticates with the endpoint's configured username and password those credentials are transmitted to the attacker; on 4.19.0 and later the producer connects to the endpoint's configured host explicitly, so the reachable impact is limited to weakening transport security (for example mail.smtp.ssl.trust, mail.smtp.starttls.enable or mail.smtp.socks.host) and interception of the outgoing message rather than host redirect. Exploitation requires a route that channels untrusted input into the mail producer without stripping the namespace. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, the per-message override is disabled by default; enable it only on trusted endpoints with useJavaMailSessionPropertiesFromHeaders=true. For deployments that cannot upgrade immediately, strip the namespace before the mail producer with removeHeaders('mail.smtp.*') and removeHeaders('mail.smtps.*') between any untrusted ingress and the smtp / smtps producer. Even with the opt-in enabled, route authors should still strip the namespace on any path that carries untrusted input. | CVE Database V5 | ||
| Critical | 9.8 | EPSS 1.1% | CVE-2026-53913Apache Camel Keycloak · Improper Authentication Critical9.8EPSS 1.1%CVE Database V5CVE-2026-53913 Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component. The KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. KeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes the policy and the request reaches the protected route, with no signature, issuer or expiry check and no request to Keycloak. The token is read from the inbound request header because allowTokenFromHeader defaults to true. Because the normal reason to place a route behind this policy is that the route performs server-side work, the bypass results in unauthenticated access to that work; where the protected route forwards to a code-execution-capable producer, it can result in unauthenticated remote code execution. This defect is independent of CVE-2026-23552: that issue concerned the issuer claim and was fixed by adding a check inside the verification routine, but here the verification routine is not reached at all in the default configuration, so the defect remains. This issue affects Apache Camel: from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, configure a non-empty requiredRoles or requiredPermissions on every KeycloakSecurityPolicy so that the token-verification path is exercised, set allowTokenFromHeader to false where the token is not expected from the request header, or perform token verification at the framework layer ahead of the policy. | CVE Database V5 | ||
| High | 8.2 | EPSS 0.9% | CVE-2026-40022Apache Camel Platform HTTP Main · Authentication Bypass Using an Alternate Path or Channel High8.2EPSS 0.9%CVE Database V5CVE-2026-40022 When authentication is enabled on the Apache Camel embedded HTTP server or embedded management server (camel-platform-http-main) and a non-root context path such as /api or /admin is configured via camel.server.path or camel.management.path, the BasicAuthenticationConfigurer and JWTAuthenticationConfigurer classes derive the authentication path from properties.getPath() when camel.server.authenticationPath / camel.management.authenticationPath is not explicitly set. Combined with the Vert.x sub-router mounting model - the sub-router is mounted at _path_* and the authentication handler is registered inside the sub-router at the resolved path - this causes the authentication handler to match only the exact configured context path, not its subpaths. Unauthenticated requests to subpaths such as /api/_route_ or /admin/observe/info therefore reach protected business routes and management endpoints without being challenged for credentials. The /observe/info endpoint can disclose runtime metadata such as the user, working directory, home directory, process ID, JVM and operating system information. This issue affects Apache Camel: from 4.14.1 before 4.14.6, from 4.18.0 before 4.18.2. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, they are suggested to upgrade to 4.14.6. If users are on the 4.18.x LTS releases stream, they are suggested to upgrade to 4.18.2. | CVE Database V5 | ||
| High | 7.0 | EPSS 0.3% | CVE-2024-2700Red Hat Security Advisory: HawtIO 4.1.0 for Red Hat build of Apache Camel 4 Release and security update High7.0EPSS 0.3%GCVE DatabaseCVE-2024-2700 HawtIO 4.1.0 for Red Hat build of Apache Camel 4 GA Release is now available. The purpose of this text-only errata is to inform you about the enhancements that improve your developer experience and ensure the security and stability of your products. * serve-static: Improper Sanitization in serve-static (CVE-2024-43800) * send: Code Execution Vulnerability in Send Library (CVE-2024-43799) * org.springframework/spring-webmvc: Path Traversal Vulnerability in Spring Applications Using RouterFunctions and FileSystemResource (CVE-2024-38816) * org.eclipse.jetty/jetty-server: Jetty ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks (CVE-2024-8184) * quarkus-core: Leak of local configuration properties into Quarkus applications (CVE-2024-2700) * braces: fails to limit the number of characters it can handle (CVE-2024-4068) * undertow: Improper State Management in Proxy Protocol parsing causes information leakage (CVE-2024-7885) * path-to-regexp: Backtracking regular expressions cause ReDoS (CVE-2024-45296) * express: Improper Input Handling in Express Redirects (CVE-2024-43796) | GCVE Database |
Page 1 of 1