What is CVE-2025-30177?

CVE-2025-30177 is a medium-severity security vulnerability in org.apache.camel:camel-undertow (maven), affecting versions >= 4.10.0, < 4.10.3. It is fixed in 4.10.3, 4.8.6.

How severe is CVE-2025-30177?

CVE-2025-30177 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.camel:camel-undertow are affected by CVE-2025-30177?

org.apache.camel:camel-undertow (maven) versions >= 4.10.0, < 4.10.3 is affected.

Is there a fix for CVE-2025-30177?

Yes. CVE-2025-30177 is fixed in 4.10.3, 4.8.6. Upgrade to this version or later.

Is CVE-2025-30177 exploitable, and should I be worried?

Whether CVE-2025-30177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-30177 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-30177 in org.apache.camel:camel-undertow

Q: How severe is CVE-2025-30177?

CVE-2025-30177 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.camel:camel-undertow are affected by CVE-2025-30177?

org.apache.camel:camel-undertow (maven) versions >= 4.10.0, < 4.10.3 is affected.

Q: Is there a fix for CVE-2025-30177?

Yes. CVE-2025-30177 is fixed in 4.10.3, 4.8.6. Upgrade to this version or later.

Q: Is CVE-2025-30177 exploitable, and should I be worried?

Whether CVE-2025-30177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-30177 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-30177?

Upgrade: org.apache.camel:camel-undertow to 4.10.3 or later, org.apache.camel:camel-undertow to 4.8.6 or later.

Summary

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

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.

Impact

CVE-2025-30177 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.10.3, 4.8.6); upgrading removes the vulnerable code path.

Affected versions

org.apache.camel:camel-undertow (>= 4.10.0, < 4.10.3) org.apache.camel:camel-undertow (>= 4.8.0, < 4.8.6)

Security releases

org.apache.camel:camel-undertow → 4.10.3 (maven) org.apache.camel:camel-undertow → 4.8.6 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-undertow to 4.10.3 or later; org.apache.camel:camel-undertow to 4.8.6 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-30177? CVE-2025-30177 is a medium-severity security vulnerability in org.apache.camel:camel-undertow (maven), affecting versions >= 4.10.0, < 4.10.3. It is fixed in 4.10.3, 4.8.6.
How severe is CVE-2025-30177? CVE-2025-30177 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.camel:camel-undertow are affected by CVE-2025-30177? org.apache.camel:camel-undertow (maven) versions >= 4.10.0, < 4.10.3 is affected.
Is there a fix for CVE-2025-30177? Yes. CVE-2025-30177 is fixed in 4.10.3, 4.8.6. Upgrade to this version or later.
Is CVE-2025-30177 exploitable, and should I be worried? Whether CVE-2025-30177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-30177 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-30177?
- Upgrade org.apache.camel:camel-undertow to 4.10.3 or later
- Upgrade org.apache.camel:camel-undertow to 4.8.6 or later