{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-netty-http. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49365 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-netty-http to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0.","what":"CVE-2026-49365 is a medium-severity vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49365 and fix it if it is affected.\n\nWhat it is: CVE-2026-49365 is a medium-severity vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49365 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-netty-http (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-netty-http (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-netty-http (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-netty-http (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-netty-http (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-netty-http (Maven): affected from 4.19.0; fixed in 4.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-49365/ (Markdown: https://insights.sbomify.com/CVE-2026-49365/index.md)","id":"CVE-2026-49365","markdown":"https://insights.sbomify.com/CVE-2026-49365/index.md","name":"CVE-2026-49365","record":{"aliases":["GHSA-42q5-xw42-xf9g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel library","requires_auth":"none","summary":"Unauthenticated attackers can obtain sensitive internal information, including stack traces and credentials, by triggering processing errors in Apache Camel Netty HTTP endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Netty HTTP component.\n\nThe 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.\nThis 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.\n\nUsers 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-07-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-21T09:55:57Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-49365","stars":0,"title":"PoC reproducer for CVE-2026-49365 (Apache Camel camel-netty-http / camel-undertow): muteException defaults to false, so an uncaught exception's full Java stack trace is returned to the HTTP client (CWE-209). Fixed in 4.14.8/4.18.3/4.21.0."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache 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","id":"CVE-2026-49365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"information_disclosure","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Command injection in IntelliJ IDEA","id":"CVE-2026-49366"},"packages":[{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":null,"source":"GHSA-42q5-xw42-xf9g"},{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":"pkg:maven/org.apache.camel/camel-netty-http","source":"GHSA-42q5-xw42-xf9g"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":null,"source":"GHSA-42q5-xw42-xf9g"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":"pkg:maven/org.apache.camel/camel-netty-http","source":"GHSA-42q5-xw42-xf9g"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":null,"source":"GHSA-42q5-xw42-xf9g"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-netty-http","purl":"pkg:maven/org.apache.camel/camel-netty-http","source":"GHSA-42q5-xw42-xf9g"}],"prev":{"headline":"Information disclosure in Apache ActiveMQ Artemis","id":"CVE-2026-49364"},"products":["Apache Camel"],"published":"2026-07-06","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["Apache Software Foundation"]},"summary":"Unauthenticated attackers can obtain sensitive internal information, including stack traces and credentials, by triggering processing errors in Apache Camel Netty HTTP endpoints.","url":"https://insights.sbomify.com/CVE-2026-49365/"}