# CVE-2026-84176: Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via Wildcard Origin Reflection > Attackers can read sensitive data from Apache Camel endpoints via credentialed cross-origin requests due to improper CORS configuration. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 19 Oct 2026 - **Updated:** 19 Oct 2026 - **Also known as:** GHSA-vxj7-chgp-72vh ## What is CVE-2026-84176? CVE-2026-84176 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. createCorsHandler() 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. Upgrade 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. Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains) ## Which versions are affected by CVE-2026-84176? ## How do I fix CVE-2026-84176? No fix has been published for CVE-2026-84176 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-84176 being exploited? There is no known exploitation of CVE-2026-84176 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-84176 (Apache Camel camel-platform-http-vertx): CORS handler sends Access-Control-Allow-Credentials: true outside the origin check and reflects the Origin when no origins are configured (credentialed any-origin) — Camel Spring Boot (github_poc): https://github.com/oscerd/CVE-2026-84176 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-84176 and fix it if it is affected. What it is: CVE-2026-84176 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-84176 in the wild and no public exploit code. Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-84176/ (Markdown: https://insights.sbomify.com/CVE-2026-84176/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84176 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84176 - OSV: https://osv.dev/vulnerability/CVE-2026-84176 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-84176/ Summaries are generated and may contain mistakes; the official description above is the record.