Skip to content

← Actionable
Critical, CVSS 9.8amended

Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes

CVE-2026-78329GHSA-v7h8-xhh6-gfj4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.camel:camel-undertow 4.22.0, 4.18.4, 4.14.9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-78329: 0.74% estimated exploitation activity in the next 30 days; percentile 54.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-v7h8-xhh6-gfj4

  2. Revision 1 · created ·

    Published from osv record GHSA-v7h8-xhh6-gfj4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-78329

Advisory: Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes
IDs: CVE-2026-78329, GHSA-v7h8-xhh6-gfj4
Record: https://patchnext.com/advisories/cve-2026-78329 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-undertow 4.22.0, 4.18.4, 4.14.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-undertow: affected >= 4.11.0, < 4.14.9; >= 4.15.0, < 4.18.4; >= 4.19.0, < 4.22.0; fixed in 4.22.0, 4.14.9, 4.18.4

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-undertow: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-undertow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v7h8-xhh6-gfj4 (OSV record GHSA-v7h8-xhh6-gfj4 lists affected ranges: Maven org.apache.camel:camel-undertow >=4.11.0 =4.15.0 =4.19.0 <4.22.0 (fixed))
- Verified: https://github.com/advisories/GHSA-v7h8-xhh6-gfj4 (GitHub-reviewed advisory GHSA-v7h8-xhh6-gfj4 lists affected ranges: Maven org.apache.camel:camel-undertow >=4.11.0 =4.15.0 =4.19.0 <4.22.0)

Commands are suggestions: review each one before running it.

Loading voting…