Apache Camel Missing Header Out Filter Leads to Potential Bypass/Injection Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2025-30177: 1.29% estimated exploitation activity in the next 30 days; percentile 70.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Bypass/Injection vulnerability in Apache Camel in Camel-Undertow component under particular conditions. This issue affects Apache Camel: from 4.10.0 before 4.10.3, from 4.8.0 before 4.8.6. Users are recommended to upgrade to version 4.10.3 for 4.10.x LTS and 4.8.6 for 4.8.x LTS. Camel undertow component is vulnerable to Camel message header injection, in particular the custom header filter strategy used by the component only filter the "out" direction, while it doesn't filter the "in" direction. This allows an attacker to include Camel specific headers that for some Camel components can alter the behaviour such as the camel-bean component, or the camel-exec component.

Published by the source

1 Apr 2025, 12:30 UTC

Last modified by the source

1 Apr 2025, 22:07 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vq4p-pchp-6g6v

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

# Patch Next advisory brief: CVE-2025-30177

Advisory: Apache Camel Missing Header Out Filter Leads to Potential Bypass/Injection Vulnerability
IDs: CVE-2025-30177, GHSA-vq4p-pchp-6g6v
Record: https://patchnext.com/advisories/cve-2025-30177 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
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.10.3, 4.8.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-undertow: affected >= 4.10.0, < 4.10.3; >= 4.8.0, < 4.8.6; fixed in 4.10.3, 4.8.6

## 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://github.com/advisories/GHSA-vq4p-pchp-6g6v (GitHub-reviewed advisory GHSA-vq4p-pchp-6g6v lists affected ranges: Maven org.apache.camel:camel-undertow >=4.10.0 =4.8.0 <4.8.6)

Commands are suggestions: review each one before running it.