oscerd opened a new pull request, #26890: URL: https://github.com/apache/camel/pull/26890
## Summary Adds a `HeaderFilterStrategy` to the `camel-hivemq` component, aligning it with the hardening applied to other Camel consumers in the CVE-2025-27636 family. ### Problem `HiveMQConsumer.onMessage()` was mapping the inbound MQTT publish topic name, QoS and retained flag directly to Exchange headers with no `HeaderFilterStrategy` in place. This means any `Camel*` header injected upstream survived onto the Exchange, bypassing the `DefaultHeaderFilterStrategy` that other consumers apply to block the internal-dispatch namespace. Additionally, if the Exchange flowed to a `camel-hivemq` producer (e.g. as a bridge), the `CamelHiveMQOverrideTopic` header — if injected — would drive where the message was re-published. ### Changes - `HiveMQEndpoint`: implements `HeaderFilterStrategyAware`, delegates to `HiveMQConfiguration` - `HiveMQConfiguration`: adds `headerFilterStrategy` field defaulting to `DefaultHeaderFilterStrategy`, with getter/setter and `@UriParam` - `HiveMQConsumer`: applies `strategy.applyFilterToExternalHeaders()` before each `setHeader()` call, following the same pattern as other fixed consumers (e.g. `camel-nats`) - Generated sources regenerated ### Testing Existing unit tests pass. The fix follows the established pattern; no new integration test is added since the behaviour is covered by the filter contract of `DefaultHeaderFilterStrategy` itself. Fixes https://issues.apache.org/jira/browse/CAMEL-24998 Generated by Bob via OSS Helper on behalf of Andrea Cosentino -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
