cve.bz

CVE-2026-78329 apache camel: Improper Input Validation

9.8 criticalEPSS 0.6%Fix available

Critical (9.8) in apache camel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-undertow 4.14.9, 4.18.4, 4.22.0.

On this page
Improper input validation vulnerability in Apache Camel Undertow component. This issue affects Apache Camel: from 4.11.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. UndertowEndpoint defaulted its headerFilterStrategy field to the base HttpHeaderFilterStrategy and pushed that instance into the UndertowHttpBinding it creates lazily, overwriting the UndertowHeaderFilterStrategy that DefaultUndertowHttpBinding installs in its own constructor. Unless a deployment supplied a custom binding or an explicit headerFilterStrategy, the undertow-specific filtering therefore never executed on endpoint-configured routes: the strategy object was constructed and immediately replaced before it could be consulted. The consequence is that the legacy websocket. Exchange-header prefix was not filtered at the undertow transport boundary in either direction, so an undertow HTTP consumer mapped inbound wire headers of that form onto the Exchange, where an undertow WebSocket producer reads them as dispatch directives and can be made to deliver to a peer other than the one the route selected; and header names that undertow itself does not accept were mapped onto the Exchange rather than being skipped. Rest DSL consumers were never affected, because UndertowComponent assigns UndertowRestHeaderFilterStrategy explicitly, which extends the undertow strategy. This is not a regression of CVE-2025-30177: the base HttpHeaderFilterStrategy configures the inbound Camel-prefix filter itself, so the protection introduced by that advisory continued to work through the base class and was never lost. What the change did was leave the undertow strategy orphaned on the endpoint path, with the effect that two subsequent corrections written into it - one skipping header names undertow rejects, one filtering the legacy websocket. prefix in both directions - were applied to a class the endpoint no longer used and never took effect in the releases that shipped them. Users are recommended to upgrade to version 4.22.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.9. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.4. For deployments that cannot upgrade immediately, configure the strategy explicitly rather than relying on the default, for example by binding an UndertowHeaderFilterStrategy in the registry and referencing it on the endpoint as undertow:http://0.0.0.0:8080/foo?headerFilterStrategy=#myStrategy, and additionally strip the dispatch headers at the trust boundary with removeHeaders(“websocket.*”). Note a residual limitation that upgrading does not remove: the undertow component deliberately keeps the websocket. values as part of its externally visible API contract, and UndertowProducer reads them with in.getHeader, which does not consult a HeaderFilterStrategy at all. The restored filtering is therefore defence in depth at the undertow transport boundary only. A route that carries an untrusted message from a non-undertow consumer into an undertow producer is not protected by this fix and must strip those headers itself.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th 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: total, assessed 2026-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
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-78329 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78329?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78329?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-78329 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-78329

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-78329](https://cve.bz/cve/badge/CVE-2026-78329.svg)](https://cve.bz/cve/CVE-2026-78329)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.11.0 before 4.14.9
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.4
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v7h8-xhh6-gfj4Mavenorg.apache.camel:camel-undertow>=4.11.0 <4.14.94.14.9
GHSA-v7h8-xhh6-gfj4Mavenorg.apache.camel:camel-undertow>=4.15.0 <4.18.44.18.4
GHSA-v7h8-xhh6-gfj4Mavenorg.apache.camel:camel-undertow>=4.19.0 <4.22.04.22.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires a specific route topology where unvalidated HTTP input directly reaches an Undertow WebSocket producer, limiting the blast radius to unauthorized message delivery or data exposure without enabling remote code execution. In Red Hat integration environments, routes exposed via the Rest DSL are not affected as they configure dedicated header filtering by default. Applications remain at risk only when standard Undertow endpoints process untrusted client requests without custom header filter definitions or explicit header sanitization.

Red Hat's mitigation

Configure an explicit UndertowHeaderFilterStrategy on the endpoint (e.g. bind an UndertowHeaderFilterStrategy in the registry and reference it on the endpoint as headerFilterStrategy=#myStrategy) and/or strip the dispatch headers at the trust boundary with removeHeaders("websocket.*") before routing to an undertow WebSocket producer. Residual limitation: routes carrying untrusted messages from a non-undertow consumer into an undertow producer are not protected by the fix and must strip those headers themselves. Upgrading to the fixed versions (4.14.9 for the 4.14.x LTS stream, 4.18.4 for the 4.18.x stream, 4.22.0 otherwise) restores UndertowHeaderFilterStrategy as the endpoint default.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4camel-undertowAffected
Red Hat Fuse 7camel-undertowOut of support scope
Red Hat Single Sign-On 7camel-undertowOut of support scope

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

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-78329 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-78329 (Apache Camel camel-undertow header filter strategy not applied, websocket.* injection) — Camel Spring Boot

Attack patterns (CAPEC)

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

References

Check your stackJSON