{"id":"CVE-2026-84176","aliases":[],"summary":"Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via Wildcard Origin Reflection","published_at":"2026-10-19T10:30:00.854Z","modified_at":"2026-11-04T10:52:32Z","products":[],"rating":{"severity":"medium","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","attack_path":"internet_unauthenticated","user_interaction":true,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.005770000163465738,"percentile":0.4835900068283081,"date":"2026-11-19T00:00:00Z"},"priority":8,"details":"Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\n\n\n\ncreateCorsHandler() set Access-Control-Allow-Credentials: true outside the origin check, so the header went out on every response to a request carrying an Origin header, including responses to origins the handler had just decided not to allow. When camel.server.cors.origins is unset, the handler treats every origin as allowed and echoes the caller's own Origin back as Access-Control-Allow-Origin. Together those produce the credentialed any-origin configuration that the fetch specification refuses to express as a literal wildcard, which is precisely why reflecting the origin is the usual way around that rule. A page on any origin could therefore make credentialed cross-origin requests to the Camel endpoint and read the responses.\n\nUpgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Access-Control-Allow-Credentials is now sent only when the request origin matched an origin the operator actually configured. With no origin list the origin is still reflected, as before, but credentials are not granted, and Vary: Origin is now set whenever the origin is reflected so that a shared cache cannot serve one origin's response to another. For deployments that cannot upgrade immediately, set camel.server.cors.origins to the explicit list of origins that need access rather than leaving it unset.","affected_stack":[],"affected_other":[{"ecosystem":"CVE","package":"Apache Software Foundation/Apache Camel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.18.5"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.22.1"}]}],"fixed":["4.18.5","4.22.1"],"provider":"cvelistv5","source":"CVE-2026-84176","relation":"self"},{"ecosystem":"NVD","package":"apache:camel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.18.5"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.22.1"}]}],"fixed":["4.18.5","4.22.1"],"provider":"nvd","source":"CVE-2026-84176","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Serverless","cpe":"cpe:/a:redhat:serverless:1","status":"affected","packages":["openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9","openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9"],"package_count":8,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat Fuse 7","cpe":"cpe:/a:redhat:jboss_fuse:7","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Out of support scope","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat build of Apache Camel 4 for Quarkus 3","cpe":"cpe:/a:redhat:camel_quarkus:3","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat build of Apache Camel for Spring Boot 4","cpe":"cpe:/a:redhat:camel_spring_boot:4","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4006","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4006","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-10-15T22:00:00Z","modified_at":"2026-11-10T23:00:00Z","summary":"Apache Camel: Mehrere Schwachstellen","details":"Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.\n\nApache Camel ist ein Integrations-Framework, das Enterprise Integration Patterns implementiert.","severity":[{"type":"BSI","score":"hoch","source":"WID-SEC-W-2026-4006"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4006.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4006"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-78162.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-78163.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-78164.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-78165.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-79983.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-79984.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-79985.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-79986.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-80312.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-80343.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-80344.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-83531.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-84176.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-84178.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-84180.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-84181.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85243.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85245.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85246.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85247.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85248.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85249.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85250.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85251.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85254.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85257.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85260.html"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-85296.html"}]},{"provider":"cvelistv5","source_id":"CVE-2026-84176","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-84176","license":"CC-BY-4.0","published_at":"2026-10-19T10:30:00.854Z","modified_at":"2026-10-19T18:42:24.974Z","summary":"Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via Wildcard Origin Reflection","details":"Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\n\n\n\ncreateCorsHandler() set Access-Control-Allow-Credentials: true outside the origin check, so the header went out on every response to a request carrying an Origin header, including responses to origins the handler had just decided not to allow. When camel.server.cors.origins is unset, the handler treats every origin as allowed and echoes the caller's own Origin back as Access-Control-Allow-Origin. Together those produce the credentialed any-origin configuration that the fetch specification refuses to express as a literal wildcard, which is precisely why reflecting the origin is the usual way around that rule. A page on any origin could therefore make credentialed cross-origin requests to the Camel endpoint and read the responses.\n\nUpgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Access-Control-Allow-Credentials is now sent only when the request origin matched an origin the operator actually configured. With no origin list the origin is still reflected, as before, but credentials are not granted, and Vary: Origin is now set whenever the origin is reflected so that a shared cache cannot serve one origin's response to another. For deployments that cannot upgrade immediately, set camel.server.cors.origins to the explicit list of origins that need access rather than leaving it unset.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","source":"CVE-2026-84176"}],"affected":[{"ecosystem":"CVE","package":"Apache Software Foundation/Apache Camel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.18.5"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.22.1"}]}],"fixed":["4.18.5","4.22.1"],"provider":"cvelistv5","source":"CVE-2026-84176","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://camel.apache.org/security/CVE-2026-84176.html"},{"type":"WEB","url":"https://issues.apache.org/jira/browse/CAMEL-24436"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25820"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25937"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25938"}]},{"provider":"nvd","source_id":"CVE-2026-84176","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84176","severity":[],"affected":[{"ecosystem":"NVD","package":"apache:camel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.18.5"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.22.1"}]}],"fixed":["4.18.5","4.22.1"],"provider":"nvd","source":"CVE-2026-84176","relation":"self"}],"product_status":[],"references":[]},{"provider":"redhat-vex","source_id":"CVE-2026-84176","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-84176","license":"CC-BY-4.0","published_at":"2026-10-19T10:30:00.854Z","modified_at":"2026-11-04T10:52:32Z","summary":"org.apache.camel/camel-platform-http-vertx: camel-platform-http-vertx: Information disclosure via overly permissive CORS configuration","details":"A flaw was found in the Apache Camel Platform HTTP Vertx component. Due to an overly permissive Cross-Origin Resource Sharing (CORS) configuration, the server reflects incoming request origins while enabling credential access. A remote attacker could exploit this flaw by enticing an authenticated user to visit a malicious website, allowing the attacker to conduct unauthorized cross-origin requests and access sensitive response data.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","source":"CVE-2026-84176"},{"type":"Red Hat","score":"Moderate","source":"CVE-2026-84176"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"OpenShift Serverless","cpe":"cpe:/a:redhat:serverless:1","status":"affected","packages":["openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9","openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9","openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9"],"package_count":8,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat Fuse 7","cpe":"cpe:/a:redhat:jboss_fuse:7","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Out of support scope","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat build of Apache Camel 4 for Quarkus 3","cpe":"cpe:/a:redhat:camel_quarkus:3","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"},{"vendor":"Red Hat","product":"Red Hat build of Apache Camel for Spring Boot 4","cpe":"cpe:/a:redhat:camel_spring_boot:4","status":"affected","packages":["camel-platform-http-vertx"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-84176"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-84176.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-84176"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2555499"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-84176"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84176"},{"type":"WEB","url":"https://camel.apache.org/security/CVE-2026-84176.html"},{"type":"WEB","url":"https://github.com/apache/camel/pull/25820"},{"type":"WEB","url":"https://github.com/apache/camel/pull/25937"},{"type":"WEB","url":"https://github.com/apache/camel/pull/25938"},{"type":"WEB","url":"https://issues.apache.org/jira/browse/CAMEL-24436"}]}],"references":[{"type":"ADVISORY","url":"https://camel.apache.org/security/CVE-2026-84176.html"},{"type":"WEB","url":"https://issues.apache.org/jira/browse/CAMEL-24436"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25820"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25937"},{"type":"FIX","url":"https://github.com/apache/camel/pull/25938"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-84176.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-84176"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2555499"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-84176"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84176"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4006","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4006","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-10T23:00:00Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-84176","url":"https://www.cve.org/CVERecord?id=CVE-2026-84176","license":"CC-BY-4.0","modified_at":"2026-10-19T18:42:24.974Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2026-84176","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84176","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-84176","url":"https://access.redhat.com/security/cve/CVE-2026-84176","license":"CC-BY-4.0","modified_at":"2026-11-04T10:52:32Z","relation":"self"}]}
