CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in apache camel. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-vertx-websocket 4.14.8, 4.18.3, 4.21.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Norg.apache.camel:camel-vertx-websocket (Maven): fixed in 4.14.8, 4.18.3, 4.21.0Explain CVE-2026-46726 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46726?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46726?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46726 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel Vertx Websocket | from 4.0.0 before 4.14.8 |
| Apache Software Foundation Apache Camel Vertx Websocket | from 4.15.0 before 4.18.3 |
| Apache Software Foundation Apache Camel Vertx Websocket | from 4.19.0 before 4.21.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-hgg5-gp4c-gpcg | Maven | org.apache.camel:camel-vertx-websocket | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-hgg5-gp4c-gpcg | Maven | org.apache.camel:camel-vertx-websocket | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-hgg5-gp4c-gpcg | Maven | org.apache.camel:camel-vertx-websocket | >=4.19.0 <4.21.0 | 4.21.0 |
Red Hat rates this Important.
A flaw was found in the Apache Camel Vertx-WebSocket component. The WebSocket consumer copies inbound query and path parameters into the Camel Exchange header map without applying a HeaderFilterStrategy. An attacker can inject Camel-internal control headers (such as CamelHttpUri) via WebSocket query parameters, causing SSRF when routed to an HTTP producer. The HTTP producer also resolves Camel property placeholders on the attacker-controlled URI, leaking environment variables, application properties, and vault secrets. Red Hat builds of Apache Camel for Spring Boot and Quarkus ship the affected camel-vertx-websocket component.
Restrict access to exposed WebSocket endpoints with authentication. If unable to upgrade, strip Camel-internal headers from inbound WebSocket messages before they reach downstream producers (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route).
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Build of Apache Camel 3.33.2.SP3 | org.apache.camel/camel-vertx-websocket:4.18.3.redhat-00001 | Fixed 2026-07-30 | RHSA-2026:48118 |
| Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16 | camel-vertx-websocket | Fixed 2026-08-13 | RHSA-2026:54622 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-vertx-websocket | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46726.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51), CWE-200 (59).