PoC Monitor
← All CVEs
CVE-2026-78329published 24 Aug 2026 16:22 UTCData: JSON · API

Apache Software Foundation Apache Camel

Apache Camel: 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

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.

First public PoC 0 h beforebefore publication · 24 Aug 2026
Public PoCs11 on GitHub
CVSS9.8critical · scored by CISA ADP · CWE-20
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Apache Software Foundation Apache Camel
  • >= 4.11.0, < 4.14.9
  • >= 4.15.0, < 4.18.4
  • >= 4.19.0, < 4.22.0

Fixed in 4.14.9, 4.18.4, 4.22.0

Mitigation

Upgrade Apache Camel to 4.14.9 or 4.18.4 or 4.22.0 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8First public PoC24 Aug 2026 · t = 0CVE published24 Aug 2026 · t = 0

First public PoC 0 h before publication; not in CISA KEV. First PoC: oscerd/CVE-2026-78329 (created 24 Aug 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-78329 24 Aug 2026 t = 0 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /exploit/attack
(?i)^/exploit/attack(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-78329 Apache Software Foundation Apache Camel exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-78329; classtype:web-application-attack; sid:9730341; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-78329)
id: gg-pocmon-cve-2026-78329-9730341
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-78329. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-78329
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/exploit/attack'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.78329