dbcve.org
CamelApplication · Apache

CVE-2026-49365

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 4.14.8 / 4.18.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Netty HTTP component. The camel-netty-http 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 because the backing field was an uninitialised primitive boolean (Java's default of 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 (via DefaultNettyHttpBinding) 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. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-netty-http consumer (for example netty-http: http://0.0.0.0:8080/api?muteException=true , or globally via the camel.component.netty-http.configuration.mute-exception=true property), so that processing errors no longer return the stack trace to the client.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The camel-netty-http HTTP server consumer exposes a muteException option that defaulted to false due to an uninitialized primitive boolean field. This caused full Java stack traces to be written into HTTP response bodies on processing errors instead of returning an empty body, exposing sensitive internal information including credentials, hostnames, IP addresses, filesystem paths, and application structure to unauthenticated clients.

MitigationUpgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams), or explicitly set muteException=true on the netty-http consumer endpoint or via camel.component.netty-http.configuration.mute-exception=true property.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.0.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache Camel version
    Inspect your project dependencies (pom.xml, build.gradle) or the Camel JAR manifest for the camel-core version. Run: grep -r 'camel-core' pom.xml or check the JAR file version in your deployment.
    Affected if The installed version falls within 4.0.0 to <4.14.8, 4.15.0 to <4.18.3, or 4.19.0 to <4.21.0.
  2. Identify netty-http consumer usage
    Search your Camel route definitions (Java, XML, YAML) for 'netty-http' in a from() clause. Example: from("netty-http:http://0.0.0.0:8080/path"). This vulnerability only affects HTTP server consumers, not producers.
    Affected if A netty-http endpoint is defined as a consumer (from()) exposing an HTTP server.
  3. Verify muteException configuration
    Inspect your route definitions and Camel configuration files for the muteException parameter on the netty-http endpoint. Also check for camel.component.netty-http.configuration.mute-exception in application.properties or application.yml.
    Affected if The muteException parameter is not explicitly set to 'true' on the netty-http consumer endpoint.
  4. Confirm endpoint is network-exposed
    Review the netty-http binding address. Look for host bindings like 0.0.0.0, or check your deployment configuration for exposed ports and network listeners.
    Affected if The netty-http consumer binds to a network-accessible address (not localhost-only).

You are affected if you run a vulnerable Apache Camel version with a netty-http HTTP server consumer that has muteException left at its default (unset), allowing unauthenticated HTTP clients to receive full stack traces on errors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.8 / 4.18.3 / 4.21.0 or later
Fixed in 4.14.84.18.34.21.0
Interim mitigation

Upgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams), or explicitly set muteException=true on the netty-http consumer endpoint or via camel.component.netty-http.configuration.mute-exception=true property.

Recommended fix High confidence

4.21.0 (or 4.18.3/4.14.8 depending on release stream)

  1. Upgrade Apache Camel to a fixed version: 4.21.0 for current releases, 4.18.3 for the 4.18.x stream, or 4.14.8 for the 4.14.x LTS stream
  2. If immediate upgrade is not possible, set muteException=true on the camel-netty-http consumer endpoint (e.g., netty-http:http://0.0.0.0:8080/api?muteException=true)
  3. Alternatively, configure globally by setting camel.component.netty-http.configuration.mute-exception=true in application.properties

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49365 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data