CVE-2026-49365

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 10, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-49365: Apache Camel: Camel-Netty-HTTP: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients

http://www.openwall.com/lists/oss-security/2026/07/05/25
generic

Apache Camel Security Advisory - CVE-2026-49365 - Apache Camel

https://camel.apache.org/security/CVE-2026-49365.html

Vendor Advisories for CVE-2026-49365(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-netty-http4.19.0, 4.20.04.21.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:02 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 13:41 UTCEG score recompute
  7. 2026-09-12 13:39 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 23:14 UTCEG score recompute
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 08:27 UTCEG score recompute
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 22:00 UTCEG score recompute
  23. 2026-08-27 22:00 UTCGHSA enrichment
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-26 13:56 UTCEG score recompute
  2. 2026-08-26 13:56 UTCGHSA enrichment
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 04:53 UTCEG score recompute
  5. 2026-08-25 04:53 UTCGHSA enrichment
  6. 2026-08-24 04:52 UTCGHSA enrichment
  7. 2026-08-23 04:50 UTCEG score recompute
  8. 2026-08-23 04:50 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 04:49 UTCEG score recompute
  11. 2026-08-22 04:49 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 04:19 UTCEG score recompute
  14. 2026-08-21 04:19 UTCGHSA enrichment
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 02:34 UTCEG score recompute
  17. 2026-08-20 02:34 UTCGHSA enrichment
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 22:53 UTCEG score recompute
  20. 2026-08-18 22:53 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 22:42 UTCEG score recompute
  23. 2026-08-17 22:42 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 18:03 UTCEG score recompute
  26. 2026-08-16 18:03 UTCGHSA enrichment
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 17:28 UTCEG score recompute
  30. 2026-08-15 17:28 UTCGHSA enrichment
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 17:26 UTCEG score recompute
  33. 2026-08-14 17:26 UTCGHSA enrichment
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-13 17:11 UTCGHSA enrichment
  36. 2026-08-12 16:58 UTCEG score recompute
  37. 2026-08-12 16:58 UTCGHSA enrichment
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-11 16:57 UTCEG score recompute
  40. 2026-08-11 16:57 UTCGHSA enrichment
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-10 16:56 UTCGHSA enrichment
  43. 2026-08-09 16:05 UTCEG score recompute
  44. 2026-08-09 16:05 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 16:04 UTCEG score recompute
  48. 2026-08-08 16:04 UTCGHSA enrichment
  49. 2026-08-07 16:02 UTCGHSA enrichment
  50. 2026-08-06 16:01 UTCEG score recompute
  51. 2026-08-06 16:01 UTCGHSA enrichment
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-05 16:00 UTCEG score recompute
  55. 2026-08-05 16:00 UTCGHSA enrichment
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 13:48 UTCEG score recompute
  58. 2026-08-04 13:48 UTCGHSA enrichment
  59. 2026-08-04 10:39 UTCEPSS rescore
  60. 2026-08-03 13:23 UTCEG score recompute
  61. 2026-08-03 13:23 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 13:15 UTCEG score recompute
  64. 2026-08-02 13:15 UTCGHSA enrichment
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 13:14 UTCEG score recompute
  67. 2026-08-01 13:14 UTCGHSA enrichment
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-31 13:13 UTCEG score recompute
  70. 2026-07-31 13:13 UTCGHSA enrichment
  71. 2026-07-30 16:28 UTCEPSS rescore
  72. 2026-07-30 13:12 UTCEG score recompute
  73. 2026-07-30 13:12 UTCGHSA enrichment
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 13:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49365?
CVE-2026-49365 is a medium vulnerability published on July 6, 2026. 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…
When was CVE-2026-49365 disclosed?
CVE-2026-49365 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49365 actively exploited?
CVE-2026-49365 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.9% of all scored CVEs.
What is the CVSS score of CVE-2026-49365?
CVE-2026-49365 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49365?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49365, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49365

Explore →

Is Your Infrastructure Affected by CVE-2026-49365?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs