Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF 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 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.
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, 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.
Improper Handling of Case Sensitivity vulnerability in Apache Camel Platform HTTP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The guard that prevents a request header being reflected into the response compared header names case sensitively, while HTTP header names are case insensitive. A caller could therefore defeat the suppression simply by varying the case of the header name. HTTP/2 makes the problem unconditional rather than optional: the protocol requires header names to be lowercase on the wire, so the comparison never matched and the suppression was inert for every request on an HTTP/2 connection. The consequence is that content the caller chose is echoed back in the response, which is the basis for response-splitting and cache-poisoning style attacks against whatever sits in front of the Camel endpoint.
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. Request header names are now compared case insensitively, so the suppression holds regardless of casing and works under HTTP/2. For deployments that cannot upgrade immediately, strip the headers in question in front of the Camel endpoint, or remove them from the response in the route rather than relying on the built-in suppression.
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.
Improper Input Validation vulnerability in Apache Camel Tika component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The Tika producer mapped every metadata key parsed out of the submitted document onto the Exchange as a header, with no filter applied. Document metadata is attacker-controlled content: the party that supplies the file chooses the metadata keys it carries. A crafted document could therefore set Exchange headers that the rest of the route depends on, including headers in the Camel namespace such as CamelFileName, which downstream components use to decide where content is written. The pattern is the same header-injection class as the consumer advisories published previously, reached here through parsed file content rather than through a protocol header.
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. Parsed document metadata is now filtered through a HeaderFilterStrategy before it is mapped onto the Exchange. A route that was reading a metadata-derived header the filter now blocks will see it missing. For deployments that cannot upgrade immediately, strip the Camel namespace after the Tika producer with removeHeaders("Camel*") before any component that acts on those headers.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Camel PQC component.
This issue affects Apache Camel: from 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1.
The producer held a single java.security.Signature instance and used it for every exchange without synchronizing access. Signature is stateful and is not thread safe: update() accumulates the data to be signed or verified, and verify() consumes that accumulated state. With concurrent exchanges sharing one instance the update and verify calls of different messages interleave, so a verification can complete against data that belongs to another exchange, or against a partially accumulated buffer. The outcome is non-deterministic and includes a verification reporting success for a message whose signature was never actually checked, which defeats the guarantee the component exists to provide. Reaching it requires concurrent traffic through the same endpoint, which is the ordinary condition for a Camel route under load.
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. The Signature instance is no longer shared across concurrent exchanges. For deployments that cannot upgrade immediately, restrict the affected route to a single concurrent consumer so that no two exchanges use the instance at once.
CVE-2026-85245 is a vulnerability in Apache Camel's Thrift component where unmarshalling incoming data uses a shared instance, causing data from one message to be exposed to others. This affects Apache Camel versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1. The flaw allows data from one tenant or user to be visible to another when served through the same route. The issue is fixed in Apache Camel 4.23.0, 4.18.5, and 4.22.1. Users unable to upgrade immediately should copy the unmarshalled body to a new instance to avoid data leakage.
Improper Authentication vulnerability in Apache Camel OAuth component.
This issue affects Apache Camel: from 4.11.0 before 4.18.5, from 4.19.0 before 4.22.1.
The camel-oauth processors that guard a route did not stop the exchange when authentication could not be completed. Where a failure to establish an authenticated session should have terminated routing and returned an error to the caller, the processors fell through and returned control to the route, so the request continued to the protected endpoint as though authentication had succeeded. The effect is a fail-open authentication guard: an unauthenticated caller reached whatever the route did next. The condition is reached on the ordinary request path of a route configured to require OAuth, and needs no special configuration or prior access on the caller's part.
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. The processors now stop the exchange and set the appropriate error status whenever an authenticated session cannot be established, so a failed authentication no longer reaches the protected part of the route. For deployments that cannot upgrade immediately, place an explicit authorization check after the OAuth processor rather than relying on it to halt the exchange, and verify that the route stops on failure.
CVE-2026-78165 is a deserialization of untrusted data vulnerability in the Apache Camel Spring Redis component affecting versions from 2.11.0 before 4.18.5 and from 4.19.0 before 4.22.1. The vulnerability arises because the component uses a default Java serialization mechanism without applying any object input filtering, allowing arbitrary serialized objects to be deserialized and their readObject methods executed. This occurs before any route logic can inspect the message, exposing the system to potential remote code execution if an attacker can publish messages to subscribed Redis channels. The issue is fixed in Apache Camel versions 4.18.5, 4.22.1, and later 4.23.0. Mitigations include upgrading to fixed versions, setting JVM-wide serialization filters, configuring non-Java serializers, and restricting Redis access.
The BDM Digital Payment Gateway WordPress plugin through 1.3.12 does not verify the credentials on its public payment-status update route and treats unset credentials as valid, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without payment in the default configuration.
A cross-site request forgery (CSRF) vulnerability in Gitea versions up to 28.1.0 allows a repository administrator to have the topics of their repository changed by visiting a malicious page. The affected endpoint lacks proper sign-in middleware, enabling unauthorized cross-origin requests. No other repository settings are affected through this route.
A vulnerability in the Linux kernel's IPv6 routing code allowed a reference cycle to form between fib6_info structures and exception routes during route removal, causing resource leaks and stalling network device unregistration. This was due to improper handling of exception insertion for dying fib6_info objects. The issue has been resolved by adding a check to prevent new exceptions from being inserted during fib6_info destruction.
A vulnerability in the Linux kernel's ovpn module related to clearing stale local source addresses in UDP output fallback has been resolved. The issue involved modifying a bind structure that is read locklessly by concurrent transmissions, which could cause torn IPv6 addresses to be observed. The fix involves retrying route lookups without modifying the bind, revalidating under lock, resetting caches, and publishing a replacement bind with a wildcard address. This prevents inconsistent state and cache invalidation issues.
A vulnerability in the Linux kernel IPv6 implementation caused a memory leak of destination cache (dst) structures for uncached routes when devices are unregistered. This was due to a race condition in handling the uncached route list, leading to improper reference counting and resource leaks. The issue affects Linux kernel version 6.11 and has been fixed in subsequent commits.
A vulnerability in the Linux kernel's MCTP socket handling allows sockets within the same network namespace to misuse preallocated tags belonging to other sockets. The flaw occurs because the function mctp_lookup_prealloc_tag() iterates over a namespace-wide tag list instead of the socket's own tag list, enabling tag consumption across sockets improperly. This issue has been fixed by restricting tag matching to the socket's own tag list.
The Vitepos – Point of Sale (POS) for WooCommerce plugin for WordPress contains a SQL Injection vulnerability in the 'src_by' parameter affecting all versions up to and including 3.5.1. This vulnerability allows unauthenticated attackers or authenticated users with any POS role to inject malicious SQL commands via the /vitepos/v1/vendor/list REST route, potentially exposing sensitive database information. The vulnerability arises from insufficient escaping and lack of proper query preparation. The CVSS 3.1 score is 7.5 (high severity), indicating a network exploitable flaw with no privileges or user interaction required and high confidentiality impact. No patch information is provided, and no known exploits are reported in the wild.
The Apache Airflow Keycloak auth manager did not end the session on logout: the logout route revoked the presented token, but `KeycloakJWTMiddleware` then issued a new, unrevoked token on the same response, so the user stayed logged in. Deployments using the Keycloak auth manager are affected: after a user logs out, anyone with later access to the same browser (for example on a shared workstation) can continue to act as that user.
Users of apache-airflow-providers-keycloak are recommended to upgrade to apache-airflow-providers-keycloak 0.11.1 or later.