cve.bz

CVE-2026-46726 apache camel: SSRF

7.5 highEPSS 0.9%Fix available

High (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.

On this page
Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Vertx Websocket component. The camel-vertx-websocket consumer mapped inbound WebSocket query and path parameters into the Camel Exchange header map without applying any HeaderFilterStrategy (VertxWebsocketConsumer.populateExchangeHeaders()). Because nothing blocked the Camel header namespace, a client connecting to the WebSocket endpoint could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as query parameters. In a route where the WebSocket consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values and sent to the attacker, disclosing environment variables, application properties and vault secrets. When the WebSocket endpoint is exposed without authentication, this is reachable by an unauthenticated remote attacker. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes the affected consumers apply a HeaderFilterStrategy that filters the Camel header namespace case-insensitively on inbound mapping, so externally-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from the inbound message before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), require authentication on the WebSocket endpoint, and avoid bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-46726

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-46726](https://cve.bz/cve/badge/CVE-2026-46726.svg)](https://cve.bz/cve/CVE-2026-46726)

HTML:

<a href="https://cve.bz/cve/CVE-2026-46726"><img src="https://cve.bz/cve/badge/CVE-2026-46726.svg" alt="CVE-2026-46726"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camel Vertx Websocketfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camel Vertx Websocketfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camel Vertx Websocketfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hgg5-gp4c-gpcgMavenorg.apache.camel:camel-vertx-websocket>=4.0.0 <4.14.84.14.8
GHSA-hgg5-gp4c-gpcgMavenorg.apache.camel:camel-vertx-websocket>=4.15.0 <4.18.34.18.3
GHSA-hgg5-gp4c-gpcgMavenorg.apache.camel:camel-vertx-websocket>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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).

ProductPackageStateAdvisory
Red Hat Build of Apache Camel 3.33.2.SP3org.apache.camel/camel-vertx-websocket:4.18.3.redhat-00001Fixed 2026-07-30RHSA-2026:48118
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16camel-vertx-websocketFixed 2026-08-13RHSA-2026:54622
Red Hat build of Apache Camel 4 for Quarkus 3camel-vertx-websocketAffected

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.

GitHub PoC

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.

  • oscerd/CVE-2026-46726 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-46726: Apache Camel camel-vertx-websocket unfiltered inbound header injection enabling SSRF and secret disclosure v…

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

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).

References

Check your stackJSON