Skip to content
VulniPulse
Sign in
Medium 2 vendors · 2 advisories

CVE-2026-84176: Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component

CVE-2026-84176 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.5 (Apache), 6.5 (Red Hat)
Weakness
CWE-346
Fixed releases
  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-84176; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-84176?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
  • Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
  • Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)

Vendor advisories for CVE-2026-84176

Apache

1 advisory
  • Advisory severityMedium6.5

    Medium [CVE-2026-84176] Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component

    CVE-2026-84176Source published Source updated

    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…

    Affected products in this advisory
    • Apache Camel Platform
    Source-reported affected versions
    • 4.0.0 before 4.18.5
    • 4.19.0 before 4.22.1
    Source-reported fixed versions
    • 4.18.5
    • 4.22.1
    Mitigation guidance
    • 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.
    • 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.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityMedium6.5

    Medium [CVE-2026-84176] org.apache.camel/camel-platform-http-vertx: camel-platform-http-vertx: Information disclosure via overly permissive CORS configuration

    CVE-2026-84176Source published Source updated

    org.apache.camel/camel-platform-http-vertx: camel-platform-http-vertx: Information disclosure via overly permissive CORS configuration. Red Hat rates this moderate (CVSS 6.5). Weakness: CWE-346. Affected products named by the advisory: OpenShift Serverless; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.

    Related products — impact not confirmed
    • OpenShift Serverless
    • Red Hat build of Apache Camel 4 for Quarkus 3
    • Red Hat build of Apache Camel for Spring Boot 4
    • Red Hat Fuse 7
    Source-reported affected versions
    • < 4.0.0
    • < 4.18.5
    • < 4.19.0
    • < 4.22.1
    Source-reported fixed versions
    • 4.23.0
    • 4.18
    • 4.18.5
    • 4.22

    1 more entries in the full advisory.

    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Full advisory and evidenceOpen source bulletin

References

More Apache advisories

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Download on the App StoreGet CVE alerts on AndroidSee app features