Skip to content
VulniPulse
Sign in
Advisory severityMedium6.5Red Hat Linux

Medium [CVE-2026-49098] Message redirection and injection via header manipulation

This medium-severity Red Hat Linux advisory covers CVE-2026-49098 affecting Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Apache Camel for Spring Boot 4.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-49098 Source published Source updated

VulniPulse record published Record updated

CVE-2026-49098
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Kafka Component.

The camel-kafka producer can override its configured target topic at runtime from the kafka.OVERRIDE_TOPIC Exchange header: KafkaProducer.evaluateTopic() returns the header value in preference to the topic configured on the endpoint.

The control-header constants in KafkaConstants (for example OVERRIDE_TOPIC = kafka.OVERRIDE_TOPIC, OVERRIDE_TIMESTAMP = kafka.OVERRIDE_TIMESTAMP, PARTITION_KEY = kafka.PARTITION_KEY) used plain, non-Camel-prefixed values. camel-kafka's own KafkaHeaderFilterStrategy does filter the kafka.* namespace, but only on the Kafka-to-Exchange serialization boundary (reading Kafka record headers into the Exchange, and writing Exchange headers into a Kafka record); it does not apply to headers that arrive from an upstream consumer in a multi-component route.

The upstream HTTP consumer uses HttpHeaderFilterStrategy, which blocks only the Camel / camel namespace, so a kafka.* header passes through unfiltered.

Affected products named by the advisory: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4.

Is CVE-2026-49098 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-49098 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-49098?

Upgrade to a fixed release named by Red Hat:

  • 4.21.0
  • 4.14
  • 4.14.8
  • 4.18
  • 4.18.3

Confirm against the vendor advisory before you patch.

Affected versions
  • < 4.0.0
  • < 4.14.8
  • < 4.15.0
  • < 4.18.3
  • < 4.19.0
  • < 4.21.0

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Fixed versions
  • 4.21.0
  • 4.14
  • 4.14.8
  • 4.18
  • 4.18.3

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Strip the kafka.* headers from untrusted inbound messages before the Kafka producer (for example removeHeaders('kafka.*') at the start of the route), and set the target topic from a trusted source.

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.