---
id: CVE-2026-84176
title: >-
  Apache Camel: Camel-Platform-HTTP-Vertx Cross-Origin Credential Exposure via
  Wildcard Origin Reflection
summary: >-
  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-…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'
cvssSource: cna
cwe:
  - CWE-942
vendor: Apache Software Foundation
product: 'org.apache.camel:camel-platform-http-vertx'
affected:
  - 'org.apache.camel:camel-platform-http-vertx >= 4.0.0 < 4.18.5'
  - 'org.apache.camel:camel-platform-http-vertx >= 4.19.0 < 4.22.1'
published: '2026-10-19'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T10:30:00.854Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-84176'
references:
  - url: 'https://camel.apache.org/security/CVE-2026-84176.html'
    label: Apache Camel Security Advisory - CVE-2026-84176
  - url: 'https://issues.apache.org/jira/browse/CAMEL-24436'
    label: CAMEL-24436
  - url: 'https://github.com/apache/camel/pull/25820'
    label: >-
      Fix on main, released in 4.23.0 (commit
      4b557e4e82048515b0141f4e3594fbecf7dc741c)
  - url: 'https://github.com/apache/camel/pull/25937'
    label: >-
      Backport to camel-4.22.x, released in 4.22.1 (commit
      b0399b181d26cd8b136fa98b54ec8e5c283338da)
  - url: 'https://github.com/apache/camel/pull/25938'
    label: >-
      Backport to camel-4.18.x, released in 4.18.5 (commit
      e23332aec12f7ec3a841e52d1821e2a580c2fbc7)
tags:
  - cve.org
ingestedAt: '2026-10-19T12:27:23.818Z'
---

## Overview

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.

## Affected

- `org.apache.camel:camel-platform-http-vertx >= 4.0.0 < 4.18.5`
- `org.apache.camel:camel-platform-http-vertx >= 4.19.0 < 4.22.1`

## Remediation

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.

### Workarounds

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.