Skip to content
VulniPulse
Sign in
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-56139] Information disclosure via error messages containing sensitive data

This medium-severity Red Hat Linux advisory covers CVE-2026-56139 affecting Red Hat build of Apache Camel for Spring Boot 4, Red Hat Single Sign-On 7.

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

CVE-2026-56139 Source published Source updated

VulniPulse record published Record updated

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

Summary

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.

Affected products named by the advisory: Red Hat build of Apache Camel for Spring Boot 4; Red Hat Single Sign-On 7.

Is CVE-2026-56139 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-56139 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-56139?

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
  • To mitigate this issue, configure the `camel-undertow` consumer to explicitly set `muteException=true`. This can be done by adding `?muteException=true` to the consumer URI (e.g., `undertow:http://0.0.0.0:8080/api?muteException=true`) or by setting the global property `camel.component.undertow.mute-exception=true`. This prevents Java stack traces from being returned in HTTP responses upon route processing errors. Note that this workaround may not apply to Rest DSL consumers in affected releases. A restart of the application or service hosting the Camel Undertow component may be required for the changes to take effect.

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.