Skip to content
VulniPulse
High8.2Red Hat Linux

High [CVE-2026-46726] Server-Side Request Forgery and sensitive data exposure

This high-severity Red Hat Linux advisory covers CVE-2026-46726 affecting Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16, Red Hat Build of Apache Camel 4.18 for Quarkus 3.33, Red Hat build of Apache Camel 4 for Quarkus 3.

CVE-2026-46726 Published Jul 6, 2026Updated by vendor Jul 6, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

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 6 hours ago·verify at source

Fixed versions
  • 4.21.0
  • 4.14
  • 4.14.8
  • 4.18
  • 4.18.3
  • camel-vertx-websocket
  • RHSA-2026:54622
  • RHSA-2026:48118

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Restrict access to exposed WebSocket endpoints with authentication. If unable to upgrade, strip Camel-internal headers from inbound WebSocket messages before they reach downstream producers (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route).

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

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.