CVE-2026-56139 is an information-disclosure vulnerability in the Apache Camel Undertow HTTP server consumer. In affected releases, the consumer's muteException option defaulted to false, causing route-processing exceptions to be serialized as complete Java Throwable stack traces in HTTP error response bodies. Other Camel HTTP server components default this option to true. Additionally, Rest DSL consumers instantiated RestUndertowHttpBinding with muteException hard-coded to false, causing stack traces to be exposed even where muteException=true was configured. The issue affects Apache Camel versions 4.0.0 through 4.14.7, 4.15.0 through 4.18.2, and 4.19.0 through 4.20.x.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a self-contained Java/Spring Boot proof-of-concept reproducer for CVE-2026-56139, an information-disclosure flaw in Apache Camel's camel-undertow Rest DSL consumer. The project contains 10 files, with core logic in four Java classes under src/main/java/com/example. Application.java is the Spring Boot entry point. RestRoutes.java defines two Camel routes: a vulnerable undertow Rest DSL endpoint on port 8888 at /api/orders and a plain undertow endpoint on port 8889 at /plain/orders. Both routes invoke FailingProcessor.java, which deliberately throws an IllegalStateException containing sensitive-looking internal details (JDBC URL, internal hostname, service account hint, vault secret hint, backend IP) to simulate realistic leakage. ExploitController.java exposes /exploit/attack on port 8080 and acts as the attacker driver: it sends GET requests to both local endpoints, captures their HTTP 500 responses, and reports that the Rest DSL route leaks the full stack trace while the plain undertow route returns an empty body when muteException=true is honored. The repository also includes application.properties configuring server.port=8080 and camel.component.undertow.mute-exception=true, plus Dockerfile and docker-compose.yml for containerized reproduction. pom.xml pins camel-undertow-starter to vulnerable version 4.18.2. This is a real exploit/reproducer rather than a mere detector: it actively triggers the vulnerable behavior and demonstrates the resulting disclosure to an unauthenticated client. The exploit capability is limited to information exposure (CWE-209), not code execution. It is operational because it includes a working trigger path and hardcoded demonstration payload/data, but it is not weaponized or framework-based.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability identified as CVE-2026-56139 affecting Apache Camel Undertow, specifically described as an Apache Camel Undertow REST DSL vulnerability.
A sensitive-information disclosure vulnerability in Apache Camel's Undertow component. Unauthenticated remote clients able to reach an affected endpoint and trigger a route-processing error can receive full Java stack traces, potentially exposing credentials in error messages, internal hostnames and IP addresses, filesystem paths, dependency/version details, database and class names, and application structure.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.