# CVE-2025-30177: Apache Camel: Camel-Undertow Message Header Injection via Improper Filtering > Attackers can inject Camel headers to trigger code execution via vulnerable components like camel-exec due to missing input filtering. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Apr 2025 - **Updated:** 1 Apr 2025 - **Also known as:** GHSA-vq4p-pchp-6g6v ## What is CVE-2025-30177? CVE-2025-30177 is a medium-severity code injection vulnerability in Apache Camel, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-164 (Improper Neutralization of Internal Special Elements) ## Which versions are affected by CVE-2025-30177? 4 open source packages ship an affected version, including org.apache.camel:camel-undertow. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-undertow` | Maven | From 4.10.0 | 4.10.3 | | `org.apache.camel:camel-undertow` | Maven | From 4.10.0 | 4.10.3 | | `org.apache.camel:camel-undertow` | Maven | From 4.8.0 | 4.8.6 | | `org.apache.camel:camel-undertow` | Maven | From 4.8.0 | 4.8.6 | Products: Apache Camel. ## How do I fix CVE-2025-30177? Upgrade org.apache.camel:camel-undertow to a fixed version for your release line: 4.10.3 or 4.8.6. ## Is CVE-2025-30177 being exploited? There is no known exploitation of CVE-2025-30177 in the wild and no public exploit code. ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-30177 and fix it if it is affected. What it is: CVE-2025-30177 is a medium-severity code injection vulnerability in Apache Camel, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-30177 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-undertow (Maven): affected from 4.10.0; fixed in 4.10.3 - org.apache.camel:camel-undertow (Maven): affected from 4.10.0; fixed in 4.10.3 - org.apache.camel:camel-undertow (Maven): affected from 4.8.0; fixed in 4.8.6 - org.apache.camel:camel-undertow (Maven): affected from 4.8.0; fixed in 4.8.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-30177/ (Markdown: https://insights.sbomify.com/CVE-2025-30177/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30177 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30177 - OSV: https://osv.dev/vulnerability/CVE-2025-30177 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-30177/ Summaries are generated and may contain mistakes; the official description above is the record.